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 for a

And it is still reproducible after reboot after the upgrade, right?

> long time, Kubuntu from 11.04 as I remember. So there is may be something
> ancient that showed up just now. Or not so ancient - maybe some
> upstart->systemd upgrade issue. I have no idea actually what it may be. How I
> can help here find what's going on?
> 
> > 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)
> Still reproducible on my testing Kubuntu 16.04 setup. I can try Ubuntu Server 
> 15.10->16.04 upgrade once again, if necessary. Is it needed if issue still 
> reproducible on updated Kubuntu 16.04?

I'll try the upgrade too.  Thanks for the hint.

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

Title:
  Can't start virtual machines after upgrade to Xenial

Status in libvirt package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  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)
  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
  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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to