Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#773561: Installing "xen-linux-system-amd64" on jessie fails

184 views
Skip to first unread message

Sydney Meyer

unread,
Dec 19, 2014, 7:10:03 PM12/19/14
to
Package: xen-linux-system-amd64
Version: 3.16+63

Dear Maintainers,

installing "xen-linux-system-amd64" on a fresh jessie (amd64) install and after dist-upgrade fails as below, while installing "xen-utils-common" and afterwards "xen-linux-system" works fine.

...
Setting up xen-hypervisor-4.4-amd64 (4.4.1-6) ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found linux image: /boot/vmlinuz-3.14-2-amd64
Found initrd image: /boot/initrd.img-3.14-2-amd64
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found linux image: /boot/vmlinuz-3.14-2-amd64
Found initrd image: /boot/initrd.img-3.14-2-amd64
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
Found linux image: /boot/vmlinuz-3.14-2-amd64
Found initrd image: /boot/initrd.img-3.14-2-amd64
done
Setting up xenstore-utils (4.4.1-6) ...
Setting up xen-utils-common (4.4.1-6) ...
Job for xen.service failed. See 'systemctl status xen.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript xen, action "start" failed.
dpkg: error processing package xen-utils-common (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of xen-utils-4.4:
xen-utils-4.4 depends on xen-utils-common (>= 4.4.1-6); however:
Package xen-utils-common is not configured yet.

dpkg: error processing package xen-utils-4.4 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of xen-system-amd64:
xen-system-amd64 depends on xen-utils-4.4; however:
Package xen-utils-4.4 is not configured yet.

dpkg: error processing package xen-system-amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of xen-linux-system-3.16.0-4-amd64:
xen-linux-system-3.16.0-4-amd64 depends on xen-system-amd64; however:
Package xen-system-amd64 is not configured yet.

dpkg: error processing package xen-linux-system-3.16.0-4-amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of xen-linux-system-amd64:
xen-linux-system-amd64 depends on xen-linux-system-3.16.0-4-amd64; however:
Package xen-linux-system-3.16.0-4-amd64 is not configured yet.

dpkg: error processing package xen-linux-system-amd64 (--configure):
dependency problems - leaving unconfigured
Setting up grub-xen-bin (2.02~beta2-18) ...
Setting up grub-xen-host (2.02~beta2-18) ...
Processing triggers for libc-bin (2.19-13) ...
Processing triggers for ca-certificates (20141019) ...
Updating certificates in /etc/ssl/certs... 173 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
Errors were encountered while processing:
xen-utils-common
xen-utils-4.4
xen-system-amd64
xen-linux-system-3.16.0-4-amd64
xen-linux-system-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Ian Campbell

unread,
Dec 20, 2014, 5:40:03 AM12/20/14
to
On Sat, 2014-12-20 at 00:57 +0100, Sydney Meyer wrote:
> Job for xen.service failed. See 'systemctl status xen.service' and 'journalctl -xn' for details.

Please can you provide the output of these two commands while in this
state.

Ian.

Sydney Meyer

unread,
Dec 20, 2014, 3:00:03 PM12/20/14
to
Hello Ian,

"systemctl status xen.service" gives:

root@jessie:/home/sydney# systemctl status xen.service
● xen.service - LSB: Xen daemons
Loaded: loaded (/etc/init.d/xen)
Active: failed (Result: exit-code) since Sat 2014-12-20 20:42:30 CET; 11s ago
Process: 4796 ExecStart=/etc/init.d/xen start (code=exited, status=255)

Dec 20 20:42:30 jessie xen[4796]: Starting Xen daemons: xenfs (warning).
Dec 20 20:42:30 jessie systemd[1]: xen.service: control process exited, code=exited status=255
Dec 20 20:42:30 jessie systemd[1]: Failed to start LSB: Xen daemons.
Dec 20 20:42:30 jessie systemd[1]: Unit xen.service entered failed state.


"journalctl -xn" gives:

root@jessie:/home/sydney# journalctl -xn
-- Logs begin at Sat 2014-12-20 20:40:10 CET, end at Sat 2014-12-20 20:42:30 CET. --
Dec 20 20:42:27 jessie kernel: hfsplus: unable to find HFS+ superblock
Dec 20 20:42:27 jessie kernel: qnx4: no qnx4 filesystem (no root dir).
Dec 20 20:42:27 jessie kernel: You didn't specify the type of your ufs filesystem

mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

>>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
Dec 20 20:42:27 jessie kernel: hfs: can't find a HFS filesystem on dev xvda2
Dec 20 20:42:27 jessie os-prober[4747]: debug: /dev/xvda5: is active swap
Dec 20 20:42:30 jessie kernel: xen:xen_evtchn: Event-channel device installed
Dec 20 20:42:30 jessie xen[4796]: Starting Xen daemons: xenfs (warning).
Dec 20 20:42:30 jessie systemd[1]: xen.service: control process exited, code=exited status=255
Dec 20 20:42:30 jessie systemd[1]: Failed to start LSB: Xen daemons.
-- Subject: Unit xen.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit xen.service has failed.
--
-- The result is failed.
Dec 20 20:42:30 jessie systemd[1]: Unit xen.service entered failed state.

Ian Campbell

unread,
Dec 22, 2014, 11:30:06 AM12/22/14
to
On Sat, 2014-12-20 at 20:46 +0100, Sydney Meyer wrote:
> Hello Ian,
>
> "systemctl status xen.service" gives:

Thanks. Sadly these logs weren't as informative a I had hoped they would
be :-/ (In case it's not clear: this is not your fault)

> root@jessie:/home/sydney# systemctl status xen.service
> ● xen.service - LSB: Xen daemons
> Loaded: loaded (/etc/init.d/xen)
> Active: failed (Result: exit-code) since Sat 2014-12-20 20:42:30 CET; 11s ago
> Process: 4796 ExecStart=/etc/init.d/xen start (code=exited, status=255)
>
> Dec 20 20:42:30 jessie xen[4796]: Starting Xen daemons: xenfs (warning).
> Dec 20 20:42:30 jessie systemd[1]: xen.service: control process exited, code=exited status=255
> Dec 20 20:42:30 jessie systemd[1]: Failed to start LSB: Xen daemons.
> Dec 20 20:42:30 jessie systemd[1]: Unit xen.service entered failed state.

This basically says "it failed", which isn't terribly helpful!

I think it is complaining because it couldn't mount xenfs, but it
doesn't say why.

If you run "/etc/init.d/xen start" from the root command line does it
say something more informative/useful?

Could you also try running /usr/lib/xen-common/bin/xen-dir
and /usr/lib/xen-common/bin/xen-toolstack by hand (also as root).

> "journalctl -xn" gives:
>
> root@jessie:/home/sydney# journalctl -xn
> -- Logs begin at Sat 2014-12-20 20:40:10 CET, end at Sat 2014-12-20 20:42:30 CET. --
> Dec 20 20:42:27 jessie kernel: hfsplus: unable to find HFS+ superblock
> Dec 20 20:42:27 jessie kernel: qnx4: no qnx4 filesystem (no root dir).
> Dec 20 20:42:27 jessie kernel: You didn't specify the type of your ufs filesystem
>
> mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
>
> >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
> Dec 20 20:42:27 jessie kernel: hfs: can't find a HFS filesystem on dev xvda2
> Dec 20 20:42:27 jessie os-prober[4747]: debug: /dev/xvda5: is active swap

This made me wonder -- are you doing/installing this in a Xen guest
(domU)? From other evidence I don't think you are but I should check.

Assuming you are running this on the dom0/host, have you booted into the
hypervisor at this point or are you running bare-metal/native? (I
suspect the latter).

Thanks,

Sydney Meyer

unread,
Dec 22, 2014, 5:10:02 PM12/22/14
to

> On 22 Dec 2014, at 17:25, Ian Campbell <i...@debian.org> wrote:
>
> On Sat, 2014-12-20 at 20:46 +0100, Sydney Meyer wrote:
>> Hello Ian,
>>
>> "systemctl status xen.service" gives:
>
> Thanks. Sadly these logs weren't as informative a I had hoped they would
> be :-/ (In case it's not clear: this is not your fault)
>
>> root@jessie:/home/sydney# systemctl status xen.service
>> ● xen.service - LSB: Xen daemons
>> Loaded: loaded (/etc/init.d/xen)
>> Active: failed (Result: exit-code) since Sat 2014-12-20 20:42:30 CET; 11s ago
>> Process: 4796 ExecStart=/etc/init.d/xen start (code=exited, status=255)
>>
>> Dec 20 20:42:30 jessie xen[4796]: Starting Xen daemons: xenfs (warning).
>> Dec 20 20:42:30 jessie systemd[1]: xen.service: control process exited, code=exited status=255
>> Dec 20 20:42:30 jessie systemd[1]: Failed to start LSB: Xen daemons.
>> Dec 20 20:42:30 jessie systemd[1]: Unit xen.service entered failed state.
>
> This basically says "it failed", which isn't terribly helpful!
>
> I think it is complaining because it couldn't mount xenfs, but it
> doesn't say why.
>
> If you run "/etc/init.d/xen start" from the root command line does it
> say something more informative/useful?

No, it fails and refers to systemctl/journalctl:

root@jessie:/home/sydney# /etc/init.d/xen start
[....] Starting xen (via systemctl): xen.serviceJob for xen.service failed. See 'systemctl status xen.service' and 'journalctl -xn' for details.
failed!
>
> Could you also try running /usr/lib/xen-common/bin/xen-dir
> and /usr/lib/xen-common/bin/xen-toolstack by hand (also as root).

root@jessie:/home/sydney# /usr/lib/xen-common/bin/xen-dir
/usr/lib/xen-4.4

root@jessie:/home/sydney# /usr/lib/xen-common/bin/xen-toolstack
/usr/lib/xen-4.4/bin/xl
>
>> "journalctl -xn" gives:
>>
>> root@jessie:/home/sydney# journalctl -xn
>> -- Logs begin at Sat 2014-12-20 20:40:10 CET, end at Sat 2014-12-20 20:42:30 CET. --
>> Dec 20 20:42:27 jessie kernel: hfsplus: unable to find HFS+ superblock
>> Dec 20 20:42:27 jessie kernel: qnx4: no qnx4 filesystem (no root dir).
>> Dec 20 20:42:27 jessie kernel: You didn't specify the type of your ufs filesystem
>>
>> mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
>>
>>>>> WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
>> Dec 20 20:42:27 jessie kernel: hfs: can't find a HFS filesystem on dev xvda2
>> Dec 20 20:42:27 jessie os-prober[4747]: debug: /dev/xvda5: is active swap
>
> This made me wonder -- are you doing/installing this in a Xen guest
> (domU)? From other evidence I don't think you are but I should check.

Yes, this particular output is from a Xen DomU with vmx enabled. The Dom0 is running Xen 4.4.1 compiled from source on a Debian Linux 3.16.2 Kernel. I have also tested this on a VMware Fusion 7 Guest (HW Version 11).
>
> Assuming you are running this on the dom0/host, have you booted into the
> hypervisor at this point or are you running bare-metal/native? (I
> suspect the latter).

The VM was running "native", i.e. the VM itself didn't boot into hypervisor mode.

Ian Campbell

unread,
Dec 23, 2014, 7:10:03 AM12/23/14
to
Control: reassign -1 xen-utils-common 4.4.1-6
Control: retitle -1 /etc/init.d/xen fails when run in a guest, causing postinst to fail.

Seems like this issue is in the Xen packages not in the xen-linux-system
metapackage, so reassigning.

On Mon, 2014-12-22 at 23:01 +0100, Sydney Meyer wrote:
> > On 22 Dec 2014, at 17:25, Ian Campbell <i...@debian.org> wrote:
> >
> > On Sat, 2014-12-20 at 20:46 +0100, Sydney Meyer wrote:
> >> Hello Ian,
> >>
> >> "systemctl status xen.service" gives:
> >
> > Thanks. Sadly these logs weren't as informative a I had hoped they would
> > be :-/ (In case it's not clear: this is not your fault)
> >
> >> root@jessie:/home/sydney# systemctl status xen.service
> >> ● xen.service - LSB: Xen daemons
> >> Loaded: loaded (/etc/init.d/xen)
> >> Active: failed (Result: exit-code) since Sat 2014-12-20 20:42:30 CET; 11s ago
> >> Process: 4796 ExecStart=/etc/init.d/xen start (code=exited, status=255)
> >>
> >> Dec 20 20:42:30 jessie xen[4796]: Starting Xen daemons: xenfs (warning).
> >> Dec 20 20:42:30 jessie systemd[1]: xen.service: control process exited, code=exited status=255
> >> Dec 20 20:42:30 jessie systemd[1]: Failed to start LSB: Xen daemons.
> >> Dec 20 20:42:30 jessie systemd[1]: Unit xen.service entered failed state.
> >
> > This basically says "it failed", which isn't terribly helpful!
> >
> > I think it is complaining because it couldn't mount xenfs, but it
> > doesn't say why.
> >
> > If you run "/etc/init.d/xen start" from the root command line does it
> > say something more informative/useful?
>
> No, it fails and refers to systemctl/journalctl:

OK.
>
> root@jessie:/home/sydney# /etc/init.d/xen start
> [....] Starting xen (via systemctl): xen.serviceJob for xen.service failed. See 'systemctl status xen.service' and 'journalctl -xn' for details.
> failed!
> >
> > Could you also try running /usr/lib/xen-common/bin/xen-dir
> > and /usr/lib/xen-common/bin/xen-toolstack by hand (also as root).
>
> root@jessie:/home/sydney# /usr/lib/xen-common/bin/xen-dir
> /usr/lib/xen-4.4
>
> root@jessie:/home/sydney# /usr/lib/xen-common/bin/xen-toolstack
> /usr/lib/xen-4.4/bin/xl

Thanks, so it thinks it is running under Xen (which given what you say
below makes sense).

What (if anything) does "mount -t xenfs xenfs /proc/xen" report?
Does /proc/xen exist?

> Yes, this particular output is from a Xen DomU with vmx enabled. The
> Dom0 is running Xen 4.4.1 compiled from source on a Debian Linux
> 3.16.2 Kernel.

Thanks, this would have been good to know up front. I suppose you are
wanting to do some sort of nested virtualisation? You are likely the
first to try this with the Debian packaging, and nested virt generally
is considered tech preview upstream, so I'd expect there to be some
wrinkles in doing this.

By "with vmx enabled" I guess you mean with nestedhvm=1 in the guest
cfg? Are you running this in a PV or HVM guest (I think HVM)? Can you
post the dmesg from the kernel please, along with the guest cfg file.

I don't have much experience with nested virt but AIUI there are some
caveats with running Xen on Xen, in particular it seems that the L1
hypervisor (see [0] for the terminology) can either be a xenbus client
of the L0 hypervisor or provide xenbus services to its own L2 guests,
but not both at the same time. I think that people generally disable PV
drivers on the L1 domain (e.g. with xen_platform_pci=1 in its config) so
that it is free to provide xenbus services to its own guests. It might
be that this isn't relevant to the issue you report here, but it might
have some bearing (and it worth trying to disable it).

[0] http://wiki.xenproject.org/wiki/Xen_nested

> I have also tested this on a VMware Fusion 7 Guest (HW Version 11).

And it fails in the same way? If so then that's interesting because I
wouldn't expect the kernel to discover that it was running on Xen under
those circumstances. I wonder if the initscript is confused because it
is running on any hypervisor at all not specifically Xen

Does /sys/hypervisor/type exist in all cases and what does it contain?

> > Assuming you are running this on the dom0/host, have you booted into the
> > hypervisor at this point or are you running bare-metal/native? (I
> > suspect the latter).
>
> The VM was running "native", i.e. the VM itself didn't boot into
> hypervisor mode.

My hypothesis is that because it is running as a guest on Xen something
is getting confused and thinking it is actually booting as a host on
Xen, but the vmware thing doesn't quite fit.

Debian Bug Tracking System

unread,
Dec 23, 2014, 7:10:03 AM12/23/14
to
Processing control commands:

> reassign -1 xen-utils-common 4.4.1-6
Bug #773561 [xen-linux-system-amd64] Installing "xen-linux-system-amd64" on jessie fails
Bug reassigned from package 'xen-linux-system-amd64' to 'xen-utils-common'.
No longer marked as found in versions linux-latest/63.
Ignoring request to alter fixed versions of bug #773561 to the same values previously set
Bug #773561 [xen-utils-common] Installing "xen-linux-system-amd64" on jessie fails
Marked as found in versions xen/4.4.1-6.
> retitle -1 /etc/init.d/xen fails when run in a guest, causing postinst to fail.
Bug #773561 [xen-utils-common] Installing "xen-linux-system-amd64" on jessie fails
Changed Bug title to '/etc/init.d/xen fails when run in a guest, causing postinst to fail.' from 'Installing "xen-linux-system-amd64" on jessie fails'

--
773561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-ker...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/handler.s.B773561.1419...@bugs.debian.org
0 new messages