adding virtual disks to existing virtual machines

[whuber97]

Hi All -

This morning I deployed a virtual machine from a template. Now, I want to add a 2nd virtual disk to this new virtual machine. When I add the disk, I select the option to "store with virtual machine."

The problem I'm having is that the disk file creates itself in the TEMPLATE's folder, NOT the new virtual machine's folder. AND, it names the vmdk file the same name as the original vmdk, so I can't move it to the right folder. As you all know I can't re-name it either.

Has anyone ever seen this?

[Chamon]

You can rename a vmdk file with the

vmkfstools -E /vmfs/volumes/datastore/servername.vmdk newname.vmdk

this will chang the name of the vmdk the flat and update the metadata.

[whuber97]

Thanks.

I'd still like to understand why esx seems tot hink that the template directory is where my virtual machine is. Something must not be right...

[Chamon]

So you now have both the template directory and the new VM directory? Then you edit the settings of the new VM and add a disk. It then creates the new vmdk in the template directory. That is very strange.

Can you give any other information that might be relevant?

[whuber97]

Those are exactly the symptoms. I thought it was strange too... I've never had this problem before...

[Chamon]

Have you powered on the new VM yet? Have you tried to add the disk while the VM is running?

[whuber97]

Been there done that. Still not working

[SuryaVMware]

Could be a bug we can verify if you post the .vmx file from the VM and the .vmtx file from the template. May be you can file a bug with VMware too..

-Surya

[Chamon]

If you rename it and move it does it still work? You would have to add it back to the vm after renaming it though

[fmateo]

Is it possible you add the disk in the template, not into deployed virtual machine? Review both configurations in VI and then like Surya said both vmx/vmtx files.

Regards

[Texiwill]

Hello,

Sounds like a bug to me, I would contact your VMware Support Representative. Either that or when you deployed the VM, something did not change that should. Look at the settings for the VM and where its default directory is. CHange that to be the proper location. Then disk creations should occur normally.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

SearchVMware Blog: http://itknowledgeexchange.techtarget.com/virtualization-pro/

Blue Gears Blogs - http://www.itworld.com/ and http://www.networkworld.com/community/haletky

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[java_cat33 · Accepted solution]

It sounds like when you deployed the VM from template you ticked the box to "edit hardware" - the "experimental feature" that VMware does note.

If you did edit the hardware before starting the actual deploy from template...... what you've experienced is EXACTLY what happens. It sure is a bug. Another work colleague of mine has had the same problem.

[whuber97]

java_cat33 -

You're exactly right! I did check that box when deploying the machine. Thanks!

Have you reported this to VMware yet?

[java_cat33]

No I haven't reported it - I've never experienced it first hand - I've only seen it.

It's a pretty crazy experimental feature!