Your message dated Tue, 17 May 2016 16:22:48 +0300
with message-id <573b1b28.5040...@msgid.tls.msk.ru>
and subject line Re: Bug#824553: qemu-nbd: devices for partitions are not
created
has caused the Debian Bug report #824553,
regarding qemu-nbd: devices for partitions are not created
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
824553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-utils
Version: 1:2.5+dfsg-5+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
In debian testing weekly build from 2016-04-18 qemu-nbd worked fine, and in
build from 2016-04-25 it stopped working.
Steps to reproduce:
qemu-img create -f qcow2 myimg.qcow2 10G
qemu-system-x86_64 -enable-kvm -hda myimg.qcow2 -cdrom
debian-testing-amd64-DVD-1.iso -m 256 -boot d
sudo modprobe nbd max_part=16 # this works OK - /dev/nbd0,1,... devices are
created
sudo qemu-nbd -c /dev/nbd0 newcd-qemu.qcow2
Result: there are no /dev/nbd0p* devices.
Maybe this will be useful: when I run "sudo qemu-nbd -c /dev/nbd0
newcd-qemu.qcow2" again, it prints this:
/build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_init():L723: Failed to set NBD
socket
/build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_receive_request():L857: read failed
But still, no /dev/nbd0p* devices appear.
I did everything absolutely the same as I always did before, but this time it
did not work.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.5.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages qemu-utils depends on:
ii libaio1 0.3.110-2
ii libc6 2.22-7
ii libgcc1 1:5.3.1-14
ii libglib2.0-0 2.48.0-1
ii libgnutls30 3.4.10-4
ii libnettle6 3.2-1
ii libuuid1 2.28-1
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages qemu-utils recommends:
ii sharutils 1:4.15.2-1
Versions of packages qemu-utils suggests:
ii debootstrap 1.0.80
pn qemu-block-extra <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
17.05.2016 15:34, Igor Liferenko wrote:
> Package: qemu-utils
> Version: 1:2.5+dfsg-5+b1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> In debian testing weekly build from 2016-04-18 qemu-nbd worked fine, and in
> build from 2016-04-25 it stopped working.
It never worked the way you outlined below.
First of all, qemu-nbd does not care about partitions or any other
details of disk images. The only possible explanation of the
"change" you see between two builds (which are built from the
same source!) is that qemu-nbd stopped working for some reason,
returning wrong data to read requests or failing read requests.
This, ofcourse, will prevent many other things from working,
including reading partition tables within qemu-system-x86_64
guests (as it uses the same code) and other things, and including
qemu-nbd for unpartitioned images.
Second, nbd devices are never made partitionable by kernel by
default. One has to use other tools, such as kpartx, to enable
partitions for nbd devices. Nothing changed in qemu about that,
and nothing can ever be changed.
And third, grave, renders package unusable, is way over-estimation,
I use qemu-nbd here quite often, for unpartitioned images too.
And it works quite well for partitioned images, both builds you
mentioned.
So closing the bugreport now.
Thanks,
/mjt
> Steps to reproduce:
>
> qemu-img create -f qcow2 myimg.qcow2 10G
> qemu-system-x86_64 -enable-kvm -hda myimg.qcow2 -cdrom
> debian-testing-amd64-DVD-1.iso -m 256 -boot d
> sudo modprobe nbd max_part=16 # this works OK - /dev/nbd0,1,... devices are
> created
> sudo qemu-nbd -c /dev/nbd0 newcd-qemu.qcow2
>
> Result: there are no /dev/nbd0p* devices.
>
> Maybe this will be useful: when I run "sudo qemu-nbd -c /dev/nbd0
> newcd-qemu.qcow2" again, it prints this:
> /build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_init():L723: Failed to set NBD
> socket
> /build/qemu-gfZfcR/qemu-2.5+dfsg/nbd.c:nbd_receive_request():L857: read
> failed
> But still, no /dev/nbd0p* devices appear.
>
> I did everything absolutely the same as I always did before, but this time it
> did not work.
>
>
> -- System Information:
> Debian Release: stretch/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.5.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages qemu-utils depends on:
> ii libaio1 0.3.110-2
> ii libc6 2.22-7
> ii libgcc1 1:5.3.1-14
> ii libglib2.0-0 2.48.0-1
> ii libgnutls30 3.4.10-4
> ii libnettle6 3.2-1
> ii libuuid1 2.28-1
> ii zlib1g 1:1.2.8.dfsg-2+b1
>
> Versions of packages qemu-utils recommends:
> ii sharutils 1:4.15.2-1
>
> Versions of packages qemu-utils suggests:
> ii debootstrap 1.0.80
> pn qemu-block-extra <none>
>
> -- no debconf information
>
--- End Message ---
