Mailing List Archive

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

FWIW, something like this is also mentioned in the Release Notes[0]:

| The old qemu-xen-traditional stubdomain device model (ioemu-stubdom)
| is deprecated and no longer built by default.

But I don't have any device_model_version settings in my configuration. In
fact, /etc/xen/xl.conf has not adjustments at all, should be all
"standard" (according to Alpine Linux's configuration, of course).

Christian.

# xl info
host : xxx
release : 5.15.10-0-lts
version : #1-Alpine SMP Fri, 17 Dec 2021 10:25:35 +0000
machine : x86_64
nr_cpus : 8
max_cpu_id : 7
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 2195.024
hw_caps : bfebfbff:77bae3bf:28100800:00000001:00000001:00000281:00000000:00000100
virt_caps : pv hvm hap shadow gnttab-v1 gnttab-v2
total_memory : 15949
free_memory : 1799
sharing_freed_memory : 0
sharing_used_memory : 0
outstanding_claims : 0
free_cpus : 0
xen_major : 4
xen_minor : 16
xen_extra : .0
xen_version : 4.16.0
xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p
hvm-3.0-x86_64
xen_scheduler : credit2
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset :
xen_commandline : dom0_mem=512M,max:1024M ucode=scan
cc_compiler : gcc (Alpine 11.2.1_git20211128) 11.2.1 20211128
cc_compile_by : buildozer
cc_compile_domain :
cc_compile_date : Wed Dec 15 22:02:49 UTC 2021
build_id : 5950bd849bf4b1a436abad47edb6b9a752a2fc04
xend_config_format : 4

--
BOFH excuse #118:

the router thinks its a printer.

I think Anthony uses Arch; Anthony, any idea what's going on here?

Thanks,
-George

On Mon, Dec 20, 2021 at 8:54 AM Christian Kujau <lists@nerdbynature.de>
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
>
> FWIW, something like this is also mentioned in the Release Notes[0]:
>
> | The old qemu-xen-traditional stubdomain device model (ioemu-stubdom)
> | is deprecated and no longer built by default.
>
> But I don't have any device_model_version settings in my configuration. In
> fact, /etc/xen/xl.conf has not adjustments at all, should be all
> "standard" (according to Alpine Linux's configuration, of course).
>
> Christian.
>
> # xl info
> host : xxx
> release : 5.15.10-0-lts
> version : #1-Alpine SMP Fri, 17 Dec 2021 10:25:35 +0000
> machine : x86_64
> nr_cpus : 8
> max_cpu_id : 7
> nr_nodes : 1
> cores_per_socket : 4
> threads_per_core : 2
> cpu_mhz : 2195.024
> hw_caps :
> bfebfbff:77bae3bf:28100800:00000001:00000001:00000281:00000000:00000100
> virt_caps : pv hvm hap shadow gnttab-v1 gnttab-v2
> total_memory : 15949
> free_memory : 1799
> sharing_freed_memory : 0
> sharing_used_memory : 0
> outstanding_claims : 0
> free_cpus : 0
> xen_major : 4
> xen_minor : 16
> xen_extra : .0
> xen_version : 4.16.0
> xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p
> hvm-3.0-x86_64
> xen_scheduler : credit2
> xen_pagesize : 4096
> platform_params : virt_start=0xffff800000000000
> xen_changeset :
> xen_commandline : dom0_mem=512M,max:1024M ucode=scan
> cc_compiler : gcc (Alpine 11.2.1_git20211128) 11.2.1 20211128
> cc_compile_by : buildozer
> cc_compile_domain :
> cc_compile_date : Wed Dec 15 22:02:49 UTC 2021
> build_id : 5950bd849bf4b1a436abad47edb6b9a752a2fc04
> xend_config_format : 4
>
> --
> BOFH excuse #118:
>
> the router thinks its a printer.
>
>

On Tue, 4 Jan 2022, 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
> >
> > FWIW, something like this is also mentioned in the Release Notes[0]:
> >
> > | The old qemu-xen-traditional stubdomain device model (ioemu-stubdom)
> > | is deprecated and no longer built by default.
> >
> > But I don't have any device_model_version settings in my configuration. In
> > fact, /etc/xen/xl.conf has not adjustments at all, should be all
> > "standard" (according to Alpine Linux's configuration, of course).
>
> I think Anthony uses Arch; Anthony, any idea what's going on here?

This was on Alpine Linux, not Arch, so the userbase may be even smaller
here, although I thought Alpine as a Xen Dom0 was a pretty good fit
because of its small installation size and reduced complexity, maybe?

Thanks,
Christian.

> >
> > Christian.
> >
> > # xl info
> > host : xxx
> > release : 5.15.10-0-lts
> > version : #1-Alpine SMP Fri, 17 Dec 2021 10:25:35 +0000
> > machine : x86_64
> > nr_cpus : 8
> > max_cpu_id : 7
> > nr_nodes : 1
> > cores_per_socket : 4
> > threads_per_core : 2
> > cpu_mhz : 2195.024
> > hw_caps :
> > bfebfbff:77bae3bf:28100800:00000001:00000001:00000281:00000000:00000100
> > virt_caps : pv hvm hap shadow gnttab-v1 gnttab-v2
> > total_memory : 15949
> > free_memory : 1799
> > sharing_freed_memory : 0
> > sharing_used_memory : 0
> > outstanding_claims : 0
> > free_cpus : 0
> > xen_major : 4
> > xen_minor : 16
> > xen_extra : .0
> > xen_version : 4.16.0
> > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p
> > hvm-3.0-x86_64
> > xen_scheduler : credit2
> > xen_pagesize : 4096
> > platform_params : virt_start=0xffff800000000000
> > xen_changeset :
> > xen_commandline : dom0_mem=512M,max:1024M ucode=scan
> > cc_compiler : gcc (Alpine 11.2.1_git20211128) 11.2.1 20211128
> > cc_compile_by : buildozer
> > cc_compile_domain :
> > cc_compile_date : Wed Dec 15 22:02:49 UTC 2021
> > build_id : 5950bd849bf4b1a436abad47edb6b9a752a2fc04
> > xend_config_format : 4
> >
> > --
> > BOFH excuse #118:
> >
> > the router thinks its a printer.
> >
> >
>

--
BOFH excuse #54:

Evil dogs hypnotised the night shift

CC xen-devel

On Tue, Jan 04, 2022 at 11:52:21AM +0000, 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

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.

Hello,

On Wed, Jan 05, 2022 at 04:27:56PM +0000, 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