[Bug 1583009] Re: Error starting domain since update

[ChristianEhrhardt]

Thanks Saverio for your ping on this.
I wonder why I haven't seen this yet out of a openstack context, might be just the scale of it but I still wonder. I run all sort of libvirt/qemu upgrade tests on a regular cadence and among others this includes Trusty->Xenial and so far none hit this issue - all guests where fine afterwards and libvirt reachable.
This might be just some sort of race or even special config, but since Mikhail in comment #19 reported to see this on some of more equally configured systems the latter is unlikely.

Since recently in weird "something failed" issues around libvirt there
was apparmor involved I wonder if one of you had uncommon apparmor
reports in dmesg. There are always a few depending on features you use,
but if you could attach the log here we could parse through if there is
an unusual one.

Bumping the prio on the Cloud Archive Task if they have seen that or
reports of it.

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

Title:
  Error starting domain since update

Status in Ubuntu Cloud Archive:
  New
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  Had no problems yesterday using virt-manager to open (or create new
  virtual machines)

  Received updates - unable to now open existing or create:

  Error starting domain: Failed to connect socket to '/var/run/libvirt
  /virtlogd-sock': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libvirt-bin 1.3.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed May 18 07:18:47 2016
  InstallationDate: Installed on 2016-01-11 (127 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160111)
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.virtlogd: [modified]
  modified.conffile..etc.libvirt.libvirtd.conf: [modified]
  modified.conffile..etc.libvirt.libxl.conf: [modified]
  modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf']
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu/networks/default.xml']
  mtime.conffile..etc.init.d.virtlogd: 2016-05-01T04:06:42
  mtime.conffile..etc.libvirt.libvirtd.conf: 2016-05-14T15:01:59
  mtime.conffile..etc.libvirt.libxl.conf: 2016-05-14T15:01:55

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1583009/+subscriptions