Celebroom
Contributor
Contributor

VM lockup during/after VMotion

(I changed the topic to better describe what is being experienced)

Hi All,

Just wanted to know if anyone has experienced instability with Linux (Ubuntu HardyHeron in this case) VMs during/after a VMotion? Ill describe the environment.

Dell blade m600s connected to an EMC CX3-20c. Each blade is dual quad core with 32GB of memory. They're all part of an enterprise cluster and the hosts are running 3.5.0, 130756.

Ive noticed this occur on two VMs now - Ive now set them to Partially Automated. Ill start to VMotion them across to another blade for whatever reason and after a few seconds they lockup. Im not just talking a simple easy "click restart" or "power down" lockup, Im talking hard lockup. I cant power the VMs off from vCenter or directly from the host. Eventually I have to vMotion all other VMs off and actually kill the relevant process ID. Also to note, while the VM is in this state flatlines their vCPUs and obviously the processors on the host.

The interesting thing is that the two VMs in question have very different functions and different levels of IO. One is a radius server with a mysql db, and the other is a low IO CVS server. Ive experienced instability with paravirtualization and the Sun JRE before, and thought perhaps something was acting up there, but I dont think so - grasping at straws.

A further item to consider is that we have other Linux VMs in this cluster running the same kernel and this doesnt happen. And yes, VM tools is installed on all of them.

Anyone got any thoughts? Ive looked in the logs and cant see anything glaringly obvious. o_O

Cheers,

Celery

Message was edited by: Celebroom

0 Kudos
4 Replies
AntonVZhbankov
Immortal
Immortal

Do you use local storage for virtual machine swap file or "store with VM"?


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, MCITP: SA+VA, VCP 3/4/5, VMware vExpert http://blog.vadmin.ru
0 Kudos
Celebroom
Contributor
Contributor

Hi Anton,

The latter. We store vmswap with the vm.

Cheers,

Celery

0 Kudos
AntonVZhbankov
Immortal
Immortal

The one reason I saw myself: client CD mounted. Somebody opened console, mounted local ISO from desktop or even physical drive.

Log off all VI sessions, relogin to vCenter, so all client CD connections will be dropped, and try to migrate VMs again.


---

VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, MCITP: SA+VA, VCP 3/4/5, VMware vExpert http://blog.vadmin.ru
0 Kudos
amurph
Contributor
Contributor

at what point in the vmotion process do they hang? 10%? 90?

0 Kudos