> 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. > > Thanks, > Ian. > -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ab8f8295-2dfe-4e24-8972-1539e82f2...@gmail.com
