[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

qemu-xen is unavailable


  • To: xen-users@xxxxxxxxxxxxxxxxxxxx
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
  • Date: Sun, 19 Dec 2021 23:04:38 +0100 (CET)
  • Authentication-results: mail.nerdbynature.de; dmarc=fail (p=none dis=none) header.from=nerdbynature.de
  • Delivery-date: Sun, 19 Dec 2021 22:22:45 +0000
  • List-id: Xen user discussion <xen-users.lists.xenproject.org>

Hi,

after upgrading from from Xen 4.15.1 to 4.16.0 (Dom0 running on Alpine 
Linux, Edge), the following is printed when starting a DomU:

-------------------------
# uname -rm
5.15.10-0-lts x86_64

# 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
-------------------------

The domain is started just fine, no ill effects so far. But I'm wondering 
on the meaning of that message. I found a patch[0] from 2019 where this 
message got introduced, but the comment above just states the same, but I 
can't figure out _why_ qemu-xen is unavailable.

Does anyone has an idea what this is all about?

Thanks,
Christian.

[0] 
https://patchwork.kernel.org/project/xen-devel/patch/20190510152047.17299-1-olaf@xxxxxxxxx/

# grep ^[a-z] /etc/xen/debian.cfg
type     = "pvh"
kernel   = "/usr/lib/grub-xen/grub-i386-xen_pvh.bin"
boot     = "cd"
name     = "debian"
uuid     = "c0673479-44e0-4b13-8eeb-145c68348603"
memory   = 1024
maxmem   = 4096
vcpus    = 2
maxvcpus = 4
vif   = [ 'mac=00:16:3E:AB:CD:01, vifname=debian', ]
disk  = [ 'format=raw, vdev=xvda, access=rw, target=/dev/vg0/debian-root', ]
vnc        = 1
vnclisten  = "127.0.0.1"
vncdisplay = "1"
vncpasswd  = "*****"

-- 
BOFH excuse #431:

Borg implants are failing



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.