From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=39687 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OFXui-0003ij-6U
	for qemu-devel@nongnu.org; Fri, 21 May 2010 15:29:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1OFXug-0005fA-MW
	for qemu-devel@nongnu.org; Fri, 21 May 2010 15:29:44 -0400
Received: from mx1.redhat.com ([209.132.183.28]:18543)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1OFXug-0005f1-Ew
	for qemu-devel@nongnu.org; Fri, 21 May 2010 15:29:42 -0400
Date: Fri, 21 May 2010 22:29:35 +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: <20100521192935.GA27526@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BF6DDA1.90304@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:23:13PM -0500, Anthony Liguori wrote:
> On 05/21/2010 10:42 AM, Gleb Natapov wrote:
> >>ProblemType: Bug
> >>Architecture: amd64
> >>Date: Fri Oct 16 17:19:59 2009
> >>DistroRelease: Ubuntu 9.10
> >What is the point forwarding distro bugs here? Can we have upstream bug
> >tracker to report upstream issues?
> 
> These bugs are being explicitly reported against upstream.
How should we know it from the message?

> Launchpad can also track status against distros bugs (Fedora,
> Debian, Gentoo, Ubuntu, etc.).
> 
Great, here we only care about upstream.

> It can be annoying is if a very Ubuntu (or other distribution)
> specific bug report is marked also affects upstream without a clear
> indication that this was in fact explicitly tested against upstream
> (and what specific version was tested).  This is something that we
> can fix though by just making protocol clear for this type of thing.
> 
New bug should be opened against upstream. Then it will be crystal
clear that somebody took the time to check against upstream.

--
			Gleb.