[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1350909.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-06-28T17:22:55+00:00 Quentin wrote:

Description of problem:

libvirt's virSystemdCreateMachine (src/util/virsystemd.c) calls the
systemd API `CreateMachineWithNetwork` via D-Bus to register machines.
It works fine until systemd 225. However, with systemd 229, the `Before`
property that is passed isn't accepted anymore and thus, makes the
registration and creation of machines to fail.

Version-Release number of selected component (if applicable):

libvirt 1.2.17 (13.el7_2.5)
systemd 229 (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT -GNUTLS -ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD 
-IDN)

Steps to Reproduce:

0. Get an Ubuntu Xenial VM
1. apt-get install qemu-kvm libvirt-bin
2. Follow instructions at https://wiki.ubuntu.com/SergeHallyn_libvirtnest , in 
particular:
 a. wget http://people.canonical.com/~serge/cdboot.xml
 b. wget -O mini.iso 
http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/mini.iso
 c. qemu-img create cdboot.img 1G
 d. virsh define cdboot.xml
 e. virsh start cdboot
3. now apt-get install systemd-container
4. now virsh destroy cdboot; virsh start cdboot; it should fail

(https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/comments/39)

Actual results:

libvirtError: Cannot set property Before, or unknown property.

Expected results:

- The machine should be started properly:
 a. `Before` shouldn't be passed,
 b. `After` should probably not be passed either,
- A systemd registration failure should maybe not be critical.

Additional info:

Issue reproduced on Ubuntu Xenial & CoreOS >1010.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/comments/48


On 2016-06-28T18:07:23+00:00 Daniel wrote:

Passing Before & After properties is absolutely required in order to get
correct shutdown ordering - ie we need systemd to run libvirt-guests.

I've confirmed testing on Fedora 24 with systemd 229 and see no failure,
so I don't believe this is a libvirt bug. More likely it is a distro
specific systemd bug or deployment mistake (eg perhaps missing libvirt-
guests.service unit file).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/comments/51


On 2016-06-28T19:10:02+00:00 Michael wrote:

I haven't been able to spot anything in either the CoreOS or Fedora
systemd patch sets that would impact this one way or the other so far,
will need to dig further.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/comments/53


On 2016-06-28T22:00:45+00:00 Michael wrote:

Ok, found some suspicious behavior in systemd. The distinction may be
whether or not the 'After' dependency refers to an existing unit or not.
On CoreOS it is entirely likely libvirtd.service doesn't exist or has a
different name. I'm not sure about the Ubuntu case. Also the order if
After/Before in the properties list is significant. Using Before/After
appears to work.

Both dependencies do not exist, but fails only when After is first:

# busctl call org.freedesktop.systemd1 /org/freedesktop/systemd1 \
org.freedesktop.systemd1.Manager StartTransientUnit 'ssa(sv)a(sa(sv))' \
test7.slice replace 2 After as 1 other.target Before as 1 fake.target 0
Cannot set property Before, or unknown property.

# busctl call org.freedesktop.systemd1 /org/freedesktop/systemd1 \
org.freedesktop.systemd1.Manager StartTransientUnit 'ssa(sv)a(sa(sv))' \
test7.slice replace 2 Before as 1 fake.target After as 1 other.target 0
o "/org/freedesktop/systemd1/job/23660"

Whether or not the Before dependency exists never matters.

Quentin: so at least this hints at a workaround, either create a dummy
libvirtd.service unit file or run the container with that unit name. Or
if the container doesn't make sense to run as libvirtd.service maybe a
unit alias is sufficient.

Alternate workaround: patch libvirt to swap the order of those two
properties.

Real fix: figure out what on earth is going on in systemd, but that's
all the brain power I can spend on this at the moment.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/comments/54


On 2016-06-29T10:24:38+00:00 Quentin wrote:

See 

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[seahawk1986]

Would it be possible to include this change to be able to receive all
queued DBus signals from a unit before it is removed?
https://github.com/systemd/systemd/commit/0dd99f86addd1f81e24e89807b6bc4aab57d5793

Tracking unit states using DBus signals has been working initially with
Ubuntu 16.04 but does not work anymore for units that become inactive
since the update of the systemd package in early september.

** Patch added: "fix-send-queued-messages.diff"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+attachment/4759303/+files/fix-send-queued-messages.diff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[RussianNeuroMancer]

Thank you, Martin!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-4ubuntu8

---
systemd (229-4ubuntu8) xenial-proposed; urgency=medium

  * Queue loading transient units after setting their properties. Fixes
starting VMs with libvirt. (LP: #1529079)
  * Connect pid1's stdin/out/err fds to /dev/null also for containers. This
fixes generators which expect a valid stdout/err fd in some container
technologies. (LP: #1608953)
  * 73-usb-net-by-mac.rules: Do not run readlink for *every* uevent, and
merely check if /etc/udev/rules.d/80-net-setup-link.rules exists.
A common way to disable an udev rule is to just "touch" it in
/etc/udev/rule.d/ (i. e. empty file), and if the rule is customized we
cannot really predict anyway if the user wants MAC-based USB net names or
not. (LP: #1615021)
  * systemd-networkd-resolvconf-update.service: Also pick up DNS servers from
individual link leases, as they sometimes don't appear in the global
ifstate. (LP: #1620559)

 -- Martin Pitt   Tue, 06 Sep 2016 14:16:29
+0200

** Changed in: systemd (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Martin Pitt]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Jérôme Poulin]

The package that was submitted to xenial-proposed fixes the problem on
my computer, machinectl start  and virsh start  can now
be run without removing systemd-nspawn.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Martin Pitt]

** Description changed:

  Can't start virtual machines after upgrade to Xenial.
  
  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.
  
  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
-   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
- callback(asyncjob, *args, **kwargs)
-   File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
- guest.start_install(meter=meter)
-   File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
- noboot)
-   File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
- dom = self.conn.createLinux(start_xml or final_xml, 0)
-   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
- if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
+   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
+ callback(asyncjob, *args, **kwargs)
+   File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
+ guest.start_install(meter=meter)
+   File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
+ noboot)
+   File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
+ dom = self.conn.createLinux(start_xml or final_xml, 0)
+   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
+ if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.
  
  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
- --- 
+ ---
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=C
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=C
+  SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560
+ 
+ SRU INFORMATION
+ ===
+ Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=5c4291769cb426a
+ 
+ Regression potential: This changes a central place of systemd (although
+ the fix is quite obvious), so if that code is broken it could
+ potentially lead to boot failure. However, the fix has been tested in
+ yakkety, and all the time in upstrean and downstream CI, so if this
+ would actually break anything it should have surfaced by now. So low
+ overall.
+ 
+ Test case: Should be verified by the reporter as the bug description
+ did not include a reproducer.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Andy Whitcroft]

