Summary: | app-emulation/virt-manager-4.1.0: emulator '/usr/lib/xen/bin/qemu-system-i386' not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John L. Poole <prestopoole> |
Component: | Current packages | Assignee: | Gentoo Xen Devs <xen> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | jstein, xen |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
error of virt-manager-4.1.0 on January 1st
error of virt-manager-4.1.0-r1 on January 7th |
Description
John L. Poole
2024-01-07 21:22:14 UTC
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... |