Lowering priority since there is a workaround.
Stilll not clear whether this is a bug in systemd-machined or in
libvirt's use of it.
** Changed in: libvirt (Ubuntu)
Importance: High => Medium
** Changed in: systemd (Ubuntu)
Importance: High => Medium
--
You received this bug
The problem is introduced by systemd-machined, which is being provided
by the systemd-container package.
The workaround is to apt-get purge systemd-container.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Feb 17 13:13:19 sl libvirtd[9909]: DBUS_METHOD_CALL:
'org.freedesktop.machine1.Manager.CreateMachineWithNetwork' on
'/org/freedesktop/machine1' at 'org.freedesktop.machine1'
Feb 17 13:13:19 sl libvirtd[9909]: DBUS_METHOD_ERROR:
'org.freedesktop.machine1.Manager.CreateMachineWithNetwork' on
So I can reproduce this now that I've updated to xenial; smb and arges
who did fresh installs cannot. Interesting.
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: rls-x-incoming
--
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 after upgrade to Xenial
To manage notifications about this bug go to:
** Changed in: systemd (Ubuntu)
Importance: Undecided => 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 after upgrade to Xenial
To manage
Issue is still reproducible with latest version of libvirt package.
--
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 after upgrade to Xenial
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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:
Issue is still reproducible on Kubuntu 16.04 with installed updates. I
reproduced it with xml from commentary #15.
--
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
I installed Kubuntu 15.04, then distupgraded to 15.10 and 16.04, but was
not able to reproduce this.
--
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 after
Maybe error message from #12 and#16 provide any useful information?
--
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 after upgrade to Xenial
To manage
Please tell me how I can help you find root of this issue? As I said,
reproducible for me on two installations (Kubuntu and Ubuntu Server).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529079
I'm also curious why the launchpad janitor marked this bug confirmed.
If anyone else can reproduce this issue, please comment here.
Otherwise, I do not want it marked confirmed until someone truly
independently reproduces it.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Incomplete
I still cannot reproduce this at all, even when starting VMs from virt-
manager.
Are you still able to reproduce this? (I'm wondering whether perhaps
there was a temporary bad state of systemd and libvirt being out of sync
some magical way)
--
You received this bug notification because you are
> I still cannot reproduce this at all, even when starting VMs from
> virt-manager.
Well, for fresh install this is not reproducible for me too. And 15.10-16.04
upgrade may not be actual trigger - both testing systems get upgraded for a
long time, Kubuntu from 11.04 as I remember. So there is
Hi, I had the same some time ago but then I went back to Wily.
--
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 after upgrade to Xenial
To manage
> And it is still reproducible after reboot after the upgrade, right?
Yes, this Kubuntu was rebooted yesterday after system upgrade.
--
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:
Quoting RussianNeuroMancer (1529...@bugs.launchpad.net):
> > I still cannot reproduce this at all, even when starting VMs from
> > virt-manager.
> Well, for fresh install this is not reproducible for me too. And 15.10-16.04
> upgrade may not be actual trigger - both testing systems get upgraded
> > I can add systemd package as affected package again?
> Yes I think that's fair, though it's more likely a bug in libvirt's use of
> systemd-machined.
Okay, I added systemd package as affected.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received
> > I can add systemd package as affected package again?
> Yes I think that's fair, though it's more likely a bug in libvirt's use of
> systemd-machined.
Okay, I added systemd package as affected.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received
Quoting RussianNeuroMancer (1529...@bugs.launchpad.net):
> I have systemd installed.
> I mean, I can add systemd package as affected package again?
Yes I think that's fair, though it's more likely a bug in libvirt's
use of systemd-machined.
--
You received this bug notification because you are
I have systemd installed.
I mean, I can add systemd package as affected package again?
--
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 after upgrade to
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+attachment/4545323/+files/kern.log
--
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:
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+attachment/4545324/+files/syslog
--
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
Seems like that won't be enough, so I'll upload two more files just in
case:
--
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 after upgrade to Xenial
To
Virtual machine xml example.
** Attachment added: "vpn2.xml"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+attachment/4545341/+files/vpn2.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could you attach the .xml for the vm?
--
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 after upgrade to Xenial
To manage notifications about this bug go
Oh, do you not have systemd installed?
Libvirt should be working falling back to non-systemd in that case, so
it doesn't excuse the bug, but installing systemd might fix it for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can add systemd again?
--
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 after upgrade to Xenial
To manage notifications about this bug go to:
apport information
** Tags added: apport-collected
** 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
Running a simple vm per https://wiki.ubuntu.com/SergeHallyn_libvirtnest
did not reproduce a failure.
I assume it's something that virt-manager added to the vm definition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Relevant quote from libvirt debug log:
2016-01-07 03:30:49.042+: 1177: info : virDBusCall:1548 : DBUS_METHOD_CALL:
'org.freedesktop.machine1.Manager.CreateMachineWithNetwork' on
'/org/freedesktop/machine1' at 'org.freedesktop.machine1'
2016-01-07 03:30:49.088+: 1177: info :
...but issue is still reproducible with same error message. On this vm
too.
** Attachment added: "libvirtd.log"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+attachment/4545344/+files/libvirtd.log
--
You received this bug notification because you are a member of Ubuntu
> Running a simple vm per https://wiki.ubuntu.com/SergeHallyn_libvirtnest did
> not reproduce a failure.
I grab this xml, correct path to img and iso files, and enable network bridge...
** Attachment added: "cdboot.xml"
Interesting, so that really seems to be a systemd-machined issue.
--
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 after upgrade to Xenial
To manage
Please collect additional information and logs with 'apport-collect
1529079'. In addition having the XML file associated with the
problematic VM may help. Please run 'virsh dumpxml testserver' and
attach to this bug report.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: libvirt (Ubuntu)
Importance: Undecided => 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 after upgrade to Xenial
To manage
** No longer affects: systemd (Ubuntu)
--
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 after upgrade to Xenial
To manage notifications
** No longer affects: systemd (Ubuntu)
--
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 after upgrade to Xenial
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
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:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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:
41 matches
Mail list logo
