From: Joaquim Barrera <jbarrera@ac.upc.edu>
To: Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: Libvirt Users <libvirt-users@redhat.com>,
Michal Privoznik <mprivozn@redhat.com>,
Jeff Cody <jcody@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [libvirt-users] Adjust disk image migration (NBD)
Date: Tue, 11 Mar 2014 18:13:18 +0100 [thread overview]
Message-ID: <531F442E.8040302@ac.upc.edu> (raw)
In-Reply-To: <53106857.8090601@redhat.com>
On 28/02/14 11:43, Paolo Bonzini wrote:
> Il 28/02/2014 11:41, Joaquim Barrera ha scritto:
>>>
>>
>> Thanks for the answer. Something is still not clear to me. Are we in
>> front of a bug (that means, something that could be fixed) or is this
>> behaviour somehow expected for some reason? More and more tests I am
>> doing, I get allways the same throughput chart: unlimited bandwidth when
>> syncronizing the disk, and smooth bandwidth limit when migrating RAM.
>>
>> Joaquim
>
> Yes, it's a bug that we can fix.
>
Hi Paolo et all. Can you tell me how to "start" the process of bug
fixing? Am I supposed to report it somewhere, or did you just take note?
Thanks a lot.
> Paolo
>
>
next prev parent reply other threads:[~2014-03-11 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52FDE495.4050004@ac.upc.edu>
2014-02-14 10:58 ` [Qemu-devel] [libvirt-users] Adjust disk image migration (NBD) Michal Privoznik
2014-02-24 15:16 ` Stefan Hajnoczi
2014-02-24 22:26 ` Paolo Bonzini
2014-02-28 10:41 ` Joaquim Barrera
2014-02-28 10:43 ` Paolo Bonzini
2014-03-11 17:13 ` Joaquim Barrera [this message]
2014-03-20 8:06 ` Stefan Hajnoczi
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=531F442E.8040302@ac.upc.edu \
--to=jbarrera@ac.upc.edu \
--cc=jcody@redhat.com \
--cc=libvirt-users@redhat.com \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).