Skip navigation

Starting from ESX 4.0, the "legacy" version of VMware's bare-metal hypervisor is a real VM, with also a virtual disk (by default named esxconsole.vmdk).

Unfortunately this does not mean that is more flexible, because you cannot manage it from vSphere Client.

 

But there a several (unsupported) way to manage this virtual disk:

 

How to Move the COS (esxconsole.vmdk) in VMware ESX 4 (vSphere)

http://www.toniwestbrook.com/archives/168

 

Adding a second VMDK to your ESX Service Console

http://www.virtuallifestyle.nl/2010/11/adding-a-second-vmdk-to-your-esx-service-console/

 

How to extend the virtual disk of the Service Console

How to extend the virtual disk of the Service Console

 

ESX fails to boot when the disk containing the datastore with esxconsole.vmdk is detected as a snapshot

http://kb.vmware.com/kb/1012142

 

Partitioning your ESX host – part II

http://www.yellow-bricks.com/2009/05/27/partitioning-your-esx-host-part-ii/

 

Best Practices for vSphere (ESX 4) Service Console Partitions

http://vmetc.com/2009/07/22/best-practices-for-vsphere-esx-4-service-console-partitions/