Empty VMWare SCSI disks

We had a heated discussion in our team today. One of my teammates was complaining that the existing 8 GB disk (the .vmdk file) that he had attached to his VMWare Player was running out of space. Hence he needed a work around for that. Remember that all of us only have a VMWare Player, not a VMWare Workstation using which you can create a hard disk image. I suggested him a hack.
  • Copy the existing .vmdk file. Give it a new name.
  • Add that file as the next SCSI drive in your VWWare configuration file (.vmx file). You can do it easily by editing your .vmx file in notepad.
  • Start your virtual OS. In his case it was RH Linux.
  • Format the newly added disk. (mke2fs /dev/sdb).
You are done. You have another 8 GB of storage. But still I was not happy about this hack. What in case he exhausts all this 8 GB soon. So I was searching the Internet. My objective is simple: I have an up and running VMWare virtual OS where I would like to add a new SCSI drive of whatever size I want.

Well! Forever For Now gives empty SCSI disks for your VMWare player in three different sizes. Added to that, you also get a bunch of good tips-and-tricks that are very useful. Go ahead and give it a try!

Forever For Now site also gives a lot of other articles that are useful too. You might find it an interesting reading to go through their web site.

Comments

Post a Comment

Popular posts from this blog

Gotchas with DBCP

I had to make use of DB connection pool in one of the applications that I was implementing. Since I am new to Java, everyone in the team was suggesting why don't you make use of Commons DBCP. Being a fan of reuse, I decided to make use of DBCP and started reading about the parameters that are exposed so that I can customize DBCP to fit my needs. While reading through the available configuration parameters , I was thinking, "I don't need to check the connection to be bad on every borrow or return. It is sufficient if I check for being bad only when the connection is sitting idle in the pool." So I set the testWhileIdle to be true and set the validationQuery to be "SELECT 1 FROM DUAL". I was thinking that the configuration that I had was the optimal for the situation in hand. But one thing I overlooked was, the default value for the testOnBorrow is true. So the moment you set the validationQuery to be any non-null value, every connection you borrow from the po
Read more

A note on Java's Calendar set() method

Remember that the Calendar's internal fields include year, month, date, hour, minutes, seconds, milliseconds and time zone. Whenever you are calling a set() method with multiple fields, like set(year, month, date), it will not affect the rest of the fields. Remember that there is no set() method with multiple fields available to set the milliseconds. If you would like to set the milliseconds, you must use set(Calendar.MILLISECOND, value). Likewise, if you are planning to set all the fields, its a good idea to reset all the fields using clear() method. This will clear milliseconds as well. Most of the times, millisecond field may not be of interest to you. But if you are going to use the UTC milliseconds, by calling getTimeInMillis(), then make sure you set the right values for milliseconds as well.
Read more

The mysterious ORA-03111 error

Recently one of the applications that I developed started throwing exceptions, that had the following message: SQL state [72000]; error code [1013]; ORA-03111: break received on communication channel When I googled around, I couldn't come across anything useful. Sadly enough most of the sites just showed the documentation for that error, without any explanation from anyone experiencing that issues. So here you go, with the best possible explanation that I could come up with. My application sets two things on the connection that is throwing this exception: It sets the fetchSize to be 2500 rows It sets the query timeout to be 10 seconds The database server and the application are separated over a long latency network (actually there is a NetEm box that emulates the long latency between these two boxes) which has a latency characteristic of 50+/-5 milliseconds. This is the whole setup. It is important to understand how the timeout is handled by the Oracle client (in my case JDBC clien
Read more