From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52480 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OFW22-0006Sy-FM for qemu-devel@nongnu.org; Fri, 21 May 2010 13:29:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OFW20-00061i-62 for qemu-devel@nongnu.org; Fri, 21 May 2010 13:29:10 -0400 Received: from thoth.sbs.de ([192.35.17.2]:15211) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OFW1z-00061P-S7 for qemu-devel@nongnu.org; Fri, 21 May 2010 13:29:08 -0400 Message-ID: <4BF6C2E0.9000000@siemens.com> Date: Fri, 21 May 2010 19:29:04 +0200 From: Jan Kiszka 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> <4BF6C14F.30200@msgid.tls.msk.ru> In-Reply-To: <4BF6C14F.30200@msgid.tls.msk.ru> Content-Type: text/plain; charset=ISO-8859-1 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: Michael Tokarev Cc: "qemu-devel@nongnu.org" , Gleb Natapov Michael Tokarev wrote: > 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 :) So, in the presence of -netdev, we may have to deemphasize on -net which is now actually an expert knob. Doc updates welcome where required. > >>> 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. If there are too much operator errors, that may actually point to some usability and/or documentation issue. > > But actually I were asking about this particular bugreport, > not about general forwarding - which - at least - should be > done with care :) Right. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux