qemu-system-x86-xen default path should match xen libexec_bin path
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libvirt (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| qemu (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
Hello to everyone.
I've tried to create a new vm called "windows-10" on the ubuntu 20.04 using virt-manager and the operation does not go well,because the error : "can't complete the installation : internal error : libxenlight failed to create new domain". The steps to reproduce this error are the following:
Step 1 - installing packages:
sudo apt install xen-hypervisor xen-utils libvirt-
step 2: enable the nvidia driver metapackage da nvidia-driver-440 from "sofware and updates / more drivers" (this step is not mandatory)
step 3 : detaching the nvidia devices from the host and attaching to xen pciback (this step is not mandatory)
root@zioma-
Binding 0000:01:00.0 to pciback
root@zioma-
Unbinding 0000:01:00.1 from snd_hda_intel
Binding 0000:01:00.1 to pciback
root@zioma-
Unbinding 0000:01:00.2 from xhci_hcd
Binding 0000:01:00.2 to pciback
root@zioma-
Unbinding 0000:01:00.3 from nvidia-gpu
Binding 0000:01:00.3 to pciback
step 4 : open virt-manager and try to configure a new xen connection and vm with these parameters
a) hypervisor = fullvirt
b) architecture = x86_64
c) emulator = /usr/lib/
d) firmware custom = /usr/lib/
e) added SCSI disk 1 = /dev/sdc ; where is installed my windows 10,which use an MBR partition scheme
f) memory allocated = 2000 MB ; max memory = 2000
press on start installation and you will get the error : "can't complete the installation : internal error : libxenlight failed to create new domain".
It seems that this bug is correlated with this :
https:/
Related branches
- Rafael David Tinoco (community): Approve
- Canonical Server: Pending requested
- Canonical Server packageset reviewers: Pending requested
-
Diff: 150 lines (+105/-0)5 files modifieddebian/changelog (+10/-0)
debian/patches/lp-1890154-s390x-protvirt-allow-to-IPL-secure-guests-with-no-re.patch (+52/-0)
debian/patches/series (+2/-0)
debian/patches/ubuntu/lp-1883984-target-s390x-Fix-SQXBR.patch (+37/-0)
debian/rules (+4/-0)
| Christian Ehrhardt (paelzer) wrote | #1 |
| Christian Ehrhardt (paelzer) wrote | #2 |
| summary: |
- can't complete the installation : internal error : libxenlight failed to - create new domain + qemu-system-x86-xen default path should match xen libexec_bin path |
| Changed in libvirt (Ubuntu): | |
| status: | New → Invalid |
| Changed in qemu (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Christian Ehrhardt (paelzer) wrote | #3 |
| Christian Ehrhardt (paelzer) wrote | #4 |
| Marietto (marietto2008) wrote | #5 |
| Launchpad Janitor (janitor) wrote | #6 |
| Changed in qemu (Ubuntu): | |
| status: | Triaged → Fix Released |
The defaults of virt-manager for xen are not 100% compatible for Ubuntu's Xen.
I've shown that when discussing about the last bug in my example how to get it working I mentioned how to adapt (c) of your list above.
Get this fixed by:
1. Install the qemu build you need for yen
apt install qemu-system-x86-xen
2a. set the emulator path to /usr/bin/
OR
2b. link the expected to the real path (avoids that you'd need to do this for every domain)
sudo ln -s /usr/bin/
One would either need to move the xen default paths in src:xen or teach virt-manager about better defaults. This moved around so much for xen I'm even unsure which component sets the wrong default.
Was at /usr/lib/
Since it is listed in the capabilities probing result I'd even expect virt-manager gets it from libvirt - to libvirt might be the right source package of this after all. But since xen was demoted that is low prio - happy to help thou if someone of the community steps up providing a fix after debugging where the probe results gets the wrong path.