From: Rod Smith <rod.smith@canonical.com>
To: qemu-devel@nongnu.org
Subject: [Bug 1848556] Re: qemu-img check failing on remote image in Eoan
Date: Thu, 17 Oct 2019 17:51:03 -0000 [thread overview]
Message-ID: <157133466395.18858.7818065006022596425.malone@gac.canonical.com> (raw)
In-Reply-To: 157133449178.19203.719001918774596241.malonedeb@gac.canonical.com
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, awaiting response... 200 OK
Length: 344195072 (328M)
Saving to: ‘bionic-server-cloudimg-amd64.img’
bionic-server-cloud 100%[===================>] 328.25M 105MB/s in
3.1s
2019-10-17 17:51:37 (105 MB/s) - ‘bionic-server-cloudimg-amd64.img’
saved [344195072/344195072]
$ qemu-img check bionic-server-cloudimg-amd64.img
No errors were found on the image.
16651/36032 = 46.21% allocated, 98.92% fragmented, 98.49% compressed clusters
Image end offset: 344195072
--
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 QEMU:
New
Bug description:
The "qemu-img check" function is failing on remote (HTTP-hosted)
images, beginning with Ubuntu 19.10 (qemu-utils version 1:4.0+dfsg-
0ubuntu9). With previous versions, through Ubuntu 19.04/qemu-utils
version 1:3.1+dfsg-2ubuntu3.5, the following worked:
$ /usr/bin/qemu-img check http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img
No errors were found on the image.
19778/36032 = 54.89% allocated, 90.34% fragmented, 89.90% compressed clusters
Image end offset: 514064384
The 10.193.37.117 server holds an Apache server that hosts the cloud
images on a LAN. Beginning with Ubuntu 19.10/qemu-utils 1:4.0+dfsg-
0ubuntu9, the same command never returns. (I've left it for up to an
hour with no change.) I'm able to wget the image from the same server
and installation on which qemu-img check fails. I've tried several
.img files on the server, ranging from Bionic to Eoan, with the same
results with all of them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1848556/+subscriptions
next prev parent reply other threads:[~2019-10-17 20:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 17:48 [Bug 1848556] [NEW] qemu-img check failing on remote image in Eoan Rod Smith
2019-10-17 17:51 ` Rod Smith [this message]
2019-10-18 7:09 ` [Bug 1848556] " Christian Ehrhardt
2019-10-18 7:11 ` Christian Ehrhardt
2019-10-18 7:24 ` Christian Ehrhardt
2019-10-18 7:39 ` Christian Ehrhardt
2019-10-18 8:31 ` Christian Ehrhardt
2019-10-18 8:47 ` Max Reitz
2019-10-18 18:14 ` Rod Smith
2019-10-21 8:57 ` Christian Ehrhardt
2019-10-21 9:23 ` Max Reitz
2019-10-21 9:27 ` Max Reitz
2019-10-21 12:49 ` Christian Ehrhardt
2019-10-21 14:17 ` Christian Ehrhardt
2019-10-21 14:24 ` Christian Ehrhardt
2019-10-21 15:15 ` Launchpad Bug Tracker
2019-10-22 21:12 ` Rod Smith
2019-10-28 6:32 ` Launchpad Bug Tracker
2019-10-28 6:38 ` Launchpad Bug Tracker
2019-10-28 6:40 ` Christian Ehrhardt
2019-10-28 6:52 ` Christian Ehrhardt
2019-10-28 15:23 ` Christian Ehrhardt
2019-11-07 9:54 ` Launchpad Bug Tracker
2019-11-07 10:56 ` Christian Ehrhardt
2019-11-21 15:31 ` Christian Ehrhardt
2019-11-22 9:54 ` Timo Aaltonen
2019-11-22 14:56 ` [Bug 1848556] Autopkgtest regression report (qemu/1:4.0+dfsg-0ubuntu9.2) Ubuntu SRU Bot
2019-11-25 11:55 ` [Bug 1848556] Re: qemu-img check failing on remote image in Eoan Christian Ehrhardt
2019-12-02 11:02 ` Launchpad Bug Tracker
2019-12-02 11:02 ` [Bug 1848556] Update Released Łukasz Zemczak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=157133466395.18858.7818065006022596425.malone@gac.canonical.com \
--to=rod.smith@canonical.com \
--cc=1848556@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.