"Solved" it. Added "/dev/sd* rk" in /etc/apparmor.d/abstractions
/libvirt-qemu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709818
Title:
Failed to lock byte 100
To manage notifications about th
Problem is just in qcow2 backed by physical drives, -- if no backing
file of it is just a file then all is ok. So, is it possible to disable
locking in such cases?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I have just faced that bug after upgrade from ubuntu 16.04 to 18.04.1.
I create VMs with qcow2 volumes backed by physical raw drives. Now it
is unable to create VM via virt-install because of "unable to lock byte
100" bug. So, since libvirt version in 18.04.1 is already 4.0.0, is
there a regressi
Hi kvaps, what you reported is a particular discussion on the handling of
snapshots.
The bug here was the general introduction of image locking that caused some
issues in formerly working cases.
The patch you referred to never made it upstream and that indicates that there
was either another so
Affects Artful and Bionic
Here is published fix for qemu:
https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg06405.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709818
Title:
Failed to
** Tags added: qemu-file-locking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709818
Title:
Failed to lock byte 100
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
This bug was fixed in the package libvirt - 3.6.0-1ubuntu1
---
libvirt (3.6.0-1ubuntu1) artful; urgency=medium
* Merged with Debian unstable (3.6)
This closes several bugs:
- aarch64: improved chardev handling (LP: #1697610)
- Forbid locking memory without memtune (LP: #
Qemu is affected and effectively the trigger, but the fix will have to
take place in libvirt - so I added a task but set it to won't fix to
reflect that.
** Changed in: qemu (Ubuntu)
Status: New => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: New => In Progress
--
You receive
