libvirt-bin configuration after installatioin fails

Bug #1506378 reported by Mustafa Muhammad
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Trying to install libvirt-bin fail

mustafa@mustafa-All-Series:~$ sudo apt install libvirt-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  qemu-kvm qemu radvd
The following NEW packages will be installed:
  libvirt-bin
0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade.
Need to get 0 B/2,290 kB of archives.
After this operation, 12.3 MB of additional disk space will be used.
Selecting previously unselected package libvirt-bin.
(Reading database ... 193743 files and directories currently installed.)
Preparing to unpack .../libvirt-bin_1.2.16-2ubuntu11_amd64.deb ...
Unpacking libvirt-bin (1.2.16-2ubuntu11) ...
Processing triggers for man-db (2.7.4-1) ...
Processing triggers for systemd (225-1ubuntu7) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up libvirt-bin (1.2.16-2ubuntu11) ...
invoke-rc.d: Unit libvirt-bin.service is masked
Job for libvirt-bin.service failed because the control process exited with error code. See "systemctl status libvirt-bin.service" and "journalctl -xe" for details.
invoke-rc.d: initscript libvirt-bin, action "start" failed.
dpkg: error processing package libvirt-bin (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 libvirt-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libvirt-bin 1.2.16-2ubuntu11
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Oct 15 11:35:41 2015
InstallationDate: Installed on 2015-10-13 (1 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf']

Revision history for this message
Mustafa Muhammad (mustafa.muhammad) wrote :
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

That is very odd. Unless /etc is a read-only filesystemd I don't see why root would be denied permission to write to that file, and there are no apparmor denials in the kernel log. Could you please attach the files

/etc/apt/sources.list
/etc/apt/sources.list.d/*
/var/log/apt/history.log
/var/log/apt/term.log

and show the result of

ls -l /etc/libvirt
cat /proc/self/mountinfo

Changed in libvirt (Ubuntu):
status: New → Incomplete
Revision history for this message
Mustafa Muhammad (mustafa.muhammad) wrote :
Download full text (4.4 KiB)

mustafa@mustafa-All-Series:~$ ls -l /etc/libvirt
total 76
drwxr-xr-x 2 root root 4096 Sep 29 04:02 hooks
-rw-r--r-- 1 root root 518 Sep 29 04:02 libvirt.conf
-rw-r--r-- 1 root root 14376 Sep 29 04:02 libvirtd.conf
-rw-r--r-- 1 root root 834 Sep 29 04:02 libxl.conf
-rw-r--r-- 1 root root 2169 Sep 29 04:02 libxl-lockd.conf
-rw-r--r-- 1 root root 1235 Sep 29 04:02 lxc.conf
drwxr-xr-x 2 root root 4096 Oct 15 11:30 nwfilter
drwxr-xr-x 3 root root 4096 Oct 15 09:50 qemu
-rw------- 1 root root 18987 Sep 29 04:02 qemu.conf
-rw-r--r-- 1 root root 2169 Sep 29 04:02 qemu-lockd.conf
-rw-r--r-- 1 root root 2134 Sep 29 04:02 virtlockd.conf
-rw-r--r-- 1 root root 1217 Sep 29 04:02 virt-login-shell.conf

mustafa@mustafa-All-Series:~$ cat /proc/self/mountinfo
19 25 0:18 / /sys rw,nosuid,nodev,noexec,relatime shared:7 - sysfs sysfs rw
20 25 0:4 / /proc rw,nosuid,nodev,noexec,relatime shared:13 - proc proc rw
21 25 0:6 / /dev rw,nosuid,relatime shared:2 - devtmpfs udev rw,size=8037228k,nr_inodes=2009307,mode=755
22 21 0:14 / /dev/pts rw,nosuid,noexec,relatime shared:3 - devpts devpts rw,gid=5,mode=620,ptmxmode=000
23 25 0:19 / /run rw,nosuid,noexec,relatime shared:5 - tmpfs tmpfs rw,size=1610920k,mode=755
25 0 8:3 / / rw,relatime shared:1 - ext4 /dev/sda3 rw,errors=remount-ro,data=ordered
26 19 0:12 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:8 - securityfs securityfs rw
27 21 0:21 / /dev/shm rw,nosuid,nodev shared:4 - tmpfs tmpfs rw
28 23 0:22 / /run/lock rw,nosuid,nodev,noexec,relatime shared:6 - tmpfs tmpfs rw,size=5120k
29 19 0:23 / /sys/fs/cgroup rw shared:9 - tmpfs tmpfs rw,mode=755
30 29 0:24 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:10 - cgroup cgroup rw,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
31 19 0:25 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:11 - pstore pstore rw
32 19 0:26 / /sys/firmware/efi/efivars rw,nosuid,nodev,noexec,relatime shared:12 - efivarfs efivarfs rw
33 29 0:27 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime shared:14 - cgroup cgroup rw,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event
34 29 0:28 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:15 - cgroup cgroup rw,memory
35 29 0:29 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime shared:16 - cgroup cgroup rw,cpu,cpuacct
36 29 0:30 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:17 - cgroup cgroup rw,devices
37 29 0:31 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:18 - cgroup cgroup rw,freezer
38 29 0:32 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime shared:19 - cgroup cgroup rw,net_cls,net_prio
39 29 0:33 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime shared:20 - cgroup cgroup rw,hugetlb,release_agent=/run/cgmanager/agent...

Read more...

Revision history for this message
Mustafa Muhammad (mustafa.muhammad) wrote :
Revision history for this message
Mustafa Muhammad (mustafa.muhammad) wrote :
Revision history for this message
Serge Hallyn (serge-hallyn) wrote : Re: [Bug 1506378] Re: libvirt-bin configuration after installatioin fails

Odd, the qemu.conf error in the bug description does not show up in
the term.log.

What does

sudo systemctl status libvirt-bin.service

show?

Revision history for this message
Mustafa Muhammad (mustafa.muhammad) wrote :

mustafa@mustafa-All-Series:~$ sudo systemctl status libvirt-bin.service
[sudo] password for mustafa:
● libvirt-bin.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since Thu 2015-10-15 20:20:49 AST; 4min 54s ago
     Docs: man:libvirtd(8)
           http://libvirt.org
  Process: 924 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited, status=1/FAILURE)
 Main PID: 924 (code=exited, status=1/FAILURE)
   CGroup: /system.slice/libvirt-bin.service

Oct 15 20:20:48 mustafa-All-Series systemd[1]: Failed to start Virtualization daemon.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Unit entered failed state.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Failed with result 'exit-code'.
Oct 15 20:20:49 mustafa-All-Series systemd[1]: libvirt-bin.service: Service hold-off time ove...rt.
Oct 15 20:20:49 mustafa-All-Series systemd[1]: Stopped Virtualization daemon.
Oct 15 20:20:49 mustafa-All-Series systemd[1]: libvirt-bin.service: Start request repeated to...ly.
Oct 15 20:20:49 mustafa-All-Series systemd[1]: Failed to start Virtualization daemon.
Oct 15 20:20:49 mustafa-All-Series systemd[1]: libvirt-bin.service: Unit entered failed state.
Oct 15 20:20:49 mustafa-All-Series systemd[1]: libvirt-bin.service: Failed with result 'start...t'.
Hint: Some lines were ellipsized, use -l to show in full.

Revision history for this message
Mustafa Muhammad (mustafa.muhammad) wrote :

mustafa@mustafa-All-Series:~$ sudo journalctl -u libvirt-bin
-- Logs begin at Thu 2015-10-15 20:20:47 AST, end at Thu 2015-10-15 20:26:42 AST. --
Oct 15 20:20:48 mustafa-All-Series systemd[1]: Starting Virtualization daemon...
Oct 15 20:20:48 mustafa-All-Series libvirtd[786]: /usr/sbin/libvirtd: initialization failed
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 20:20:48 mustafa-All-Series systemd[1]: Failed to start Virtualization daemon.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Unit entered failed state.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Failed with result 'exit-code'.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: Stopped Virtualization daemon.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: Starting Virtualization daemon...
Oct 15 20:20:48 mustafa-All-Series libvirtd[817]: /usr/sbin/libvirtd: initialization failed
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 20:20:48 mustafa-All-Series systemd[1]: Failed to start Virtualization daemon.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Unit entered failed state.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Failed with result 'exit-code'.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: Stopped Virtualization daemon.
Oct 15 20:20:48 mustafa-All-Series systemd[1]: Starting Virtualization daemon...

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

What do you get when you do:

sudo ls -l /etc/libvirt/qemu.conf
sudo getfacl /etc/libvirt/qemu.conf
sudo libvirtd

and please attach the file 'libvirtd.out' after doing:

sudo strace -f -olibvirtd.out libvirtd

Revision history for this message
Mustafa Muhammad (mustafa.muhammad) wrote :

Now I am on new installation and this issue doesn't happen anymore.
You can mark it as closed as I can't reproduce it anymore.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Thanks for the update.

Changed in libvirt (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

(marking 'invalid' meaning 'cannot reproduce any more')

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.