Problem to migrate a VM between 2 ESX hosts

[dmatton]

Hello everybody,

Sorry for my poor english, but I'm French :smileyhappy:

So, I've got a problem when I try to migrate a VM between 2 ESX hosts (rel. 3.0.1).

I use the migrate option in Virtual Center (rel. 2.0.1) and after few minutes, the status goes in time out.

Test 1 : I migrate VM1 (16 GB) between host1 and host2 through VC : OK

Test 2 : I migrate VM2 (116 GB) between host1 and host2 through VC : OK

Test 3 : I migrate VM3 (116 GB) between host1 and host2 through VC : failed / time out

OK, so I wait one day and I realize the same tests

Test 1 : I migrate VM1 (16 GB) between host1 and host2 through VC : OK

Test 2 : I migrate VM3 (116 GB) between host1 and host2 through VC : failed / time out

Test 3 : I migrate VM2 (116 GB) between host1 and host2 through VC : OK

So, the problem is about the VM3, but I don't know why... :smileysad:

Someone can help me and give me some advice ?

Thanks

David

[Nautilus]

Hi David,

what you mean with "migrate" Vmotion (move a powered VM to another Host) or Dmotion (move the vmdk Files betwenn HOSTS).. When vmotion than I'am a little bit confusend tha you write about VMDK File Size.

When you migrate the VMDK Files, Than try with

vmkfstools -i /vmfs/volumes/source.vmdk vmfs/volumes/destination.vmdk

When you want to vmotion this VM than check the log file /var/log/vmware/hostd.log You will get some informations about this Task

Kind regards

Nautilus

________________________________________________________________________________________________________________________________________________

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

[dmatton]

Hi Nautilus,

I don't use Vmotion (no licence) and personnaly I don't use the vmkfstools command to move vmdk files.

In Virtual Center, there is an option which is "Migrate...". I use it, to move a VM from an ESX Server to another ESX Server.

[wila]

Hi,

The default time out on every operation processed via the Virtual Infrastructure Client is 15 minutes. So if you migrate takes over 15 minutes, you'll get an error. This doesn't mean that the process didn't actually complete.

Have you checked if the VM was actually moved?

[dmatton]

Hi wila,

For the VM2, the migration takes 5 hours. And there is no problem, no time out.

[Nautilus]

Hi again,

with vmkfstools you will be copy a VMDK File and move. For trouble shooting. When the copy (cloning) with vmkfstools works, than you know you have Problems with virtual Center and when not, you have problems with ESX hsost and maybe with Virtual Center to.

Kind regards

Nautilus

________________________________________________________________________________________________________________________________________________

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points