Hello RussianNeuroMancer, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu8
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Martin Pitt]

ps://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-
xenial=5c4291769c

** Changed in: systemd (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Martin Pitt]

Thanks! Moving this to the systemd package then. This commit is included
in v231, so fixed in yakkety. I'll backport it to xenial.

** Changed in: libvirt (Ubuntu)
   Status: Triaged => Invalid

** Changed in: systemd (Ubuntu)
   Status: Invalid => Fix Released

** Also affects: libvirt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1350909
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Martin Pitt]

sorry, correct link: https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntu-xenial=5c4291769c

** Changed in: libvirt (Ubuntu Xenial)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Terra Nova]

The fix has been merged into systemd via:
https://github.com/systemd/systemd/pull/3676

It appears this was not a libvirt problem and the systemd 'invalid' tag
is incorrect.

Has anyone already created a systemd issue to get it updated with this
patch (I didn't find any)?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Quentin MACHU]

This issue happens to us because libvirt is being used inside a Docker
container which share systemd with the host. Therefore, neither of these
units exist on the host and as mentioned above, when a non-existing unit
is specified in the `After` clause - listed first - the `Before` clause
makes systemd fail.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Michael Marineau]

Is the libvirtd.service named differently on the Ubuntu system? I'm
pretty sure this is a systemd bug, where if the properties list After
first and After names a non-existent unit the Before property will fail.
If After names an existing unit or Before is listed first it works. From
https://bugzilla.redhat.com/show_bug.cgi?id=1350909#c3

# busctl call org.freedesktop.systemd1 /org/freedesktop/systemd1 \
org.freedesktop.systemd1.Manager StartTransientUnit 'ssa(sv)a(sa(sv))' \
test7.slice replace 2 After as 1 other.target Before as 1 fake.target 0
Cannot set property Before, or unknown property.

# busctl call org.freedesktop.systemd1 /org/freedesktop/systemd1 \
org.freedesktop.systemd1.Manager StartTransientUnit 'ssa(sv)a(sa(sv))' \
test7.slice replace 2 Before as 1 fake.target After as 1 other.target 0
o "/org/freedesktop/systemd1/job/23660"

Whether or not the Before dependency exists never matters.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Daniel Berrange]

> Not sure of the importance of that `Before` close there yet.

The Before/After properties provide the correct ordering of units on
shutdown. Without this dependency, there is no guarantee that libvirt-
guests.service will be invoked before systemd kills the machines, nor
that it will keep libvirtd.service running until the VMs have been
shutdown.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Quentin MACHU]

Just created an issue on libvirt's upstream bug tracker:
https://bugzilla.redhat.com/show_bug.cgi?id=1350909

** Bug watch added: Red Hat Bugzilla #1350909
   https://bugzilla.redhat.com/show_bug.cgi?id=1350909

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Daniel Berrange]

> You can't specify an ordering dependency to an object that you create
*right now*, as there is no way to enforce them. So just dropping these
two lines ought to fix it.

