[Bug 1583009] Re: Error starting domain since update

[Jeff Silverman]

I think I am having the same problem.  I am running 16.04.3 LTS.  I
tried apt-get update and apt-get upgrade, but the software revision
levels did not change, still at 1.3.1.

root at jeff-desktop:/home/jeffs/work/juniper/vmx-17.2R.13# dpkg -l "*libvirt*" 
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                   Version                  Architecture             Description
+++-======================================-========================-========================-=================================================================================
ii  gir1.2-libvirt-glib-1.0:amd64          0.2.2-0.1ubuntu1         amd64                    libvirt glib mainloop integration
ii  libvirt-bin                            1.3.1-1ubuntu10.12       amd64                    programs for the libvirt library
un  libvirt-daemon                         <none>                   <none>                   (no description available)
un  libvirt-daemon-system                  <none>                   <none>                   (no description available)
ii  libvirt-glib-1.0-0:amd64               0.2.2-0.1ubuntu1         amd64                    libvirt glib mainloop integration
ii  libvirt0:amd64                         1.3.1-1ubuntu10.12       amd64                    library for interfacing with different virtualization systems
ii  python-libvirt                         1.3.1-1ubuntu1           amd64                    libvirt Python bindings
root at jeff-desktop:/home/jeffs/work/juniper/vmx-17.2R.13# 

However, I looked at the directory, and I see named sockets but they
don't have the names anticipated:

root at jeff-desktop:/home/jeffs/work/juniper/vmx-17.2R.13# virsh net-edit ?
error: failed to connect to the hypervisor
error: no valid connection
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

root at jeff-desktop:/home/jeffs/work/juniper/vmx-17.2R.13# ls -l /var/run/libvirt/libvirt-sock
ls: cannot access '/var/run/libvirt/libvirt-sock': No such file or directory
root at jeff-desktop:/home/jeffs/work/juniper/vmx-17.2R.13# ls -l /var/run/libvirt
total 0
drwxr-xr-x 2 root root  40 Aug  3 12:58 hostdevmgr
drwxr-xr-x 2 root root  40 Aug  3 12:58 lxc
drwxr-xr-x 2 root root 100 Aug  3 23:02 network
drwxr-xr-x 2 root root  40 Aug  3 12:58 qemu
drwxr-xr-x 2 root root  40 Aug  3 12:58 storage
drwxr-xr-x 2 root root  40 Aug  3 12:58 uml-guest
srw-rw-rw- 1 root root   0 Aug  3 12:58 virtlockd-sock
srw-rw-rw- 1 root root   0 Aug  3 12:58 virtlogd-sock
root at jeff-desktop:/home/jeffs/work/juniper/vmx-17.2R.13# 

What do I do next?

Thank you


Jeff

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