From: Launchpad Bug Tracker <1272252@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1272252] Re: qemu-img ftp/http convert
Date: Mon, 21 Jun 2021 04:17:37 -0000 [thread overview]
Message-ID: <162424905790.11837.14783540078575755238.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20140124101150.11988.40603.malonedeb@wampee.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1272252
Title:
qemu-img ftp/http convert
Status in QEMU:
Expired
Bug description:
Converting images with ftp or http as source could be done a lot
faster. The way it works now (qemu 1.7.50) is significantly slower
than the optimal way.
FTP - how it works now
1. Connect and login to ftp-server. Ask for size of file.
2. Get a chunk of data using rest+retr
3. Goto step 1 again in a loop until all data is retrieved
FTP - better solution
1. Connect and login to ftp-server. Dont ask for size of file.
2. Retrieve all remaining data
3. Goto step 1 again if disconnected/io error (max NN errors etc)
Http - how it works now
1. Connect to webserver and ask for size of file / http HEAD.
2. Get a chunk of data using http Range.
3. Goto step 1 again in a loop until all data is retrieved.
Http - better solution
1. Connect to webserver.
2. Retrieve all remaining data.
3. Goto step 1 again if disconnected/io error (max NN errors).
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1272252/+subscriptions
prev parent reply other threads:[~2021-06-21 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 10:11 [Qemu-devel] [Bug 1272252] [NEW] qemu-img ftp/http convert Mr J
2016-10-31 12:22 ` [Qemu-devel] [Bug 1272252] " Thomas Huth
2021-04-22 3:58 ` Thomas Huth
2021-06-21 4:17 ` Launchpad Bug Tracker [this message]
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=162424905790.11837.14783540078575755238.malone@loganberry.canonical.com \
--to=1272252@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.