FS#63183 - [libvirt] regression, it's once again looking for a hard coded /usr/bin/kvm-spice
Attached to Project:
Community Packages
Opened by Mitch Muncrief (muncrief) - Saturday, 13 July 2019, 16:45 GMT
Last edited by freswa (frederik) - Wednesday, 14 October 2020, 20:50 GMT
Opened by Mitch Muncrief (muncrief) - Saturday, 13 July 2019, 16:45 GMT
Last edited by freswa (frederik) - Wednesday, 14 October 2020, 20:50 GMT
|
Details
There appears to be a simple regression in the libvirt
package where it's once again hard coding /usr/bin/kvm-spice
instead of using /usr/bin/qemu-system-x86_64. This causes
libvirtd to report that it can't find /usr/bin/kvm-spice and
of course VMs will not work.
I remember this happening some time before, and the solution is quite simple. Just execute the following command in a terminal: sudo ln -s /usr/bin/qemu-system-x86_64 /usr/bin/kvm-spice By the way I looked through a backup from a few months ago to see if kvm-spice was linked before but it wasn't. So something has changed in either qemu or libvirt so that the appropriate binary is no longer identified. And as I mentioned earlier I vaguely remember this problem from before and believe the problem was that /usr/bin/kvm-spice had somehow been hard coded into libvirt. However I have no way of knowing for sure if it's the same problem. |
This task depends upon
Comment by Robin Broda (coderobe) -
Wednesday, 06 May 2020, 21:57 GMT
Is this still an issue with 6.3.0 (currently in
[community-testing])?