Unable to start EUC instances - no supported architecture for os type 'hvm'

Bug #452572 reported by Mathias Gug
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
Medium
Dustin Kirkland 

Bug Description

Sometimes the NC is unable to start instances. The error in the nc.log file points to "no supported architecture for os type 'hvm'". The theory is that eucalyptus starts and connects to libvirt when the latter is not ready yet.

The current workaround is to restart libvirt and then eucalyptus-nc.

Mathias Gug (mathiaz)
Changed in eucalyptus (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Matt Zimmerman (mdz) wrote :

Dan says this is the same root cause as bug 446036

Changed in eucalyptus (Ubuntu):
assignee: nobody → Dustin Kirkland (kirkland)
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 1.6.2~bzr1120-0ubuntu4

---------------
eucalyptus (1.6.2~bzr1120-0ubuntu4) lucid; urgency=low

  [ Thierry Carrez ]
  * debian/*publication.upstart: Start publication jobs when eth0 is up, and
    never stop them to work around The Upstart Bug (LP: #503850)

  [ Dustin Kirkland ]
  * debian/control, debian/eucalyptus-nc.upstart: (LP: #446036, #452572)
    - add a versioned depends for eucalyptus-nc on a new version
      of libvirt-bin that starts using upstart
    - start eucalyptus-nc on started libvirt-bin
 -- Dustin Kirkland <email address hidden> Wed, 06 Jan 2010 19:16:01 -0600

Changed in eucalyptus (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.