I come bearing data!
After a kind of long bisect, the bad commit was:
commit 1e886639791762e89b51aa0507f523c6a1448831
Author: Paolo Bonzini
Date: Thu Jun 29 15:27:41 2017 +0200
vdi: make it thread-safe
And then, when I went to verify it on git master before reporting it
against qemu upstr
Lest anyone think this is resolved, I just experienced it on buster,
running kernel 4.19.0-16-amd64 and 5.2+dfsg-9~bpo10+1 from
buster-backports.
In my case, though, I've used qemu-nbd without difficulty for raw
files on the order of 40G before without difficulty - but this time,
with a VDI of act
So, I started to dig a bit deeper by simply downgrading the qmeu-utils package.
Running the recent version of buster but version qemu-utils_2.8+dfsg-6+deb9u8
(http://snapshot.debian.org/package/qemu/1%3A2.8%2Bdfsg-6%2Bdeb9u8/#qemu-utils_1:3a:2.8:2b:dfsg-6:2b:deb9u8)
works.
All other versions g
I did some more research and found this post, which pretty much is identical to
what I have: https://lists.openwall.net/linux-ext4/2018/01/25/22
Here is some recent output from /var/log/syslog:
Nov 20 13:11:49 debian kernel: [ 160.820705] block nbd1: Connection timed out
Nov 20 13:15:12 debia
Package: qemu-utils
Version: 1:4.1-1+b3
Severity: normal
Dear Maintainer,
I experience the following syptoms since Debian buster. In Debian stretch it
works just fine:
Load Kernel Module: sudo modprobe nbd max_part=16
Create an image: qemeu-image create vdi /path/to/img-file.vdi 120G
Bind the im
5 matches
Mail list logo
