From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=42177 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OFVvb-0002Bl-2D for qemu-devel@nongnu.org; Fri, 21 May 2010 13:22:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OFVvZ-00059O-6Z for qemu-devel@nongnu.org; Fri, 21 May 2010 13:22:30 -0400 Received: from isrv.corpit.ru ([81.13.33.159]:38342) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OFVvV-00058o-Qf for qemu-devel@nongnu.org; Fri, 21 May 2010 13:22:29 -0400 Message-ID: <4BF6C14F.30200@msgid.tls.msk.ru> Date: Fri, 21 May 2010 21:22:23 +0400 From: Michael Tokarev MIME-Version: 1.0 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> <4BF6BFE9.2030300@siemens.com> In-Reply-To: <4BF6BFE9.2030300@siemens.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [Bug 453617] Re: kvm hangs at 100% cpu when connecting to forwarded ports (when listed incorrectly on the command line) List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: qemu-devel@nongnu.org, Gleb Natapov 21.05.2010 21:16, Jan Kiszka wrote: > 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. >> It exists in qemu-kvm-0.12.4 at least, I just verified. > > Well, this particular bug rather looks like a potential documentation > insufficiency: > > Instantiating two user space networking stacks on the _same_ vlan with > _identical_ parameters is just asking for troubles. If the reporter read > the manual and then did the mistake, we may have to clarify the docs > what "-net user" does. Actually it's solved like that in ubuntu, by updating documentation. It's a common trap - two pairs of -net nic -net tap without specifying vlan=NN and voila, you have a loop on your network. This has been tried/trapped on more than once, that's for sure :) >> What's wrong with that forwarding? > > IMHO so far nothing - as long as the ratio of pure downstream issues > remains low. I think we should give this channel a chance as it can be > advantageous to have more "real" end-user reports. There's very few distro-specific bugreports usually. At least on Debian. Two observations: I forward or notify about bugs filed against Debian package (I maintain qemu-kvm there) anyway, and quite some bugs filed actually are either usage/operator errors or sort of misunderstanding or misuse, not real bugs. But actually I were asking about this particular bugreport, not about general forwarding - which - at least - should be done with care :) Thanks! /mjt