VMware Cloud Community
mortengh
Enthusiast
Enthusiast

Migration/cloning results in corrupted target VM

Hello!

I have a strange problem where migrating or cloning a VM results in a VM with ALOT of disk errors.

I have one SSD with native VMFS - on which only a Solaris-11.2 VM exists (a ZFS fileserver).

The fileserver shares an NFS share that is mounted by the host itself. This works great and have done so for years.

I though have a strange situation where I clone/migrate a VM from the fileserver to the native VMFS on the SSD.

It seems to go well but the resulting VM is corrupted. It can boot but with alot of diskerrors.

I have tried to do an MD5 compare of the 'flat' file and they are different.

This is strange because the host can read data from the fileserver via NFS. It does that all the time. And it can write data to the VMFS on the SSD (I can create a VM on the SSD manually). But when the two processes are combined the problems occures.

Have anybody had these problems?

System:

  Host: HP Proliant Microserver N40L, 16GB ECC RAM

  Hypervisor: ESXi-5.5_update2

  HBA: LSI-9240i (only one used. HP internal controllers NOT used - ESXi booted from internal USB)

I know the host isn't supported but anyway - I do not expect this to be a problem in this situation?

Best regards,

- Morten Green Hermansen, Fanitas

Tags (3)
Reply
0 Kudos
0 Replies