Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Is there a clear winner in the filesystem area? As in, does some filesystem perform significantly better in a virtualized environment such as VMWare or VirtualBox? Is there more or less disk space wasted in the VMDK/VDI formats with some filesystems, does the layout of a particular filesystem stand out when running in a virtual environment? Is journalling worth it for non-critical operations? Or are they all the same?

share|improve this question

2 Answers 2

up vote 2 down vote accepted

Honestly, I've found that my choice of filesystem really depended on what the application of the VM was for. Maybe journaling isn't needed if you're never writing anything (in which case, read only might be in order). I use VMs to experiment a lot and have settled on giving ext4 a try. The delayed allocation seems to work quite well with it though I have no hard numbers to give to you.

So what do you need? Stability and reliability? ext3 might be the way to go. Tons of little files? ReiserFS/ext4(maybe). Large contiguous files? XFS. I would think that anything which can delay writing more will be the most efficient due to overhead in write operations but as of now it's all speculation and theorycraft.

share|improve this answer
    
I use a Linux virtual machine with rsync/rsnapshot for making backups of a VPS. I didn't find a good rsnapshot alternative for Windows, my main OS, thus, a VM. The backup contains a copy of the entire OS, so many small files I'd say. And what rsnapshot does is create hard links to create multiple "copies" of files that don't change between snapshots. (Doesn't Time machine do this?) Anyway, a few snapshots of the 10GB VPS now take up about 30GB when looking at the VDK. So to sum up, I'd prefer a FS that takes the least amount of space in this scenario - many small files, many hardlinks. –  TomA Oct 6 '09 at 20:13

I like VMDK over VDI basically because VMDK is more mature and has more features. I'm not aware of anything VDI can do that VMDK cannot. Both VDI and VMDK support growable disks which saves disk space on the host. But, the maximum size of a VMDK disk can be expanded without having to backup and restore to a new VMDK disk using vmware-diskmanager. You can then use gparted to resize existing partitions to fill the new disk space. Very slick. With VDI, you would need to create a new VDI disk and migrate data from one to the other, AFAIK.

As far as choosing a filesystem on the guest OS goes, I don't think things change that much in a virtual environment. The same properties you use to choose a filesystem apply equally in both cases.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.