9 Answers
9

I would put your VM images on a seperate spindle. Having them on a seperate disk with a large cache is likely to yield a much larger performance boost than which filesystem you use.

Given that a corruption in a VM image could be catastrophic, I would be looking at robustness of filesystem over performance. Is it likely to survive a power failure, for example? So (to use the examples you've cited) I would certainly use NTFS over FAT32, regardless of performance characteristics, simply because it is a journaling filesystem and therefore much more fault tolerant.

If possible, I would highly recommend putting your virtual machine images on another hard drive and not on the same drive (even if it is on a different partition). Save your main hard drive for OS tasks and running Virtualbox, and let the second drive handle the data, because there will be a lot of it going back and forth, and it will slow down your system considerable as the hard drive becomes the bottleneck.

If you have to keep it on the same drive, make sure you use large blocks when formatting it. Since large chunks of data are moved, I believe that this will help performance (someone please correct me if I am wrong here). I am not sure if there is a better fs for the images or not. This post from Sun points towards ZFS as being pretty nice to use.

I counter that in production. I have a number of servers running RAID 10s for the OS and virtualization. The IO overhead of the OS (just running a hypervisor) is low enough not to be memorable, and the 64gb partition is small. THis is more efficient than lossing 2 discs. Note that I dont mean small system - the largetst has a 6 disc boot now with 64gb RAM running a lot of machines. It soon getsupgraded to 8 discs because of space need ;)
– TomTomOct 28 '10 at 18:39

For host based VMs, it doesn't really matter. You'll want to use something that easily works with larger files though, so stay away from file systems like reiserfs which handles smaller files faster than larger ones. Most of my linux installs go with jfs for journaling speed and B+ Tree. See wiki link

..and you may already be aware of this. Ubuntu doesnt natively read NTFS. This requires the installation of a separate package, which is very simple, but I have noticed that performance on the NTFS partition, when read by Ubuntu, is noticeably slow.

The partition on Linux that hosts the vmdk files does matter I think, if that is what you are actually asking.

XFS might be best as it is more tested, you will get disk IO improvements with that. You could also use the newer ext4. The main things you want is extents so the big files don't get broken up, both these file systems have that and support Linux well. Myself, I would go with ext4 just because it is familiar, even if new. However, I have no numbers to back this up right now :-)

Also, allocate all the disk space first, don't chose grow as needed. The best option for performance might be to give the VM direct access to the partition itself, so there isn't an extra layer, but that kind of ruins the point of VMs for many people.

Lastly, this link has some tuning tips vmware server running on Linux that might help you get better IO performance.

ext3 is best. Don't go for ext4 as it was kinda disturbing to my harddisk. Before or after installing ubuntu do learn the terminal commands to repair and check your partition for errors. You will surely needed to do it occasionally in commandline mode if you deal with both NTFS and ext like partitions on same harddisk.

Due to too many command line operations, there are too many questions about every possible problem in ubuntu. Amazingly there are equal and more helpers are also available.

I was too having in such problems and by that time my system was on the window installation mode and asking for partition of hard disk. I was surfing internet on my mobile to find solutions about what to do.

And amazingly I got so many supported replies that I easily finished my partitions.

I am thanking all those who are spending their time and thoughts on ubuntu development and support!

If you chose NTFS, and you are going to run VMWare, it really doesn't like having it's VM flat files on an NTFS partition. We could never get the vm's to run if the files were on ntfs, we had to use ext3.(i am running vmware server1.x on top of RHEL)