I'm familiar with extending .VMDK files but, I noticed that the one I just extended still shows the original size in Virtual Center under the VM settings. Is this something that will resolve itself or is there something I have to restart to force it to display the new size.
Removing/readding the VM is fairly non-disruptive. It doesn't impact power operations of the VM or the VMs availability on the network. About the only things you have to do is re-add it back to whatever VM folder structure you previously had it in, and also check to see whether or not the VM's historical performance data gets nuked (you may or may not care about this one).
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
The easiest way in my opinion is just to remove it from the VM (but don't delete it from disk) and then add it as existing disk. Then the size will be shown correct.
That's the way I do it.
Axel
VirtualCenter can be a little slow in updating the display. Try not to let it bother you too much. If you want immediate results, you could probably unregister/reregister the VM but that's a lot of work for very little return.
Jas
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
Hi,
Try restarting the VC agent service from service console, that will update the information
Thanks
Both, removing the disk from the VM and sdding it back like ax_s posted and unregistering and re-registering the VM as jasonboche posted both sound like good suggestions. I won't be able to try either of these anytime soon. Restarting the VC agent or just waiting don't resolve the display. I may try bouncing the Virtual Center server but, I doubt if that resolves it either.
It would be nice to non-disruptivley fix the display only because when you're trying to see what is taking up your datastore it will be confusing.
Removing/readding the VM is fairly non-disruptive. It doesn't impact power operations of the VM or the VMs availability on the network. About the only things you have to do is re-add it back to whatever VM folder structure you previously had it in, and also check to see whether or not the VM's historical performance data gets nuked (you may or may not care about this one).
[i]Jason Boche[/i]
[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]
You must restart the VCI service !
Sorry...I'm not familar with this VCI service. Can you explain?
Hi,
Try
service mgmt-vmware restart
To restart VC services
Thanks
restart the windows Service ....
