From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=36502 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OFYD6-00086T-BJ
	for qemu-devel@nongnu.org; Fri, 21 May 2010 15:48:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1OFYD4-0007fk-NE
	for qemu-devel@nongnu.org; Fri, 21 May 2010 15:48:44 -0400
Received: from mx1.redhat.com ([209.132.183.28]:12879)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1OFYD4-0007fT-Bs
	for qemu-devel@nongnu.org; Fri, 21 May 2010 15:48:42 -0400
Date: Fri, 21 May 2010 22:48:37 +0300
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [Bug 453617] Re: kvm hangs at 100% cpu when
	connecting to forwarded ports (when listed incorrectly on the command
	line)
Message-ID: <20100521194837.GC27526@redhat.com>
References: <20091017002811.3816.18618.malonedeb@gangotri.canonical.com>
	<20100521115544.17238.22413.launchpad@loganberry.canonical.com>
	<20100521154252.GA12462@redhat.com> <4BF6DDA1.90304@codemonkey.ws>
	<20100521193700.GB27526@redhat.com>
	<4BF6E2AE.6000106@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BF6E2AE.6000106@codemonkey.ws>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Dustin Kirkland <kirkland@canonical.com>

On Fri, May 21, 2010 at 02:44:46PM -0500, Anthony Liguori wrote:
> On 05/21/2010 02:37 PM, Gleb Natapov wrote:
> >Another thing. If my memory serves me right it was promised that message
> >will contain enough info to contact bug reporter without going through
> >launchpad web interface. In other words email of bug reporter will be
> >specified. I can't find it in the message.
> 
> It is when the bug is original filed against the upstream project.
> 
> I think what you're suggesting is that bugs filed against a distro
> (say Ubuntu) should not just be marked as "also affects upstream"
> but rather that a new upstream bug should be filed.  It's still
> possible to connect the two bugs and I think it's not an
> unreasonable suggestion.
> 
Correct, thanks.

--
			Gleb.