From: Max Reitz <1888467@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1888467] Re: qemu-img http convert bug
Date: Mon, 27 Jul 2020 14:11:32 -0000 [thread overview]
Message-ID: <159585909218.29426.3265733007008207026.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 159540494097.10238.3390638369680947345.malonedeb@gac.canonical.com
OK, that’s interesting. To be honest, I have no idea. I’ll keep this in
mind and I’ll try to play around with it, but I can’t promise anything.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1888467
Title:
qemu-img http convert bug
Status in QEMU:
New
Bug description:
Hello, Why the file sizes of http conversion and local conversion are
inconsistent?
Use the http method of qemu-img for conversion. The size of some formats after conversion is different from the local method of qemu-img. Such as vhd, vdi. qcow2 and vmdk are normal。
My image size is 40 G, raw format.
The source is the same file, but the access method is different
http method of qemu-img: qemu-img convert -f raw -O vdi http://xxx xxx.vdi(19G,after conversion)
local method of qemu-img: qemu-img convert -f raw -O vdi xxx.raw xxx.vdi(3G,after conversion)
thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1888467/+subscriptions
next prev parent reply other threads:[~2020-07-27 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 8:02 [Bug 1888467] [NEW] qemu-img http convert bug dunfeng zhang
2020-07-22 8:38 ` [Bug 1888467] " Max Reitz
2020-07-22 9:07 ` dunfeng zhang
2020-07-27 14:11 ` Max Reitz [this message]
2020-07-28 8:18 ` dunfeng zhang
2020-07-28 14:16 ` Max Reitz
2021-05-07 4:39 ` Thomas Huth
2021-07-07 4:17 ` Launchpad Bug Tracker
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=159585909218.29426.3265733007008207026.malone@chaenomeles.canonical.com \
--to=1888467@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).