Commit 890cbccb0 included in upstream release 5.1.0.
** Changed in: qemu
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1884831
Title:
qemu-nbd fails to
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please
On 6/23/20 4:35 PM, Eric Blake wrote:
Let's get nbd.ko out of the picture. The problem can be reproduced in
user space (here, where I built qemu-nbd to log trace messages to
stderr):
$ truncate --size=3G file
$ qemu-nbd -f raw file --trace=nbd_\*
$ nbdsh -u nbd://localhost:10810 -c
Let's get nbd.ko out of the picture. The problem can be reproduced in
user space (here, where I built qemu-nbd to log trace messages to
stderr):
$ truncate --size=3G file
$ qemu-nbd -f raw file --trace=nbd_\*
$ nbdsh -u nbd://localhost:10810 -c 'h.trim(3*1024*1024*1024,0)'
Traceback (most recent
Hmm, carrying on further, with the nbd-client connection, I'm seeing
that the kernel DID break things into two separate BLKDISCARD calls, as
seen from the nbdkit side of things:
# from the blkdiscard strace:
ioctl(3, BLKGETSIZE64, [5368709120])= 0
ioctl(3, BLKSSZGET, [512]) = 0
** Project changed: qemu => nbd
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1884831
Title:
qemu-nbd fails to discard bigger chunks
Status in nbd:
New
Bug description:
This report is moved
