From: Jan Kiszka <jan.kiszka@siemens.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>
Subject: [Qemu-devel] Re: [Bug 453617] Re: kvm hangs at 100% cpu when connecting to forwarded ports (when listed incorrectly on the command line)
Date: Fri, 21 May 2010 19:29:04 +0200 [thread overview]
Message-ID: <4BF6C2E0.9000000@siemens.com> (raw)
In-Reply-To: <4BF6C14F.30200@msgid.tls.msk.ru>
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
next prev parent reply other threads:[~2010-05-21 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091017002811.3816.18618.malonedeb@gangotri.canonical.com>
2010-05-21 11:55 ` [Qemu-devel] [Bug 453617] Re: kvm hangs at 100% cpu when connecting to forwarded ports (when listed incorrectly on the command line) Launchpad Bug Tracker
2010-05-21 15:42 ` Gleb Natapov
2010-05-21 16:31 ` Michael Tokarev
2010-05-21 17:16 ` [Qemu-devel] " Jan Kiszka
2010-05-21 17:22 ` Michael Tokarev
2010-05-21 17:29 ` Jan Kiszka [this message]
2010-05-21 18:12 ` Gleb Natapov
2010-05-21 17:23 ` Jan Kiszka
2010-05-21 18:07 ` [Qemu-devel] " Gleb Natapov
2010-05-21 19:23 ` Anthony Liguori
2010-05-21 19:29 ` Gleb Natapov
2010-05-21 19:37 ` Gleb Natapov
2010-05-21 19:44 ` Anthony Liguori
2010-05-21 19:48 ` Gleb Natapov
2016-11-07 18:20 ` Thomas Huth
2017-09-13 6:57 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BF6C2E0.9000000@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gleb@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).