Re: [ovirt-users] Problem starting VMs
Wolfgang Bucher <wolfgang.bucher(a)netland-mn.de> writes:
After reboot i cannot start some vms, and i get the following
warnings in vdsm.log:
periodic/6::WARNING::2016-08-18
19:26:10,244::periodic::261::virt.periodic.VmDispatcher::(__call__) could not
run <class 'virt.periodic.DriveWatermarkMonitor'> on
[u'5c868b6a-db8e-4c67-a2b7-8bcdefc3350a']
[...]
vmId=`5c868b6a-db8e-4c67-a2b7-8bcdefc3350a`::could not run on
5c868b6a-db8e-4c67-a2b7-8bcdefc3350a: domain not connected
periodic/3::WARNING::2016-08-18
Those messages may be present on VM start and may (or may not) be
harmless.
[...]
sometimes the vm starts after 15 min and more.
Do you mean that some VMs start after long time and some don't start at
all? If a VM doesn't start at all then there should be some ERROR
message in the log. If all the VMs eventually start sooner or later,
then it would be useful to see the whole piece of the log from the
initial VM.create call to the VM start.
And what do you mean exactly by the VM start? Is it that a VM is not
booting in the meantime, is inaccessible, is indicated as starting or
not running in Engine, something else?