Not exactly sure how to tell this but here goes:
We are in the process of migrating over our exsisting VM guests from our old Vm server farm (all Intel -->all AMD) All migrations have been done cold and then tools updated etc to the current updates.
No issues have show up at this time from that process. BUT one of the guest needed to have the vmdk file extended for additional space (no big deal here as we had been doing that all the time) Well I shut down the guest edited properties and selected the harddisk and went from 15GB to 25GB then applied the new setting and then went to my guest server that I use for diskpart runs. I went into edit properties add existing HD and drilled down to the location of the vmdk file and selected the expanded vmdk file click ok to add it and the folowing error comes up: "Internal Problem: The system information reported by the host for 'VirtualDisk' is inconsistent. This device cannot currently be edited." & when you acknowledge this error you get the following error "Object reference not set to an instance of an object." I get that twice
So point one:Guest runs fine no errors that I can see. I can do a normal new partition inside the VM with no issues.
Point 2: If I do a clean template deploy I can extend the vmdk files with no issues
Point 3: I can vmotion /storage vmotion and pretty much anything I want with the guest with no issues except attach it to another guest to run diskpart.
Now one more thing I decided to try I had 2 guest that I had decomissioned so I used one of them and de-attached its vmdk file and tried to attach it to another VM guest (no go) so I then tried to attach it back to the its original guest profile and it would not attach back to its self and I get the exact same errors listed above...!
So any thoughts, suggestions, pointers etc would be much appreciated as this makes no sense to me at the moment. I'm running ESXvi3.5U3 and I believe I'm runnning VCC 2.5U2 or 3 but not the latest that was just released...
SOunds like the partition editing did not work as expected.... When I do this, instead of editing the partitions by hand I use VMware COnverter and perform a V2V, during the V2V I modify the size of the VMDK to be what I desire (lower or higher) and let it handle all the partition code. This tends to work much better than doing things by hand.
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.
Blue Gears and SearchVMware Pro Blogs: http://www.astroarch.com/wiki/index.php/Blog_Roll
Top Virtualization Security Links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links