This bug was fixed in the package qemu - 1:4.0+dfsg-0ubuntu9.2
---
qemu (1:4.0+dfsg-0ubuntu9.2) eoan; urgency=medium
* d/p/ubuntu/lp-1848556-curl-Handle-success-in-multi_check_completion.patch:
fix a potential hang when qemu or qemu-img where accessing http backed
disks via
Eoan - without fix -> hang
With fix:
qemu-img check http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img
No errors were found on the image.
Hello Rod, or anyone else affected,
Accepted qemu into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:4.0+dfsg-
0ubuntu9.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This was tonight first accepted and then immediately rejected as it was
surpassed by a security fix.
=> Rebased and uploaded 1:4.0+dfsg-0ubuntu9.2 to eoan-unapproved again.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Focal is complete the MPs reviewed, SRU Teamplates ready and pre-tests done.
Uploading to E-unapproved for the SRU Teams consideration.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1848556
Title:
This bug was fixed in the package qemu - 1:4.0+dfsg-0ubuntu10
---
qemu (1:4.0+dfsg-0ubuntu10) focal; urgency=medium
* d/p/ubuntu/lp-1848556-curl-Handle-success-in-multi_check_completion.patch:
fix a potential hang when qemu or qemu-img where accessing http backed
disks via
FYI: uploaded to 20.04 Focal, considering SRUs (Eoan) after this
completes
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1848556
Title:
qemu-img check failing on remote image in Eoan
Status in
Now that Focal is open I have opened proper Focal MP replacing the old one and
also an Eoan SRU MP right away.
=>
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374770
=>
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374771
--
You received
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374771
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1848556
Title:
qemu-img check failing on
** Changed in: qemu (Ubuntu Eoan)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: qemu (Ubuntu Focal)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374770
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1848556
Title:
qemu-img check failing on
I managed to check the PPA version just now, and it's working fine.
Thanks for the quick fix!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1848556
Title:
qemu-img check failing on remote image in
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/374447
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1848556
Title:
qemu-img check failing on
For me with the version from the PPA works fine on local as well as remote http
connections.
Thanks @Max for the fix.
@Rod:
Waiting for you to test and verify based on the PPA.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
@Rod: Your self built issue seems like at config/make time there were
not all build deps available. I have put a test build in PPA [1], could
you give that one a try on your end as well?
[1]: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1848556-qemu-
img-curl-hang-eoan
--
You received
** Description changed:
+ Ubuntu SRU Template:
+
+ [Impact]
+
+ * There is fallout due to changes in libcurl that affect qemu and might
+lead to a hang.
+
+ * Fix by backporting the upstream fix
+
+ [Test Case]
+
+ * If you have network just run
+$ qemu-img check
Hi Rod,
You don’t need to add anything, but maybe there’s some library missing.
--enable-curl should force support and then tell you whether there’s
something missing.
Max
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Hi Christian,
I don’t see any issue but the fact that the whole series should be
backported (0487861685294660b23bc146e1ebd5304aa8bbe0 through
bfb23b480a49114315877aacf700b49453e0f9d9, maybe also c34dc07f9f01cf686,
but that isn’t strictly necessary).
Max
--
You received this bug notification
Hi Max,
libcurl 7.65.3-1ubuntu3 and was >7.59 for several releases (more than a year at
least) - so there must be something else going on that this triggers now.
But never the less with the fix from [1] I can again get it to work
successfully.
I think I should backport that to our qemu 4.0 in
I tried qemu from git, but I get an "unknown protocol" error when I try
to access an image via HTTP:
$ ./qemu-img check http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img
qemu-img: Could not open
'http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img': Unknown protocol
'http'
Is
Hi,
Could you try the qemu’s master branch?
bfb23b480a49114315877aacf700b49453e0f9d9 has fixed an issue that sounds
very much like this. The problem in that case is that libcurl 7.59.0
changed behavior, so bisecting qemu will not produce results.
Max
--
You received this bug notification
Since it seemed so easy, while bisecting I found that it hangs with
v4.0.0 and v3.1.0 from git and even v3.0.0.
Since the reported good version was 3.1 I began to wonder if I might have
overlooked something.
I wondered if it might be e.g. the apache version providing a different
behavior on
Quick checks:
- does not depend on the exact image, e.g.
https://cloud-images.ubuntu.com/eoan/current/eoan-server-cloudimg-amd64.img or
https://download.fedoraproject.org/pub/fedora/linux/releases/30/Cloud/x86_64/images/Fedora-Cloud-Base-30-1.2.x86_64.qcow2
hang as well
- the former qemu 3.1
The stuck poll is at:
#0 0x7fafb935ad26 in __GI_ppoll (fds=0x560dba615670, nfds=1,
timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at
../sysdeps/unix/sysv/linux/ppoll.c:39
#1 0x560db89550b9 in ppoll (__ss=0x0, __timeout=0x0, __nfds=, __fds=) at
Hi Rod,
I did try to recreate with the qemu version that you have.
$ apt install apache2 qemu-system-x86
$ qemu-img create -f qcow2 /var/www/html/test.img 1G
# local
$ qemu-img check test.img
No errors were found on the image.
# remote
$ qemu-img check http://localhost:80/test.img
** Attachment added: "strace of the hanging qemu-img"
https://bugs.launchpad.net/qemu/+bug/1848556/+attachment/5298128/+files/qemu-img-hangs.strace
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Oh, there's no problem checking the file once it's on the local
filesystem:
$ wget http://10.193.37.117/cloud/bionic-server-cloudimg-amd64.img
--2019-10-17 17:51:33--
http://10.193.37.117/cloud/bionic-server-cloudimg-amd64.img
Connecting to 10.193.37.117:80... connected.
HTTP request sent,
27 matches
Mail list logo
