Re: qemu-xen is unavailable
Hello, On Wed, Jan 05, 2022 at 04:27:56PM +, Anthony PERARD wrote: > The bug here is that libxl shouldn't print this message for PVH guest > because it's confusing. It also does it for PV guests, again if no qemu is installed (or needed). I squash it by adding: device_model_version="qemu-xen" device_model_override="/bin/true" do the domU config files. Cheers, Andy
Re: qemu-xen is unavailable
On Wed, 5 Jan 2022, Anthony PERARD wrote: > Looking at the original email, the domain config file has type="pvh", so > I don't think qemu is actually needed. And the domain is starting fine, > so this message isn't really needed and would be a bug I guess. Thanks for responding. Indeed, the "qemu" package is not installed on this machine, and looking closer, the Alpine folks did something to their Xen/Qemu packagesp[0][1]. I can't check right now but I'll test if the warning goes away with the "qemu" package installed. Thanks again, Christian. [0] https://git.alpinelinux.org/aports/commit/?id=9f064ced3 [1] https://git.alpinelinux.org/aports/commit/?id=55d655af7 > I think it comes from libxl trying to figure out which QEMU to use even > if it isn't going to be needed. And since there's no qemu to be found, > the message is printed, even when qemu isn't needed. > > I guess you have this message because you didn't install a qemu package > (or qemu-xen), but you don't need the package as you are only starting a > PVH guest. > > The bug here is that libxl shouldn't print this message for PVH guest > because it's confusing. -- BOFH excuse #244: Your cat tried to eat the mouse.
Re: qemu-xen is unavailable
CC xen-devel On Tue, Jan 04, 2022 at 11:52:21AM +, George Dunlap wrote: > > On Sun, 19 Dec 2021, Christian Kujau wrote: > > > # xl create -f /etc/xen/debian.cfg > > > Parsing config from /etc/xen/debian.cfg > > > libxl: info: libxl_create.c:121:libxl__domain_build_info_setdefault: > > qemu-xen is unavailable, using qemu-xen-traditional instead: No such file > > or directory Looking at the original email, the domain config file has type="pvh", so I don't think qemu is actually needed. And the domain is starting fine, so this message isn't really needed and would be a bug I guess. I think it comes from libxl trying to figure out which QEMU to use even if it isn't going to be needed. And since there's no qemu to be found, the message is printed, even when qemu isn't needed. I guess you have this message because you didn't install a qemu package (or qemu-xen), but you don't need the package as you are only starting a PVH guest. The bug here is that libxl shouldn't print this message for PVH guest because it's confusing. Thanks, -- Anthony PERARD
