From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51977) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQY0K-0005mP-17 for qemu-devel@nongnu.org; Thu, 20 Mar 2014 04:07:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WQY09-0006X9-RH for qemu-devel@nongnu.org; Thu, 20 Mar 2014 04:07:07 -0400 Received: from mail-wg0-x230.google.com ([2a00:1450:400c:c00::230]:56555) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQY09-0006Wz-JJ for qemu-devel@nongnu.org; Thu, 20 Mar 2014 04:06:57 -0400 Received: by mail-wg0-f48.google.com with SMTP id l18so299770wgh.31 for ; Thu, 20 Mar 2014 01:06:56 -0700 (PDT) Date: Thu, 20 Mar 2014 09:06:54 +0100 From: Stefan Hajnoczi Message-ID: <20140320080654.GC28673@stefanha-thinkpad.redhat.com> References: <52FDE495.4050004@ac.upc.edu> <52FDF6F0.4090405@redhat.com> <20140224151654.GB23185@stefanha-thinkpad.hitronhub.home> <392369891.8578031.1393280788249.JavaMail.zimbra@redhat.com> <531067ED.7000404@ac.upc.edu> <53106857.8090601@redhat.com> <531F442E.8040302@ac.upc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <531F442E.8040302@ac.upc.edu> Subject: Re: [Qemu-devel] [libvirt-users] Adjust disk image migration (NBD) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Joaquim Barrera Cc: Fam Zheng , Michal Privoznik , Jeff Cody , qemu-devel , Libvirt Users , Paolo Bonzini On Tue, Mar 11, 2014 at 06:13:18PM +0100, Joaquim Barrera wrote: > 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? Hi Jaoquim, Thanks for reporting this. We're in the bug-fixing phase of the QEMU 2.0 release cycle so your reminder is perfect timing. I'll take a look at this issue today. Stefan