Hello,
the problem is "waiting for launch" takes up to 20 min. I did a lot of tests with some vm's and th problem is: 1. create a win2012 server 2. attache a new disk (thin provision) 3. fill the disk from network share with about 100G 4. shutdown the vm 5. reboot host and try starting the vm (takes a lot of time until launch) It's because of a high fragmented filessystem Thanks Wolfgang -----Ursprüngliche Nachricht----- Von: Milan Zamazal <[email protected]> Gesendet: Die 23 August 2016 15:17 An: Wolfgang Bucher <[email protected]> CC: [email protected] Betreff: Re: Problem starting VMs Wolfgang Bucher <[email protected]> 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?
_______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
