Hi everybody,<br><br>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 &quot;Up&quot; as fast as we&#39;d like. VDSM show the following in the logs:<br>

<br><span style="font-size:11pt;font-family:&quot;Lucida Grande&quot;">Thread-420807::DEBUG::2012-06-06
22:14:47,662::clientIF::54::vds::(wrapper) [10.225.52.7]::call <b>getVmStats </b>with
(&#39;e3b250c9-a5ca-42da-bd8f-245a3ef4bbfb&#39;,) {}<br>
Thread-420807::DEBUG::2012-06-06
22:14:47,663::libvirtvm::222::vm.Vm::(_getDiskStats)
vmId=`e3b250c9-a5ca-42da-bd8f-245a3ef4bbfb`::<b>Disk stats not available<br>
</b>Thread-420807::DEBUG::2012-06-06
22:14:47,663::libvirtvm::251::vm.Vm::(_getDiskLatency)
vmId=`e3b250c9-a5ca-42da-bd8f-245a3ef4bbfb`::<b>Disk latency not available<br></b></span><span style="font-size:11.0pt;font-family:&quot;Lucida Grande&quot;">Thread-420807::DEBUG::2012-06-06
22:14:47,663::clientIF::59::vds::(wrapper) return getVmStats with {&#39;status&#39;:
{&#39;message&#39;: &#39;Done&#39;, &#39;code&#39;: 0}, &#39;statsList&#39;: [{&#39;status&#39;: &#39;Up&#39;, &#39;username&#39;:
&#39;Unknown&#39;, &#39;memUsage&#39;: &#39;0&#39;, &#39;acpiEnable&#39;: &#39;tru<br>
e&#39;, &#39;pid&#39;: &#39;32299&#39;, &#39;displayIp&#39;: &#39;0&#39;, &#39;displayPort&#39;: u&#39;5900&#39;, &#39;session&#39;: &#39;Unknown&#39;,
&#39;displaySecurePort&#39;: u&#39;5901&#39;, &#39;cdrom&#39;:
&#39;/rhev/data-center/c861891c-7011-4209-9871-73c4b4e42560/b1ad8b2c-d2e1-479b-be2e-90fcbe446e86/images/11111111<br>
-1111-1111-1111-111111111111/CorePlus-current.iso&#39;, &#39;pauseCode&#39;: &#39;NOERR&#39;,
&#39;clientIp&#39;: &#39;&#39;, &#39;kvmEnable&#39;: &#39;true&#39;, &#39;network&#39;: {u&#39;vnet0&#39;: {&#39;macAddr&#39;:
u&#39;00:1a:4a:a8:7a:50&#39;, &#39;rxDropped&#39;: &#39;0&#39;, &#39;rxErrors&#39;: &#39;0&#39;, &#39;txDropped&#39;: &#39;0&#39;,
&#39;txRate&#39;: &#39;<br>
0.0&#39;, &#39;rxRate&#39;: &#39;0.0&#39;, &#39;txErrors&#39;: &#39;0&#39;, &#39;state&#39;: &#39;unknown&#39;, &#39;speed&#39;: &#39;1000&#39;,
&#39;name&#39;: u&#39;vnet0&#39;}}, &#39;vmId&#39;: &#39;e3b250c9-a5ca-42da-bd8f-245a3ef4bbfb&#39;,
&#39;monitorResponse&#39;: &#39;0&#39;, &#39;cpuUser&#39;: &#39;0.00&#39;, &#39;disks&#39;: {u&#39;vda&#39;: {&#39;readLatency&#39;:
&#39;0&#39;, &#39;app<br>
arentsize&#39;: &#39;1073741824&#39;, &#39;writeLatency&#39;: &#39;0&#39;, &#39;imageID&#39;:
&#39;38ffdd23-e16d-4cde-a384-3290450fe87f&#39;, &#39;flushLatency&#39;: &#39;0&#39;, &#39;truesize&#39;:
&#39;1073741824&#39;}}, &#39;boot&#39;: &#39;c&#39;, &#39;statsAge&#39;: &#39;1.81&#39;, &#39;cpuIdle&#39;: &#39;100.00&#39;,
&#39;elapsedTime&#39;: &#39;61&#39;, &#39;vmType&#39;:<br>
 &#39;kvm&#39;, &#39;cpuSys&#39;: &#39;0.00&#39;, &#39;timeOffset&#39;: &#39;0&#39;, &#39;appsList&#39;: [], &#39;guestIPs&#39;:
&#39;&#39;, &#39;displayType&#39;: &#39;qxl&#39;, &#39;nice&#39;: &#39;&#39;}]}<br><br>This repeats for about a minute until the VM is finally marked &quot;Up&quot;. Is there any trick we can do to get ovirt to mark the VM &quot;Up&quot; quicker? Perhaps generate some sort of activity on the VM?<br>

<br>Thanks,<br>Andrey<br><br><br></span>