canonical-server team mailing list archive

[Launchpad Bug Tracker <344400@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

Since updating to libvirt 0.6.1-0ubuntu1, my VMs intermittently fail to
start up.

Here is a log of a failure:

[Thu, 12 Mar 2009 17:08:15 virt-manager 15428] DEBUG (engine:496) Starting vm 'sec-gutsy-amd64'.
[Thu, 12 Mar 2009 17:08:18 virt-manager 15428] DEBUG (error:76) Uncaught Error: Error starting domain: internal error unable to start guest:  : Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 498, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 508, in startup
    self.vm.create()
  File "/usr/lib/python2.6/dist-packages/libvirt.py", line 287, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error unable to start guest: 

This usually happens after a reboot, upon starting a VM for the first
time, or when I have high system usage (ie compiling).

The included debdiff fixes the problem for me by increasing the 3 second
timeout for a vm to start. Under load, I've seen my VMs take up to 8-10
seconds to start.

** Affects: libvirt (Ubuntu)
     Importance: Undecided
     Assignee: Canonical Server Team (canonical-server)
         Status: Confirmed


** Tags: regression-potential
-- 
libvirtError: internal error unable to start guest
https://bugs.launchpad.net/bugs/344400
You received this bug notification because you are a member of Canonical Server Team, which is a bug assignee.