From: Gleb Natapov <gleb@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [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 21:07:12 +0300 [thread overview]
Message-ID: <20100521180712.GB12462@redhat.com> (raw)
In-Reply-To: <4BF6B56D.4060406@msgid.tls.msk.ru>
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.
next prev parent reply other threads:[~2010-05-21 18:07 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
2010-05-21 18:12 ` Gleb Natapov
2010-05-21 17:23 ` Jan Kiszka
2010-05-21 18:07 ` Gleb Natapov [this message]
2010-05-21 19:23 ` [Qemu-devel] " 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=20100521180712.GB12462@redhat.com \
--to=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).