qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org, Brian Thomason <brian.thomason@canonical.com>
Subject: Re: [Qemu-devel] [PATCH] better describe -net options
Date: Wed, 17 Mar 2010 11:40:30 -0500	[thread overview]
Message-ID: <4BA105FE.10503@codemonkey.ws> (raw)
In-Reply-To: <20100317161316.GA19158@shareable.org>

On 03/17/2010 11:13 AM, Jamie Lokier wrote:
> Anthony Liguori wrote:
>    
>>     On 03/05/2010 03:07 PM, Brian Thomason wrote:
>>
>>       The manpage reflects that multiple -net user calls may be made,
>>       but if this is done, it can cause the program to hang. Instead,
>>       multiple -net calls can be combined into one, and this patch adds
>>       that information to qemu-options.hx. Also, -net user may only
>>       be used in conjunction with -net nic.  This is already implcitly
>>       stated, but this patch makes that statement more explicit.
>>
>>     Actually, the problem is that the user created a loop.  It's actually
>>     valid to have something like:
>>     -net user -net dump,file=foo.pcap -net nic
>>     But having -net user -net user creates a loop.
>>      
> When I used -net user -net user, it didn't hang: QEMU crashed with a
> stack overflow.
>
> It crashed after a doing a successful full OS install, because
> everything was fine until the first network packet.
>
> That's not nice, even if it is user error.
>    

Well we should dedicate this case in the code and throw an error.

Regards,

Anthony Liguori

> -- Jamie
>    

      reply	other threads:[~2010-03-17 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 21:07 [Qemu-devel] [PATCH] better describe -net options Brian Thomason
2010-03-17 15:32 ` Anthony Liguori
2010-03-17 16:13   ` Jamie Lokier
2010-03-17 16:40     ` Anthony Liguori [this message]

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=4BA105FE.10503@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=brian.thomason@canonical.com \
    --cc=jamie@shareable.org \
    --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).