Today I wanted to Storage vMotion a VM to a new datastore. But for the first time I got a general error message:
followed up by a general system error message:
I got the same message when I tried to start a “normal” vMotion. So I start to troubleshoot this error. First I looked at the vmware.log of the VM. Nothing unusual in there. So the next stop was the VMkernel. But there was nothing unusual in it too. So I used the good old Microsoft like fix to restart the VMware services at the Service Console using the following command:
service mgmt-vmware restart
after a minute or so I was able to start a vMotion again and after the vMotion completed I started the storage vMotion I was planning to do and this worked like a charm again.
To recap. Sometimes you need to restart the mgmt-vmware to fix the connection between the vSphere host and vCenter.
@gabvirtualworld *sigh* Why do I always have to reselect the resource pool when migrating VMs? Now I can’t move multiple VMs at once when in diff pools.
Well I felt the same about this. For the people who don’t know what Gabrie means whit his tweet, I will add two screenshots to explain it. When you start the Migrate (VMotion) task, You need to select what kind of migration you want to do. I choose the Change host option:
If you want to migrate multiple VM’s then I think you will find the next screen as annoying as I and Gabrie find it.
So to get rid of this annoying option. I created a script with an UI to VMotion multiple VM’s at the same time. Note: You can only VMotion to one Selected host.
We disabled in HA the option “Virtual Machine Monitoring” and set DRS to manual. The problem with Virtual Machine monitoring is:
The Virtual Machine heartbeats are being dropped which is triggered by VMotion and the VM gets reset by the HA feature as it thinks it has gone offline. Since the feature is now off it should be safe to turn on DRS again.
There are more people who have this problem, read the following post on the VMware forum, 3.5U3 – any guinea pigs yet?.
I made a support request @ VMware. The told me today that 20 November patch 10 for VMware 3.5 Update 3 will be released. Patch 10 fixes SOME random reboot problems in Update 3. I hope it resolves this nasty issue.
In deze post lees je hoe je informatie uit de VC database kunt halen d.m.v. een query. Het gaat dan in het bijzonder om het aantal VMotion taken die gestart zijn. Je kunt dan na gaan hoe vaak een VM wordt gevmotioned via een handmatige taak of via DRS.
De volgende query kun je loslaten op VC database:
SELECT vpx_event.event_type, vpx_event.vm_name, vpx_event.create_time from vpx_event where event_type like ‘%migrate%’ SELECT distinct(vpx_event.event_type) from vpx_event order by event_type
De volgende informatie komt dan terug uit de query:
Het gaat dan om de volgende event_types:
vim.event.VmMigratedEvent (handmatige VMotion)
vim.event.DrsVmMigratedEvent (VMotion via DRS)
Meer informatie vind je in het volgende Topic op VMUG.nl gestart door Gabrie.