You're only considering startup ordering. These properties also apply to
ordering when stopping units, and so these do make sense & are required
to get correct shutdown ordering for machines.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Quentin MACHU]

We do experience that issue too on CoreOS. Until CoreOS 1010, it worked
just fine (systemd v225), and afterwards (systemd v229), the issue is
present.

The libvirt code mentioned above did not change since 2014. Therefore,
it seems that a change to systemd between 225 and 229 generates that
issue.

Not sure of the importance of that `Before` close there yet. I need to
document myself more. We could try without it and see how it goes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Quentin MACHU]

I do experience it too in CoreOS+CentOS (docker).
Question is why is it a problem now?
These lines have been present there since 2014.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Serge Hallyn]

Reminder - see comment #40 for the proposed fix.

The pertinent question is, given that that is upstream, why is this
apparently not a problem for other systemd-based distros?  How does it
work in Fedora?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Andrew Cooks]

I tried the fix suggested in #40, but couldn't get it to work.

[Wed, 08 Jun 2016 10:39:46 virt-install 23425] DEBUG (cli:305)   File 
"/usr/share/virt-manager/virt-install", line 1063, in 
sys.exit(main())
  File "/usr/share/virt-manager/virt-install", line 1057, in main
start_install(guest, continue_inst, options)
  File "/usr/share/virt-manager/virt-install", line 768, in start_install
fail(e, do_exit=False)
  File "/usr/share/virt-manager/virtinst/cli.py", line 305, in fail
logging.debug("".join(traceback.format_stack()))

[Wed, 08 Jun 2016 10:39:46 virt-install 23425] ERROR (cli:306) End of file 
while reading data: Input/output error
[Wed, 08 Jun 2016 10:39:46 virt-install 23425] DEBUG (cli:308) 
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-install", line 741, in start_install
dom = guest.start_install(meter=meter, noboot=options.noreboot)
  File "/usr/share/virt-manager/virtinst/guest.py", line 501, in start_install
noboot)
  File "/usr/share/virt-manager/virtinst/guest.py", line 416, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3606, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
libvirtError: End of file while reading data: Input/output error

I really need both systemd-container and libvirt to work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[keshara Dorakumbura]

Cannot start virtual machines via kvm once install 'systemd-container'
package. I am on Ubuntu16.04-xenial.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Serge Hallyn]

** Changed in: libvirt (Ubuntu)
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Jérôme Poulin]

Well, until then...

virsh () { apt-get -qqy remove systemd-container >/dev/null;
/usr/bin/virsh "$@"; apt-get -qqy install systemd-container >/dev/null;
}

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Serge Hallyn]

Interesting.  It is still this way in libvirt git HEAD.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Martin Pitt]

The error message is pretty clear. src/util/virsystemd.c does

if (virDBusCallMethod(conn,
  NULL,
  ,
  "org.freedesktop.machine1",
  "/org/freedesktop/machine1",
  "org.freedesktop.machine1.Manager",
  "CreateMachineWithNetwork",
[...]
"After", "as", 1, "libvirtd.service",
 "Before", "as", 1, "libvirt-guests.service") < 0) {

and these properties are unknown/invalid for machines. You can't specify
an ordering dependency to an object that you create *right now*, as
there is no way to enforce them. So just dropping these two lines ought
to fix it.

(Also, it would be nice if a failure to register to machined wasn't
fatal)

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: libvirt (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Martin Pitt]

The error message is pretty clear. src/util/virsystemd.c does

if (virDBusCallMethod(conn,
  NULL,
  ,
  "org.freedesktop.machine1",
  "/org/freedesktop/machine1",
  "org.freedesktop.machine1.Manager",
  "CreateMachineWithNetwork",
[...]
"After", "as", 1, "libvirtd.service",
 "Before", "as", 1, "libvirt-guests.service") < 0) {

and these properties are unknown/invalid for machines. You can't specify
an ordering dependency to an object that you create *right now*, as
there is no way to enforce them. So just dropping these two lines ought
to fix it.

(Also, it would be nice if a failure to register to machined wasn't
fatal)

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: libvirt (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Serge Hallyn]

@pitti,

to reproduce in a fresh vm,

1. apt-get install qemu-kvm libvirt-bin
2. follow instructions at https://wiki.ubuntu.com/SergeHallyn_libvirtnest , in 
particular:
 a. wget http://people.canonical.com/~serge/cdboot.xml
 b.  wget -O mini.iso 
http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-amd64/current/images/netboot/mini.iso
 
 c. qemu-img create cdboot.img 1G
 d. virsh define cdboot.xml
 e. virsh start cdboot
3. now apt-get install systemd-container

now virsh destroy cdboot; virsh start cdboot;  it should fail

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[RussianNeuroMancer]

** Summary changed:

- Can't start virtual machines after upgrade to Xenial
+ Can't start virtual machines with installed systemd-container package on 
Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs