qemu would pause a vm when doing extend on the vm disk and this would
result in INFO messages on vm's pause.
looks like this is what you are seeing.
Dafna
On 09/09/2014 02:45 PM, Frank Wall wrote:
Hi,
today I've noticed that one of my VMs was paused. I took a look
at the engine.log and found only this:
2014-09-09 04:00:09,017 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
(DefaultQuartzScheduler_Worker-46) VM XXX 8ad326be-5103-498a-a11d-0ea1eee4bbf4 moved from
Up --> Paused
The vdsm log provides a better error message:
libvirtEventLoop::INFO::2014-09-09 04:00:07,279::vm::4574::vm.Vm::(_onIOError)
vmId=`8ad326be-5103-498a-a11d-0ea1eee4bbf4`::abnormal vm stop device ide0-0-1 error
libvirtEventLoop::DEBUG::2014-09-09
04:00:07,279::vm::5176::vm.Vm::(_onLibvirtLifecycleEvent)
vmId=`8ad326be-5103-498a-a11d-0ea1eee4bbf4`::event Suspended detail 2 opaque None
Still, I don't know what exactly caused this. Only *one* VM was affected,
so I doubt it was a general error on this host. Does anyone have an
explanation for this?
ovirt-engine-3.4.3-1.fc19.noarch
vdsm-4.14.11.2-0.fc19.x86_64
Regards
- Frank
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users