Pkg xen devel - Jan 2019 - Bug#919879: xen-utils-common: no module named fsimage in log

Package: xen-utils-common
Version: 4.11.1-1
Severity: important

Dear Maintainer,

I tried to start a newly created guest, and the following happened:

root at xen1:~# xl create /etc/xen/registry.cfg 
Parsing config from /etc/xen/registry.cfg
libxl: error: libxl_bootloader.c:649:bootloader_finished: Domain 4:bootloader
failed - consult logfile /var/log/xen/bootloader.4.log
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [27494]
exited with error status 1
libxl: error: libxl_create.c:1266:domcreate_rebuild_done: Domain 4:cannot
(re-)build domain: -3
libxl: error: libxl_domain.c:1034:libxl__destroy_domid: Domain 4:Non-existant
domain
libxl: error: libxl_domain.c:993:domain_destroy_callback: Domain 4:Unable to
destroy guest
libxl: error: libxl_domain.c:920:domain_destroy_cb: Domain 4:Destruction of
domain failed
root at xen1:~#  tail -50 /var/log/xen/bootloader.4.log
Traceback (most recent call last):
  File "/usr/lib/xen-4.11/bin/pygrub", line 23, in <module>
    import fsimage
ImportError: No module named fsimage

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xen-utils-common depends on:
ii  libc6           2.28-5
ii  libxenstore3.0  4.11.1~pre.20180911.5acdd26fdc+dfsg-5
ii  lsb-base        10.2018112800
ii  python          2.7.15-3
ii  ucf             3.0038+nmu1
ii  udev            240-2
ii  xenstore-utils  4.11.1~pre.20180911.5acdd26fdc+dfsg-5

xen-utils-common recommends no packages.

xen-utils-common suggests no packages.

-- Configuration Files:
/etc/xen/xl.conf changed:
autoballoon="0"


-- no debconf information

Hi Ralph,

On 1/20/19 1:44 PM, Ralph Aichinger wrote:
> [...]
> 
> root at xen1:~# xl create /etc/xen/registry.cfg 
> Parsing config from /etc/xen/registry.cfg
> libxl: error: libxl_bootloader.c:649:bootloader_finished: Domain
4:bootloader failed - consult logfile /var/log/xen/bootloader.4.log
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader
[27494] exited with error status 1
> libxl: error: libxl_create.c:1266:domcreate_rebuild_done: Domain 4:cannot
(re-)build domain: -3
> libxl: error: libxl_domain.c:1034:libxl__destroy_domid: Domain
4:Non-existant domain
> libxl: error: libxl_domain.c:993:domain_destroy_callback: Domain 4:Unable
to destroy guest
> libxl: error: libxl_domain.c:920:domain_destroy_cb: Domain 4:Destruction of
domain failed
> root at xen1:~#  tail -50 /var/log/xen/bootloader.4.log
> Traceback (most recent call last):
>   File "/usr/lib/xen-4.11/bin/pygrub", line 23, in <module>
>     import fsimage
> ImportError: No module named fsimage
Thanks for your report.

pygrub is indeed currently broken due to some libraries that got
renamed. Bug 912381 [0] is also tracking this.

Getting this fixed is on the TODO list for the Buster release [1].

However, it is also recommended to switch to the grub2 bootloader
instead which can boot PV and also PVH guests (with Debian Linux 4.19
kernel package) right now.

In the domU you need grub-xen [2] and in the dom0 you need grub-xen-host
[3]. A 32-bit or 64-bit PV domU would be started by either
grub-i386-xen.bin or grub-x86_64-xen.bin, and all PVH can be started
with the new grub-i386-xen_pvh.bin.

The domU will need to have a grub configuration file pointing to the
installed kernel image. No boot sector etc is needed.

See bug 912381 [4] for some more comments.

Hans

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912381
[1]
https://alioth-lists.debian.net/pipermail/pkg-xen-devel/2019-January/007539.html
[2] https://packages.debian.org/buster/grub-xen
[3] https://packages.debian.org/buster/grub-xen-host
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912381#63

Your message dated Fri, 22 Feb 2019 16:37:31 +0000
with message-id <E1gxDpL-000AIs-O6 at fasolo.debian.org>
and subject line Bug#912381: fixed in xen 4.11.1+26-g87f51bf366-2
has caused the Debian Bug report #912381,
regarding xen-utils-common: no module named fsimage in log
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
912381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912381
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Ralph Aichinger <ra at pi.h5.or.at>
Subject: xen-utils-common: no module named fsimage in log
Date: Sun, 20 Jan 2019 12:44:16 +0000
Size: 3260
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190222/c33b3b8d/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Ian Jackson <ijackson at chiark.greenend.org.uk>
Subject: Bug#912381: fixed in xen 4.11.1+26-g87f51bf366-2
Date: Fri, 22 Feb 2019 16:37:31 +0000
Size: 19114
URL:
<http://alioth-lists.debian.net/pipermail/pkg-xen-devel/attachments/20190222/c33b3b8d/attachment-0003.mht>