How to fix error 'libxenlight failed to create a new domain'?
Maybe this will work. Yet to try.
So it looks like there is a need to add the following to a file named usr.sbin.libvirtd
. In commandline, updatedb (sudo updatedb
) and then use locate to find that file (locate usr.sbin.libvirtd
).
Edit it with gedit or nano or vi or another applicable text editor
Under these lines:
/lib/udev/scsi_id PUx,
/lib/udev/scsi_id PUx,
/usr/lib/xen-common/bin/xen-toolstack PUx,
Add:
/usr/lib/xen-*/bin/pygrub PUx,
Taken by and large from:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1326003/comments/2
Related videos on Youtube
Guest
Updated on September 18, 2022Comments
-
Guest over 1 year
Using Virt-Manager 1.2.1 on 14.04. / Xen 4.4 from repos. Cannot create VM machine because this error crops up on virt-manager.
This is after editing
/etc/xen/xend-config.sxp
to allow virt-manager to work and restarting libvirt and xen services.Closest clue is from the OpenSuse forums which suggest Apparmor and libvirtd are in conflict. Solution seemed to be to disable Apparmor. Apparmor does not seem installed though.
-
Christopher Angulo-Bertram almost 8 yearsWhere is the virtual host installed?
-
Christopher Angulo-Bertram almost 8 yearsCan you add the exact error message you are getting?
-
Christopher Angulo-Bertram almost 8 yearsSorry, I was not seeing the trees due to the forest. Never mind my last comment.
-
Christopher Angulo-Bertram almost 8 yearsBetter comment, have you tried this answer? askubuntu.com/questions/466292/virt-manager-cant-connect-to-xen
-
Guest almost 8 yearsThanks. Yes, tried that link. Virt-manager does connect and works passed that point and gets stuck later down the line with above error. In short, didn't help.
-
Guest almost 8 yearsIt appears to be a permission issue. Others have raised this same issue. Have a look:\n bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1326003 \n forums.fedoraforum.org/archive/index.php/t-288781.html \
-
Guest almost 8 years
-
Guest almost 8 yearsLaunchapad link adds a clue that pygrub might not have enough permissions. This is an old 2014 bug. Looks fixed. Maybe another file has been affected the same way?
-