Issues with VMotioning VMs on local storage but not cold VMotion

[chicagovm]

I have 2 ESX servers utilizng a x-over cable for VMotion for testing purposes.

The local VMFS storage was setup on both. When I cold VMotion it moves the VM and disk files over.

When I try to hot VMotion I get errors regarding the following: The VM has no real OS at this point as it just has a 8GB HD1.

Unable to access the file xxx.vswp

HD1 is not accessible to the destination host. Unable to access file xxx.vmdk

Any ideas?

Same happens with VM that has an OS on the VMDK.

[TCronin · Accepted solution]

Shared storage is a requirement for vmotion. Both hosts have to have access to the same volume as only the memory, cpu and network connections are moved in a vmotion. The actual disk stays in place. So to do a vmotion you have to have either a SAN, or iScsi or NFS.

[chicagovm]

Vmotion only works with shared SAN storage..

duh!

thnks

[vijayalka]

Means Vmotion not worked with ISCSI and NFS?

It only works with SAN am I correct?

Thanks

Vijay