[Users] Getting ovirt to update VMs to "Up" state sooner

[Dan Kenigsberg]

On Thu, Jun 07, 2012 at 12:26:30PM +0300, Yaniv Kaul wrote:
> On 06/07/2012 05:23 AM, Andrey F. wrote:
> >Hi everybody,
> >
> >We are trying to optimize our continuous integration system around
> >our ovirt-management software (i.e. we call into the ovirt apis to
> >create VMs, do funny stuff with the VMs, etc.). For our tests, we
> >deployed a VM that boots extremely quickly (2 seconds) in hoping
> >to speed up our tests. Unfortunately, ovirt is not updating the
> >state of the VM to "Up" as fast as we'd like. VDSM show the
> >following in the logs:
> >
> >Thread-420807::DEBUG::2012-06-06
> >22:14:47,662::clientIF::54::vds::(wrapper) [10.225.52.7]::call
> >*getVmStats *with ('e3b250c9-a5ca-42da-bd8f-245a3ef4bbfb',) {}
> >Thread-420807::DEBUG::2012-06-06
> >22:14:47,663::libvirtvm::222::vm.Vm::(_getDiskStats)
> >vmId=`e3b250c9-a5ca-42da-bd8f-245a3ef4bbfb`::*Disk stats not
> >available
> >*Thread-420807::DEBUG::2012-06-06
> >22:14:47,663::libvirtvm::251::vm.Vm::(_getDiskLatency)
> >vmId=`e3b250c9-a5ca-42da-bd8f-245a3ef4bbfb`::*Disk latency not
> >available
> >*Thread-420807::DEBUG::2012-06-06
> >22:14:47,663::clientIF::59::vds::(wrapper) return getVmStats with
> >{'status': {'message': 'Done', 'code': 0}, 'statsList':
> >[{'status': 'Up', 'username': 'Unknown', 'memUsage': '0',

As you can see, Vdsm reports 'Up' by now. It should have reported
'Powering up' for 60 seconds (unless an internal guest agent reports
that it is up before that).

While the Vm is not reported as 'Up' what is its reproted state?

> 
> Do you have the guest agent installed on the guest?
> Y.
>