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
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
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
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
** 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
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.
** 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):
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.
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.
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
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.
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
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
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
> 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
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
> 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
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.
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:
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
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
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
** 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
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.
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
The error message is pretty clear. src/util/virsystemd.c does
if (virDBusCallMethod(conn,
NULL,
,
"org.freedesktop.machine1",
"/org/freedesktop/machine1",
The error message is pretty clear. src/util/virsystemd.c does
if (virDBusCallMethod(conn,
NULL,
,
"org.freedesktop.machine1",
"/org/freedesktop/machine1",
@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
** 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.
29 matches
Mail list logo
