From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=37582 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OFWct-0000RN-Tv
	for qemu-devel@nongnu.org; Fri, 21 May 2010 14:07:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1OFWcs-0003Ch-A3
	for qemu-devel@nongnu.org; Fri, 21 May 2010 14:07:15 -0400
Received: from mx1.redhat.com ([209.132.183.28]:1454)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <gleb@redhat.com>) id 1OFWcs-0003Ca-13
	for qemu-devel@nongnu.org; Fri, 21 May 2010 14:07:14 -0400
Date: Fri, 21 May 2010 21:07:12 +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: <20100521180712.GB12462@redhat.com>
References: <20091017002811.3816.18618.malonedeb@gangotri.canonical.com>
	<20100521115544.17238.22413.launchpad@loganberry.canonical.com>
	<20100521154252.GA12462@redhat.com>
	<4BF6B56D.4060406@msgid.tls.msk.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4BF6B56D.4060406@msgid.tls.msk.ru>
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: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org

On Fri, May 21, 2010 at 08:31:41PM +0400, Michael Tokarev wrote:
> 21.05.2010 19:42, 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?
> 
> Um, this _is_ upstream issue, as far as I can see.
So bug report should be marked as upstream issue and not distro package
bug. Then it will be clear that distro maintainers looked at the bug and
determined it to be upstream issue.

> It exists in qemu-kvm-0.12.4 at least, I just verified.
> 
Then fill bug report against upstream.

> What's wrong with that forwarding?
> 
Do we want every Ubuntu bug report about qemu/qemu-kvm automatically
forwarded to mailing list?

--
			Gleb.