> On 23 Aug 2016, at 11:06, Wolfgang Bucher <wolfgang.buc...@netland-mn.de> > wrote: > > Thank's > > but what do you mean with "initialization is finished”
until it gets from WaitForLaunch to PoweringUp state, effectively until the qemu process properly starts up > > sometimes the vm crashes while copying files! when exactly? Can you describe exactly what you are doing and what is reported as a reason for crash. When exactly does it crash and how? Thanks, michal > > > > Wolfgang > > > -----Ursprüngliche Nachricht----- > Von: Milan Zamazal <mzama...@redhat.com> > Gesendet: Die 23 August 2016 16:59 > An: Wolfgang Bucher <wolfgang.buc...@netland-mn.de> > CC: users@ovirt.org (users@ovirt.org) <users@ovirt.org> > Betreff: Re: AW: Problem starting VMs > > Wolfgang Bucher <wolfgang.buc...@netland-mn.de> writes: > > > 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 > > I see, thank you for the explanation. In such a case, it may take a lot > of time before all the initialization is finished. > > Regards, > Milan > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
