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

Re: [Xen-users] Debian 8.4, EFI, and systemd = Tricky

  • To: xen-users@xxxxxxxxxxxxx
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
  • Date: Tue, 12 Apr 2016 09:11:36 -0400
  • Delivery-date: Tue, 12 Apr 2016 13:12:25 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

On 2016-04-12 08:52, Paul Daniels wrote:

    Message: 6
    Date: Tue, 12 Apr 2016 11:05:23 +0100
    From: Simon Hobson <linux@xxxxxxxxxxxxxxxx
    To: "xen-users@xxxxxxxxxxxxx <mailto:xen-users@xxxxxxxxxxxxx>"
    <xen-users@xxxxxxxxxxxxx <mailto:xen-users@xxxxxxxxxxxxx>>
    Subject: Re: [Xen-users] Debian 8.4, EFI, and systemd = Tricky
    Message-ID: <D68AEF50-4237-4B5A-BB63-8A1C05418B0C@xxxxxxxxxxxxxxxx
    Content-Type: text/plain; charset=us-ascii

    Paul Daniels <walkabout.pd@xxxxxxxxx
    <mailto:walkabout.pd@xxxxxxxxx>> wrote:

     > At this point exec /bin/systemd hangs the machine, no output just
    a cursor(like every other hang)

    Apart from the fact that I wouldn't have had SystemD installed in
    the first place, have you considered installing SysVinit and
    removing SystemD ? Given the normal recommendation for the host to
    be as minimal a system as you can, I can't see any reason to be
    running anything that depends on it.

I'll probably have to head that way.

It's actually a convenience issue for me, easier to have a fully loaded
dom0 and to segregate out portions onto the xen domU's.  DHCP, LTSP,
webservices. As I need to modify one simply send the vm to my servers,
with minimal dom0's.  But when I'm onsite with just a laptop, having the
same functionality is awesome. Been great up until I was forced to
update my debian. Systemd is faster, and seems logical, and looks like
something ill encounter on a regular basis.
TBH, while it has some redeeming qualities, most of the arguments for it fall flat on their face for Domain-0. The journal is a pointless waste of processor time and I/O bandwidth unless you need to use software that only works with it (which right now is only other systemd services), the 'management' tools (hostnamed, timedated, and friends) are absolutely pointless even on a regular system, the boot time speedups are marginal on Xen systems (most people need to serialize start-up of certain services regardless, and Xen requires it (xenstored needs to be running before you can use the tools, and most people require some serialization of domain start-up too)), upower's utility is debatable when running on Xen, udisks is a security issue, logind is pointless for a control domain (and of debatable utility for a single user system anyway). The only thing that I'd say is even remotely useful for a control domain is udev (and you could just use eudev or mdev instead).

So it would be great if it worked.

I was hoping that someone had encountered and solved similar issues, and
would share their experiences.
While I can't help much in this particular case, I can tell you from personal experience dealing with Fedora at work that systemd does not reliably work when run via exec from a shell. Also, I think the EFI bit may be unrelated (unless you're trying to use systemd-boot, which doesn't appear to be the case based on your earlier e-mails).

Xen-users mailing list



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