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

I have a vmdk file which can grow to 600 gb, and splits every 2 gb. Since I physically have 2 x 500gb drives, I would like some of the 2-gig vmdk's to be on D:\, and the rest be on E:.

I edited the master vmdk file (which lists all the 2-gig vmdk files) and tried giving each a full file path. However when I boot the virtual machine I get an error saying "unable to open [master vmdk filename]"

Any ideas if it's possible to split those sub-vmdk files across multiple drives?

share|improve this question
add comment

2 Answers

Why are you splitting it into 2GB chunks? there's no need, that's a very old compromise they still keep in for backwards compatibility - nobody would use that in a professional environment. Also would you not consider just expanding D: with the space on the second drive rather than fiddle with the config file? Manually editing such a key file will only lead to heartache even if you got it working this time.

This site's for pro's and everything about your question strikes me as more of a home environment - is that the case?

share|improve this answer
    
Thanks chopper. It is a bit of a home job. Should I ask elsewhere? If I don't split every 2 gigs, what happens when the guest OS grows larger than 500gb? –  Fidel Jan 7 '13 at 17:32
    
See, this is a resource-limitation issue, i.e. home related, take a look at our FAQ at some point please, it'll help you understand why we're here and also our sister-sites. Basically in a pro environment you'd have the .vmdk created at full size on day one to aid in stability and performance - you can't do that as it is right now, not without combining your disks. –  Chopper3 Jan 7 '13 at 17:42
    
Understand. Thanks chopper –  Fidel Jan 7 '13 at 18:00
add comment
up vote 1 down vote accepted

The path has to be relative to the master vmdk file (doco). Create a symbolic link using junction so the vmdk thinks it's referring to a subdirectory whereas in fact it's referencing E:\

junction "D:\VMs\VirtualMachineA\e-drive" "E:\VirtualMachineA\"

Then edit the master vmdk file eg:

RW 4192256 SPARSE "/e-drive/VirtualMachineA-s101.vmdk"
share|improve this answer
add comment

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.