FS#53560 - [libvirt] Regression: libvirt-3.2.0-1 breaks usage of

Attached to Project: Community Packages
Opened by Marius Steffen (Marius_Linux) - Tuesday, 04 April 2017, 10:12 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 07 April 2017, 09:23 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

After upgrading from libvirt-3.1.0-1 to libvirt-3.2.0-1, using <vendor_id [...] /> for setting the Hyper-V vendor inside an libvirt xml does no longer work. When trying to start the QEMU guest, either using virsh or virt-manager, libvirt complains:

error: Failed to start domain creative_virt
error: internal error: unknown CPU feature __kvm_hv_vendor_id

resulting in the inability to start the VM.

Additional info:
* libvirt-3.2.0-1
* Domain XML is attached


Steps to reproduce:
1. Install libvirt-3.2.0-1
2. Restart libvirtd
3. Try to run QEMU VM containing the tag described above
   domain.xml (7 KiB)
This task depends upon

Closed by  Sergej Pupykin (sergej)
Friday, 07 April 2017, 09:23 GMT
Reason for closing:  Fixed
Additional comments about closing:  applied patch
https://libvirt.org/git/?p=libvirt.git;a =commit;h=ae102b5d7bccd29bc6015a3e0acefe aa90d097ac
Comment by Bart Willems (hersenbeuker) - Tuesday, 04 April 2017, 16:24 GMT
Same problem here. I need this vendor ID string to enable my nvidia drivers. F*ck you nvidia!
Comment by Ron Festa (ronoverdrive) - Tuesday, 04 April 2017, 23:38 GMT
Can confirm, libvirt 3.2 breaks vendor_id feature.
Comment by Thilo Berndt (schlehmil) - Wednesday, 05 April 2017, 17:46 GMT
Confirmed here as well
Comment by Marius Steffen (Marius_Linux) - Thursday, 06 April 2017, 14:32 GMT
This bug has been fixed and merged in the v3.2-maint branch upstream about 2hrs ago:
https://www.redhat.com/archives/libvir-list/2017-April/msg00334.html
https://libvirt.org/git/?p=libvirt.git;a=commit;h=ae102b5d7bccd29bc6015a3e0acefeaa90d097ac

As that's the maintenance branch, I think a recompilation with the new commits of Arch's libvirt* packages shouldn't be a problem?

Loading...