Unable to specify hw_vif_model image metadata for Virtuozzo hypervisor virt_type=parallels

Bug #1635230 reported by Maxim Nestratov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Maxim Nestratov

Bug Description

If you specify hw_vif_model in image metadata when you use Virtuozzo (libvirt virt_type=parallels), then a UnsupportedHardware exception will be thrown.

2016-08-04 19:11:44.880 16260 ERROR nova.compute.manager [req-8b5cdf08-e3b3-4d0d-9d1c-a1ff10daee71 690eedf97d024da8974029784c26cff1 4a7ea1a081334814b7f45b5950657564 - - -] [instance: 63ae37d5-a377-4ff8-9ea8-2bfc86565415] Instance failed to spawn
[..]
2016-08-04 19:11:44.880 16260 ERROR nova.compute.manager [instance: 63ae37d5-a377-4ff8-9ea8-2bfc86565415] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/vif.py", line 81, in is_vif_model_valid_for_virt
2016-08-04 19:11:44.880 16260 ERROR nova.compute.manager [instance: 63ae37d5-a377-4ff8-9ea8-2bfc86565415] raise exception.UnsupportedVirtType(virt=virt_type)

Changed in nova:
assignee: nobody → Maxim Nestratov (mnestratov)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/365943
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e5e4dfcfdb918b57dcbd3e3cfb171e3b70e3c701
Submitter: Jenkins
Branch: master

commit e5e4dfcfdb918b57dcbd3e3cfb171e3b70e3c701
Author: Maxim Nestratov <email address hidden>
Date: Tue Sep 6 11:33:05 2016 +0300

    libvirt: add supported vif types for virtuozzo virt_type

    Enable vif driver configuring for virtuozzo and make configuration
    parameter use_virtio_for_bridges be usable for virtuozzo hypervisor.

    Change-Id: Ied17a5406d5625f1e9f704e5b9b46d300f2870c2
    Closes-Bug: #1635230

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 15.0.0.0b1

This issue was fixed in the openstack/nova 15.0.0.0b1 development milestone.

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.