[Top][All Lists]

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

[Bug 1823790] Re: QEMU mishandling of SO_PEERSEC forces systemd into tig

From: Tobias Koch
Subject: [Bug 1823790] Re: QEMU mishandling of SO_PEERSEC forces systemd into tight loop
Date: Tue, 04 Feb 2020 12:51:07 -0000

I carried out the following test:

* fetched the QEMU coming with 18.04,
* added this patch,
* built an LXD container with arch arm64 and the patched qemu-aarch64-static 
* launched it on amd64

Previously various systemd services would not come up properly, now they
are running like a charm. The only grief I have is that network
configuration does not work, but that is due to

    # ip addr
    Unsupported setsockopt level=270 optname=11

which is a different story.

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  QEMU mishandling of SO_PEERSEC forces systemd into tight loop

Status in QEMU:

Bug description:
  While building Debian images for embedded ARM target systems I
  detected that QEMU seems to force newer systemd daemons into a tight

  My setup is the following:

  Host machine: Ubuntu 18.04, amd64
  LXD container: Debian Buster, arm64, systemd 241
  QEMU: qemu-aarch64-static, 4.0.0-rc2 (custom build) and 3.1.0 (Debian 

  To easily reproduce the issue I have created the following repository:

  The call where systemd gets looping is the following:
  2837 getsockopt(3,1,31,274891889456,274887218756,274888927920) = -1 errno=34 
(Numerical result out of range)

  Furthermore I also verified that the issue is not related to LXD.
  The same behavior can be reproduced using systemd-nspawn.

  This issue reported against systemd seems to be related:

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]