Re: [ovirt-users] Prestarted vms in a pool

----- Original Message ----- > From: "Michal Skrivanek" <michal.skrivanek(a)redhat.com&gt; > To: "Omer Frenkel" <ofrenkel(a)redhat.com&gt; > Cc: "Michel Rode" <rode(a)b1-systems.de&gt;, users(a)ovirt.org > Sent: Thursday, August 28, 2014 10:59:16 AM > Subject: Re: [ovirt-users] Prestarted vms in a pool > > > On Aug 28, 2014, at 09:56 , Omer Frenkel <ofrenkel(a)redhat.com&gt; wrote: > >> >> >> ----- Original Message ----- >>> From: "Michel Rode" <rode(a)b1-systems.de&gt; >>> To: users(a)ovirt.org >>> Sent: Wednesday, August 27, 2014 10:53:00 PM >>> Subject: [ovirt-users] Prestarted vms in a pool >>> >>> Hi all, >>> >>> we have a little problem here...we created a new pool with 10 vms and 4 >>> of them as prestarted. >>> >>> During the sysprep (Windows vms) the vms getting rebooted and this is >>> the problem: >>> >>> 2014-08-27 17:22:47,759 INFO >>> [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] >>> (DefaultQuartzScheduler_Worker-54) VM PC53VP0002-3 18d06e9b-3674-4ad6-b3 >>> c9-511416f69ae0 moved from Up --> RebootInProgress >>> 2014-08-27 17:22:47,775 INFO >>> [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] >>> (DefaultQuartzScheduler_Worker-54) VM PC53VP0002-2 77a3e6ca-bcaf-4415-a0 >>> 20-34e0f43307d4 moved from Up --> RebootInProgress >>> 2014-08-27 17:22:47,785 INFO >>> [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] >>> (DefaultQuartzScheduler_Worker-54) VM PC53VP0002-4 3430c339-cc89-45e5-af >>> e6-49b217b2598d moved from Up --> RebootInProgress >>> 2014-08-27 17:22:47,846 INFO >>> [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] >>> (DefaultQuartzScheduler_Worker-75) VM PC53VP0002-1 825850ef-e63c-4c99-93 >>> 89-400f1af22e5f moved from Up --> RebootInProgress >>> 2014-08-27 17:22:57,027 INFO [org.ovirt.engine.core.bll.VmPoolMonitor] >>> (DefaultQuartzScheduler_Worker-60) [6e7094ae] VmPool >>> 4f5fe15b-123c-4beb-b596-528747f2 >>> a6ec is missing 4 prestarted Vms, attempting to prestart 4 Vms >>> >>> And after 10mins all vms in the pool are started! >>> >>> Why is VmPoolMonitor attempting to prestart 4 Vms again? >>> >> >> the problem is that the monitor dont take into consideration this status >> (RebootInProgress) > > hm, but RebootInProgress is used during the shutdown phase as well - and then > during the actual boot its unchanged, all the way till VM is reported Up > again. > could it be a problem? > i think not, because even if the vm is shutting down now, its still a running vm,

if we dont want to exceed the user configuration, we can count it as still running, and in the next cycle (5 mins) it will not be counted and we will get a better decision. what do you think?

> > Thanks, > michal > > >> only WaitForLaunch, PoweringUp or Up >> >> could you please open a bug on this? >> >> Thanks! >> >>> Thanks! >>> Michel >>> >>> -- >>> Michel Rode >>> Linux / Unix Consultant & Trainer >>> >>> Mail: rode(a)b1-systems.de >>> >>> B1 Systems GmbH >>> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de >>> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > >