| 2017-03-29 22:20:06 |
Simon Déziel |
bug |
|
|
added bug |
| 2017-03-30 09:59:20 |
Christian Ehrhardt |
libvirt (Ubuntu): status |
New |
Confirmed |
|
| 2017-03-30 09:59:27 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-03-30 09:59:27 |
Christian Ehrhardt |
bug task added |
|
libvirt (Ubuntu Xenial) |
|
| 2017-03-30 09:59:27 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-03-30 09:59:27 |
Christian Ehrhardt |
bug task added |
|
libvirt (Ubuntu Zesty) |
|
| 2017-03-30 09:59:27 |
Christian Ehrhardt |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-03-30 09:59:27 |
Christian Ehrhardt |
bug task added |
|
libvirt (Ubuntu Yakkety) |
|
| 2017-03-30 10:04:38 |
Christian Ehrhardt |
libvirt (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2017-03-30 10:04:40 |
Christian Ehrhardt |
libvirt (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2017-04-05 07:33:20 |
Christian Ehrhardt |
libvirt (Ubuntu Zesty): assignee |
|
ChristianEhrhardt (paelzer) |
|
| 2017-04-05 07:33:30 |
Christian Ehrhardt |
tags |
amd64 apparmor apport-bug xenial |
amd64 apparmor apport-bug server-next xenial |
|
| 2017-04-05 07:33:38 |
Christian Ehrhardt |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2017-04-26 07:35:21 |
Christian Ehrhardt |
tags |
amd64 apparmor apport-bug server-next xenial |
amd64 apparmor apport-bug server-next virt-aa-helper xenial |
|
| 2017-06-13 13:39:55 |
Christian Ehrhardt |
tags |
amd64 apparmor apport-bug server-next virt-aa-helper xenial |
amd64 apparmor apport-bug virt-aa-helper xenial |
|
| 2017-09-18 06:16:43 |
Christian Ehrhardt |
libvirt (Ubuntu Yakkety): status |
Confirmed |
Won't Fix |
|
| 2017-09-18 06:16:46 |
Christian Ehrhardt |
libvirt (Ubuntu): status |
Confirmed |
In Progress |
|
| 2017-09-18 06:16:51 |
Christian Ehrhardt |
libvirt (Ubuntu Zesty): assignee |
ChristianEhrhardt (paelzer) |
|
|
| 2017-09-19 06:31:56 |
Christian Ehrhardt |
libvirt (Ubuntu): status |
In Progress |
Triaged |
|
| 2017-09-19 09:09:09 |
Christian Ehrhardt |
summary |
Apparmor prevents using ZFS storage pools |
Apparmor prevents using storage pools |
|
| 2017-09-19 09:16:41 |
Christian Ehrhardt |
libvirt (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-09-19 09:36:19 |
Christian Ehrhardt |
description |
Apparmor prevents qemu-kvm guests from using ZFS volumes.
[Impact]
* ZFS storage pools are not usable.
[Test Case]
0) Create a zpool (system specific so not documented here)
1) Create a ZFS storage pool (named like your zpool, "internal" here)
virsh pool-define-as internal zfs
virsh pool-start internal
2) Create a volume
virsh vol-create-as internal foo 2G
2) Create a KVM guest
4) Edit the guest's XML profile to use the ZFS volume (zvol)
<disk type='volume' device='disk'>
<driver name='qemu' type='raw' cache='none'/>
<source pool='internal' volume='foo'/>
<target dev='vda' bus='virtio'/>
</disk>
5) Start the guest
The guest refuses to start:
# virsh start nms
error: Failed to start domain foo
error: internal error: process exited while connecting to monitor: 2017-03-29T22:07:31.507017Z qemu-system-x86_64: -drive file=/dev/zvol/internal/foo,format=raw,if=none,id=drive-virtio-disk0,cache=none: Could not open '/dev/zvol/internal/foo': Permission denied
dmesg reveals the culprit:
apparmor="DENIED" operation="open" profile="libvirt-988a8c25-5190-4762-8170-55dc75fc66ca" name="/dev/zd224" pid=23052 comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=109 ouid=109
apparmor="DENIED" operation="open" profile="libvirt-988a8c25-5190-4762-8170-55dc75fc66ca" name="/dev/zd224" pid=23052 comm="qemu-system-x86" requested_mask="wr" denied_mask="wr" fsuid=109 ouid=109
Checking /etc/apparmor.d/libvirt/libvirt-$UUID.files shows that no "/dev/zdXX" has been added.
[Additional info]
# lsb_release -rd
Description: Ubuntu 16.04.2 LTS
Release: 16.04
# apt-cache policy libvirt-bin apparmor linux-image-generic
libvirt-bin:
Installed: 1.3.1-1ubuntu10.8
Candidate: 1.3.1-1ubuntu10.8
Version table:
*** 1.3.1-1ubuntu10.8 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.3.1-1ubuntu10 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
apparmor:
Installed: 2.10.95-0ubuntu2.5
Candidate: 2.10.95-0ubuntu2.5
Version table:
*** 2.10.95-0ubuntu2.5 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.10.95-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
linux-image-generic:
Installed: 4.4.0.70.76
Candidate: 4.4.0.70.76
Version table:
*** 4.4.0.70.76 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
100 /var/lib/dpkg/status
4.4.0.21.22 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libvirt-bin 1.3.1-1ubuntu10.8
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Mar 29 17:48:06 2017
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.libvirt-guests: [modified]
modified.conffile..etc.libvirt.qemu.conf: [modified]
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.default.libvirt-guests: 2016-08-29T21:09:57.632048
mtime.conffile..etc.libvirt.qemu.conf: 2017-03-29T17:26:03.924234
mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2016-04-23T19:24:13.505208 |
Apparmor prevents qemu-kvm guests from using ZFS volumes.
[Impact]
* storage pools are not usable.
Examples with zfs and LVM pools
[Test Case 1]
# Prep ZFS
1) Create a zpool
$ for i in $(seq 1 3); do dd if=/dev/zero of=/tmp/fdisk${i} bs=1M count=1024; done
$ sudo zpool create internal /tmp/fdisk*
2) Create a ZFS storage pool and volume (named like your zpool, "internal" here)
$ virsh pool-define-as internal zfs
$ virsh pool-start internal
$ virsh vol-create-as internal foo 2G
# prep LVM
4) prepare a (fake) LVM
$ for i in $(seq 1 3); do dd if=/dev/zero of=/tmp/lvdisk${i} bs=1M count=1024; done
$ sync
$ DISKS=$(for i in $(seq 1 3); do sudo losetup -f show /tmp/lvdisk${i}; done)
$ sudo pvcreate --verbose $DISKS
$ sudo vgcreate --verbose testvg $DISKS
5) Create LVM Pool and volume
$ virsh pool-define-as testvg logical
$ virsh pool-start testvg
$ virsh vol-create-as testvg guest1 2G
# Prep Guest and use Pools
6) Create a KVM guest e.g. via uvtool
$ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=xenial
$ ssh-keygen
$ uvt-kvm create --password=ubuntu testguest release=xenial arch=amd64 label=daily
7) Edit the guest's XML profile to use the ZFS and LVM volumes (zvol)
<disk type='volume' device='disk'>
<driver name='qemu' type='raw' cache='none'/>
<source pool='internal' volume='foo'/>
<target dev='vda' bus='virtio'/>
</disk>
<disk type='volume' device='disk'>
<driver name='qemu' type='raw'/>
<source pool='testvg' volume='guest1'/>
<target dev='vda' bus='virtio'/>
</disk>
8) Start the guest
The guest refuses to start:
# virsh start nms
error: Failed to start domain foo
error: internal error: process exited while connecting to monitor: 2017-03-29T22:07:31.507017Z qemu-system-x86_64: -drive file=/dev/zvol/internal/foo,format=raw,if=none,id=drive-virtio-disk0,cache=none: Could not open '/dev/zvol/internal/foo': Permission denied
dmesg reveals the culprit:
apparmor="DENIED" operation="open" profile="libvirt-988a8c25-5190-4762-8170-55dc75fc66ca" name="/dev/zd224" pid=23052 comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=109 ouid=109
apparmor="DENIED" operation="open" profile="libvirt-988a8c25-5190-4762-8170-55dc75fc66ca" name="/dev/zd224" pid=23052 comm="qemu-system-x86" requested_mask="wr" denied_mask="wr" fsuid=109 ouid=109
Checking /etc/apparmor.d/libvirt/libvirt-$UUID.files shows that no "/dev/zdXX" has been added.
[Additional info]
# lsb_release -rd
Description: Ubuntu 16.04.2 LTS
Release: 16.04
# apt-cache policy libvirt-bin apparmor linux-image-generic
libvirt-bin:
Installed: 1.3.1-1ubuntu10.8
Candidate: 1.3.1-1ubuntu10.8
Version table:
*** 1.3.1-1ubuntu10.8 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.3.1-1ubuntu10 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
apparmor:
Installed: 2.10.95-0ubuntu2.5
Candidate: 2.10.95-0ubuntu2.5
Version table:
*** 2.10.95-0ubuntu2.5 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.10.95-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
linux-image-generic:
Installed: 4.4.0.70.76
Candidate: 4.4.0.70.76
Version table:
*** 4.4.0.70.76 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
100 /var/lib/dpkg/status
4.4.0.21.22 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libvirt-bin 1.3.1-1ubuntu10.8
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Mar 29 17:48:06 2017
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.libvirt-guests: [modified]
modified.conffile..etc.libvirt.qemu.conf: [modified]
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.default.libvirt-guests: 2016-08-29T21:09:57.632048
mtime.conffile..etc.libvirt.qemu.conf: 2017-03-29T17:26:03.924234
mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2016-04-23T19:24:13.505208 |
|
| 2017-12-05 10:38:55 |
Hervé BRY |
bug |
|
|
added subscriber Hervé BRY |
| 2018-01-10 15:56:49 |
Christian Ehrhardt |
summary |
Apparmor prevents using storage pools |
Apparmor prevents using storage pools and hostdev networks |
|
| 2018-01-26 08:00:37 |
Christian Ehrhardt |
tags |
amd64 apparmor apport-bug virt-aa-helper xenial |
amd64 apparmor apport-bug libvirt-apparmor-dev virt-aa-helper xenial |
|
| 2018-03-18 11:45:44 |
Oliver Brakmann |
bug |
|
|
added subscriber Oliver Brakmann |
| 2018-06-20 17:30:52 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2018-10-19 05:31:41 |
David A. Desrosiers |
bug |
|
|
added subscriber David A. Desrosiers |
| 2019-03-24 18:37:23 |
Nicolas Wild |
bug |
|
|
added subscriber Nicolas Wild |
| 2019-03-25 08:39:18 |
Christian Ehrhardt |
libvirt (Ubuntu Xenial): status |
Confirmed |
Won't Fix |
|
| 2019-03-25 08:39:20 |
Christian Ehrhardt |
libvirt (Ubuntu Zesty): status |
Confirmed |
Won't Fix |
|
| 2019-05-31 16:48:59 |
Vincent Vanlaer |
bug |
|
|
added subscriber Vincent Vanlaer |
| 2020-02-04 01:24:13 |
Garry Lawrence |
attachment added |
|
virt-aa-helper-support-pools.patch https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1677398/+attachment/5325076/+files/virt-aa-helper-support-pools.patch |
|
| 2020-02-04 04:29:08 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apparmor apport-bug libvirt-apparmor-dev virt-aa-helper xenial |
amd64 apparmor apport-bug libvirt-apparmor-dev patch virt-aa-helper xenial |
|
| 2020-02-04 04:29:18 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2020-03-01 10:15:39 |
cbachert |
bug |
|
|
added subscriber PelzigesOhr |
| 2020-05-26 08:08:59 |
Christian Ehrhardt |
bug |
|
|
added subscriber Christian Ehrhardt |
| 2020-05-26 08:13:10 |
Christian Ehrhardt |
bug |
|
|
added subscriber Garry Lawrence |
| 2020-05-26 09:45:56 |
Christian Ehrhardt |
description |
Apparmor prevents qemu-kvm guests from using ZFS volumes.
[Impact]
* storage pools are not usable.
Examples with zfs and LVM pools
[Test Case 1]
# Prep ZFS
1) Create a zpool
$ for i in $(seq 1 3); do dd if=/dev/zero of=/tmp/fdisk${i} bs=1M count=1024; done
$ sudo zpool create internal /tmp/fdisk*
2) Create a ZFS storage pool and volume (named like your zpool, "internal" here)
$ virsh pool-define-as internal zfs
$ virsh pool-start internal
$ virsh vol-create-as internal foo 2G
# prep LVM
4) prepare a (fake) LVM
$ for i in $(seq 1 3); do dd if=/dev/zero of=/tmp/lvdisk${i} bs=1M count=1024; done
$ sync
$ DISKS=$(for i in $(seq 1 3); do sudo losetup -f show /tmp/lvdisk${i}; done)
$ sudo pvcreate --verbose $DISKS
$ sudo vgcreate --verbose testvg $DISKS
5) Create LVM Pool and volume
$ virsh pool-define-as testvg logical
$ virsh pool-start testvg
$ virsh vol-create-as testvg guest1 2G
# Prep Guest and use Pools
6) Create a KVM guest e.g. via uvtool
$ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=xenial
$ ssh-keygen
$ uvt-kvm create --password=ubuntu testguest release=xenial arch=amd64 label=daily
7) Edit the guest's XML profile to use the ZFS and LVM volumes (zvol)
<disk type='volume' device='disk'>
<driver name='qemu' type='raw' cache='none'/>
<source pool='internal' volume='foo'/>
<target dev='vda' bus='virtio'/>
</disk>
<disk type='volume' device='disk'>
<driver name='qemu' type='raw'/>
<source pool='testvg' volume='guest1'/>
<target dev='vda' bus='virtio'/>
</disk>
8) Start the guest
The guest refuses to start:
# virsh start nms
error: Failed to start domain foo
error: internal error: process exited while connecting to monitor: 2017-03-29T22:07:31.507017Z qemu-system-x86_64: -drive file=/dev/zvol/internal/foo,format=raw,if=none,id=drive-virtio-disk0,cache=none: Could not open '/dev/zvol/internal/foo': Permission denied
dmesg reveals the culprit:
apparmor="DENIED" operation="open" profile="libvirt-988a8c25-5190-4762-8170-55dc75fc66ca" name="/dev/zd224" pid=23052 comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=109 ouid=109
apparmor="DENIED" operation="open" profile="libvirt-988a8c25-5190-4762-8170-55dc75fc66ca" name="/dev/zd224" pid=23052 comm="qemu-system-x86" requested_mask="wr" denied_mask="wr" fsuid=109 ouid=109
Checking /etc/apparmor.d/libvirt/libvirt-$UUID.files shows that no "/dev/zdXX" has been added.
[Additional info]
# lsb_release -rd
Description: Ubuntu 16.04.2 LTS
Release: 16.04
# apt-cache policy libvirt-bin apparmor linux-image-generic
libvirt-bin:
Installed: 1.3.1-1ubuntu10.8
Candidate: 1.3.1-1ubuntu10.8
Version table:
*** 1.3.1-1ubuntu10.8 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.3.1-1ubuntu10 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
apparmor:
Installed: 2.10.95-0ubuntu2.5
Candidate: 2.10.95-0ubuntu2.5
Version table:
*** 2.10.95-0ubuntu2.5 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.10.95-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
linux-image-generic:
Installed: 4.4.0.70.76
Candidate: 4.4.0.70.76
Version table:
*** 4.4.0.70.76 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
100 /var/lib/dpkg/status
4.4.0.21.22 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libvirt-bin 1.3.1-1ubuntu10.8
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Mar 29 17:48:06 2017
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.libvirt-guests: [modified]
modified.conffile..etc.libvirt.qemu.conf: [modified]
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.default.libvirt-guests: 2016-08-29T21:09:57.632048
mtime.conffile..etc.libvirt.qemu.conf: 2017-03-29T17:26:03.924234
mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2016-04-23T19:24:13.505208 |
Apparmor prevents qemu-kvm guests from using ZFS volumes.
[Impact]
* storage pools are not usable.
Examples with zfs and LVM pools
[Test Case 1]
# Prep ZFS
1) Create a zpool
$ for i in $(seq 1 3); do dd if=/dev/zero of=/tmp/fdisk${i} bs=1M count=1024; done
$ sudo zpool create internal /tmp/fdisk*
2) Create a ZFS storage pool and volume (named like your zpool, "internal" here)
$ virsh pool-define-as internal zfs
$ virsh pool-start internal
$ virsh vol-create-as internal foo 2G
# prep LVM
4) prepare a (fake) LVM
$ for i in $(seq 1 3); do dd if=/dev/zero of=/tmp/lvdisk${i} bs=1M count=1024; done
$ sync
$ DISKS=$(for i in $(seq 1 3); do sudo losetup -f --show /tmp/lvdisk${i}; done)
$ sudo pvcreate --verbose $DISKS
$ sudo vgcreate --verbose testvg $DISKS
5) Create LVM Pool and volume
$ virsh pool-define-as testvg logical
$ virsh pool-start testvg
$ virsh vol-create-as testvg guest1 2G
# Prep Guest and use Pools
6) Create a KVM guest e.g. via uvtool
$ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=xenial
$ ssh-keygen
$ uvt-kvm create --password=ubuntu testguest release=xenial arch=amd64 label=daily
7) Edit the guest's XML profile to use the ZFS and LVM volumes (zvol)
<disk type='volume' device='disk'>
<driver name='qemu' type='raw' cache='none'/>
<source pool='internal' volume='foo'/>
<target dev='vda' bus='virtio'/>
</disk>
<disk type='volume' device='disk'>
<driver name='qemu' type='raw'/>
<source pool='testvg' volume='guest1'/>
<target dev='vda' bus='virtio'/>
</disk>
8) Start the guest
The guest refuses to start:
# virsh start nms
error: Failed to start domain foo
error: internal error: process exited while connecting to monitor: 2017-03-29T22:07:31.507017Z qemu-system-x86_64: -drive file=/dev/zvol/internal/foo,format=raw,if=none,id=drive-virtio-disk0,cache=none: Could not open '/dev/zvol/internal/foo': Permission denied
dmesg reveals the culprit:
apparmor="DENIED" operation="open" profile="libvirt-988a8c25-5190-4762-8170-55dc75fc66ca" name="/dev/zd224" pid=23052 comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=109 ouid=109
apparmor="DENIED" operation="open" profile="libvirt-988a8c25-5190-4762-8170-55dc75fc66ca" name="/dev/zd224" pid=23052 comm="qemu-system-x86" requested_mask="wr" denied_mask="wr" fsuid=109 ouid=109
Checking /etc/apparmor.d/libvirt/libvirt-$UUID.files shows that no "/dev/zdXX" has been added.
[Additional info]
# lsb_release -rd
Description: Ubuntu 16.04.2 LTS
Release: 16.04
# apt-cache policy libvirt-bin apparmor linux-image-generic
libvirt-bin:
Installed: 1.3.1-1ubuntu10.8
Candidate: 1.3.1-1ubuntu10.8
Version table:
*** 1.3.1-1ubuntu10.8 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
1.3.1-1ubuntu10 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
apparmor:
Installed: 2.10.95-0ubuntu2.5
Candidate: 2.10.95-0ubuntu2.5
Version table:
*** 2.10.95-0ubuntu2.5 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.10.95-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
linux-image-generic:
Installed: 4.4.0.70.76
Candidate: 4.4.0.70.76
Version table:
*** 4.4.0.70.76 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
100 /var/lib/dpkg/status
4.4.0.21.22 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libvirt-bin 1.3.1-1ubuntu10.8
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Mar 29 17:48:06 2017
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.libvirt-guests: [modified]
modified.conffile..etc.libvirt.qemu.conf: [modified]
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.default.libvirt-guests: 2016-08-29T21:09:57.632048
mtime.conffile..etc.libvirt.qemu.conf: 2017-03-29T17:26:03.924234
mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2016-04-23T19:24:13.505208 |
|
| 2020-05-26 12:41:19 |
Christian Ehrhardt |
bug |
|
|
added subscriber Jamie Strandboge |
| 2020-09-06 20:43:09 |
giannoug |
bug |
|
|
added subscriber George Giannou |
| 2021-02-23 09:49:12 |
Christian Ehrhardt |
bug watch added |
|
https://gitlab.com/libvirt/libvirt/-/issues/135 |
|
| 2021-02-23 09:49:21 |
Christian Ehrhardt |
bug task added |
|
libvirt |
|
| 2021-04-27 08:10:22 |
Dennis |
bug |
|
|
added subscriber Dennis |
| 2022-05-20 15:48:27 |
Bug Watch Updater |
libvirt: status |
Unknown |
New |
|
| 2022-11-24 14:19:08 |
Jacob Yundt |
bug |
|
|
added subscriber Jacob Yundt |
| 2023-05-11 09:00:10 |
Christian Ehrhardt |
libvirt (Ubuntu): assignee |
Christian Ehrhardt (paelzer) |
|
|
| 2023-05-17 12:47:03 |
Dan Streetman |
removed subscriber Dan Streetman |
|
|
|
