Created attachment 881656 [details] error of virt-manager-4.1.0 on January 1st New install on new hardware to be used for Xen: ryzwork ~ # uname -a Linux ryzwork 6.1.67-gentoo-x86_64 #1 SMP PREEMPT_DYNAMIC Fri Dec 29 17:18:40 PST 2023 x86_64 AMD Ryzen 9 7950X 16-Core Processor AuthenticAMD GNU/Linux ryzwork ~ # I installed virt-manager 4.1.0. in Dom0. In an Xfce4 session on Dom0 as root I launched from a console: virt-manager. The Virtual Machine Manager window appeared on my Xfce4 desktop. I had previously started the /etc/init.d/libvirtd. After specifying everything for a simple MS Windows 7 install, I encountered this error message in a child dialog: Unable to complete install: 'unsupported configuration: emulator '/usr/lib/xen/bin/qemu-system-i386' not found A screenshot of the error message dialog plus a console showing the location of the file not found (in another location) is attached as Screenshot_2024-01-01_17-38-21.png The file, qemu-system-i386, the dialog said it could not find under /usr/lib/xen/bin does, in fact, exist under /usr/libexec/xen/bin as the screenshots show. ryzwork ~ # date; eix virt-manager Sun Jan 7 12:56:46 PM PST 2024 [I] app-emulation/virt-manager Available versions: 4.1.0^t (~)4.1.0-r1^t **9999*l^t {gui policykit sasl test PYTHON_SINGLE_TARGET="python3_10 python3_11"} Installed versions: 4.1.0-r1^t(11:22:49 AM 01/07/2024)(gui policykit -sasl -test PYTHON_SINGLE_TARGET="python3_11 -python3_10") Homepage: https://virt-manager.org https://github.com/virt-manager/virt-manager Description: A graphical tool for administering virtual machines ryzwork ~ # Today, January 7th, I installed 4.1.0-r1 just in case the difference in "r1" handled the problem I previously encountered. I ran the same attempt and got the same error message. (Note: I changed the color of the root's Xfce4 desktop to yellow from the previous green.) A screenshot showing the same error message will be attached as file Screenshot_2024-01-07_12-50-08.png and shows the same problem. I have preserved the build trees from /var/tmp/portage of both virt-manager-4.1.0-r1 AND qemu-8.0.4 into an isolated location in case anything from either is needed. I rebuilt qemu adding the key words spice usbredir. I have not rebooted and suspect the problem is something was misdirected during an install, or some pointer or PATH variable is missing. The "Add an attachment" facility seems to limit 1 attachment on the initial opening of a bug, I'll attach the other screenshot forthwith.
Created attachment 881657 [details] error of virt-manager-4.1.0-r1 on January 7th
xen@, I'm not familiar with libvirt/virt-manager with the Xen hypervisor; could it be that there's some PATH manipulation missing somewhere?
(In reply to John Helmert III from comment #2) > xen@, I'm not familiar with libvirt/virt-manager with the Xen hypervisor; > could it be that there's some PATH manipulation missing somewhere? Yes, some path setting must be afoul. Perhaps I'm the first person to try and install and run virt-manager on Xen on Gentoo? I did not want to tinker just in case anyone fielding this bug would want me to try something. The environment is extremely new and pristine. Let me know what you'd like me to try.
I did two things, the first of which may be surperfluous; 1) in a console in root's Xfce3 desktop on Dom0, I executed: export PATH="$PATH:/usr/libexec/xen/bin" I launched in the modified console: virt-manager The Virtual Manager window appears and I went through the same steps I did before and go the same error message. 2) In a separate console, I created a soft link as follows: ln -s /usr/libexec/xen /usr/lib/xen I then returned to my pending session of Virtual Manager and proceeded with an installatin. A child window opened up and I successfully installed MS Windows7 and after creating an account successfully opened NotePad and saved a file. While this is cheating, it confirms the believe that the problem arises from a missing path specification. As far as I am concerned, the above approach is a "Works For Me".
Ah, good to know! I think xen@ should handle the PATH then...
