Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The situation:

I have these virtual machines that are used for building software, and I'm trying to keep all the builds on the same "disk", if you will. The virtual machines:

2 x Windows
4 x Linux (3 Mandriva and 1 CentOS)

What is the best way to share a drive between virtual machines? I am currently using NFS (sharing a drive from Linux -> Windows using Services for Unix), but I'm not sure that is the most efficient.

share|improve this question
up vote 2 down vote accepted

I usually lean towards running Samba on Linux to facilitate file sharing with Windows. Mostly because you don't have to worry about setting up custom services on the Windows side. That's a plus for me because I find it easier to implement services on the Linux side.

You can mount the shares using the cifs filesystem type (which supersedes smbfs) on the other Linux machines.

The samba software suite, as well as the cifs kernel module, are usually included by default in most distributions.

share|improve this answer

which virtual machine are you using ? Propably you could create a common shared disk. Have a look at

share|improve this answer
I'm using VMWare. – Sagar Aug 10 '10 at 18:06
They use machines with the same OS. I wonder if that would work between Linux and Windows. – Sagar Aug 10 '10 at 18:15
Yes, that's the gotcha. With your heterogeneous environment, you would need to find a clustered file system which supports both Windows and Linux. I'm not aware of any non-commercial solution (i.e. costs a lot) which would fit that requirement. – chuckx Aug 10 '10 at 18:31
Client or server support? Gluster has native samba support, as I recall. Linux or similar servers. – Ronald Pottol Aug 10 '10 at 20:14
If i understood well , The article suggest to "exploit" the fact that they are instances of the same virtual machine and not totally seperate machines. An example of what i mean ... InstanceA -(write)> VMmanager (disk) -(read)> InstanceB So, instead of using some network interface, it's using the fact that they can be connected "internally" via the manager. – Nikolaidis Fotis Aug 10 '10 at 20:30

Your Answer


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.