← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1427977] Re: Failed to launch new VM after changing "nova.conf" for specifying target cpu_model

 

Haha, closing the bug then :)

** Changed in: nova
       Status: In Progress => 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/1427977

Title:
  Failed to launch new VM after changing "nova.conf" for specifying
  target cpu_model

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Version: stable/icehouse

  Description:
  Change the Nova config file "nova.conf" for specifying the target cpu_model of Penryn as follows:

  cpu_mode = custom
  cpu_model = Penryn
  virt_type = kvm|qemu

  After that, restart Nova services.

  Eventually, try launching new VM, but it is failed with the following
  Traceback:

  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f] Traceback (most recent call last):
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]   File "/opt/stack_stable_juno/nova/nova/compute/manager.py", line 2231, in _build_resources
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]     yield resources
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]   File "/opt/stack_stable_juno/nova/nova/compute/manager.py", line 2101, in _build_and_run_instance
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]     block_device_info=block_device_info)
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]   File "/opt/stack_stable_juno/nova/nova/virt/libvirt/driver.py", line 2619, in spawn
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]     write_to_disk=True)
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]   File "/opt/stack_stable_juno/nova/nova/virt/libvirt/driver.py", line 4150, in _get_guest_xml
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]     context)
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]   File "/opt/stack_stable_juno/nova/nova/virt/libvirt/driver.py", line 3936, in _get_guest_config
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]     flavor, CONF.libvirt.virt_type)
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]   File "/opt/stack_stable_juno/nova/nova/virt/libvirt/vif.py", line 352, in get_config
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f]     _("Unexpected vif_type=%s") % vif_type)
  2015-03-04 17:24:39.175 31397 TRACE nova.compute.manager [instance: 3987b178-2049-4421-9951-86d90c7d9b3f] NovaException: Unexpected vif_type=binding_failed

  
  Furthermore, the created folder "OPEN_STACK_INSTALL_DIR/data/drives/sdb1" is left orphaned

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


References