qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
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 21:12:54 +0300	[thread overview]
Message-ID: <20100521181254.GC12462@redhat.com> (raw)
In-Reply-To: <4BF6C14F.30200@msgid.tls.msk.ru>

On Fri, May 21, 2010 at 09:22:23PM +0400, Michael Tokarev wrote:
> But actually I were asking about this particular bugreport,
> not about general forwarding - which - at least - should be
> done with care :)
> 
Ugh, I am talking about general forwarding not this particular bug
report :) Although it was not clear to me from the message that distro
maintainers actually looked at the report and verified it against
upstream.

--
			Gleb.

  parent reply	other threads:[~2010-05-21 18:13 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 [this message]
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=20100521181254.GC12462@redhat.com \
    --to=gleb@redhat.com \
    --cc=jan.kiszka@siemens.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).