[Bug 1583009] Re: Error starting domain since update

ChristianEhrhardt 1583009 at bugs.launchpad.net
Tue Jan 30 06:39:02 UTC 2018


> Sorry about the confusion.

Never mind, now things are clear - thanks!

> 1- update libvirt
> 2- virst list (I see running vms)
> 3- try to stop the vm with nova, "openstack server stop uuid"
> 4- virsh list. (now it hangs)
>

I'd need insight from the OpenStack Team on this how nova might interfere here.
This is out of my area of expertise now - but UCA Team is already
subscribed so that should be ok.

>
> anyhow, how does a reload of those process could even work ?
> If the PID is kept the same it's defenitely not the "new version" that is running.
> I think it would be better to restart the services instead of only reloading them.

This is intentional and ok.
If you'd fully restart the service it would loose some of the logs.
Instead see [1] in section "signals" virtlogd is designed to reload
itself via exeve.
This is how it is same-pid but new code while maitaining open logs.

[1]: http://manpages.ubuntu.com/manpages/bionic/en/man8/virtlogd.8.html

-- 
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:
  Incomplete
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



More information about the Ubuntu-openstack-bugs mailing list