yahoo-eng-team team mailing list archive

[Vish Ishaya <vishvananda@xxxxxxxxx>]

Ok i think my issue was due to incompatible versions of libvirt and
qemu. That said it seems like passing in the arch element is probably
incorrect.

** Changed in: nova
       Status: New => Invalid

** Changed in: nova/folsom
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1134703

Title:
  Newer libvirt fails with host-model

Status in OpenStack Compute (Nova):
  Invalid
Status in OpenStack Compute (nova) folsom series:
  Invalid

Bug description:
  Newer installs of libvirt reject our host-model xml with the following
  error:

  $ sudo virsh -d0 start instance-00000002
  start: domain(optdata): instance-00000002
  start: found option <domain>: instance-00000002
  start: <domain> trying as domain NAME
  error: Failed to start domain instance-00000002
  error: internal error Cannot find suitable CPU model for given data
  Manually running cpu-compare gives the exact error:

  $ sudo virsh cpu-compare libvirt.xml

  error: Failed to compare host CPU with libvirt.xml
  error: XML error: 'arch' element element cannot be used inside 'cpu' element with 'match' attribute'

  According to the following patch, I believe our xml generation is
  incorrect and older versions of libvirt were silently ignoring the
  error:

  http://osdir.com/ml/libvir-list/2010-07/msg00240.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1134703/+subscriptions