[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1905979
Title:
Check if F_
That is indeed the source and patches, but I wanted to follow their git
repo for easier maintenance. Surely they must have one.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1905979
Title:
Check if
The kernel version is Linux hostname 4.15.0-124-generic #127-Ubuntu SMP
Fri Nov 6 10:54:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1905979
Title:
Check
Look in the same directory as that .deb link above - the the files
ending in orig.tar.gz (upstream source) and files ending in
debian.tar.xz (downstream modifications)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launc
Interesting. Thanks for the link.
The file system we are using is the Quobyte file system (2.24.1)
(https://www.quobyte.com/), which works via FUSE.
We've had problems with OFD locks with this file system in the past, so my
first thought, seeing the error in comment #1, was that those would be
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1905979
Title:
Check if F_OFD_SETLK is supported may give wrong result
Status in QEMU:
Incomple
In this thread, it is pointed out that support for OFD is provided by
the generic VFS layer in the kernel, so there should never be a
situation where one filesystem supports OFD and another does not support
OFD:
https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg05264.html
Can you say wha
This is rather serious, since it causes VMs to crash:
Unexpected error in raw_check_lock_bytes() at
/build/qemu-PKI6mj/qemu-4.2/block/file-posix.c:796:
Failed to get "write" lock
2020-11-23 11:32:27.810+: shutting down, reason=crashed
when openstack attempts to create a snapshot.
--
You re
