From: Jean-Michel POURE <jm@poure.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Clarification about qemu-fast (was segfaults in fc1)
Date: Thu, 24 Jun 2004 08:36:40 +0200 [thread overview]
Message-ID: <200406240836.41050.jm@poure.com> (raw)
In-Reply-To: <20040623165006.GA22835@jbrown.mylinuxbox.org>
Le mercredi 23 Juin 2004 18:50, Jim C. Brown a écrit :
> That is not exactly true. Qemu works fine for me, even when I start it when
> I am offline. However I use VDE/tuntap and do have a local area network, so
> it is possible that qemu requires a network connection to function
> correctly (IIRC since 0.5.5 qemu uses -user-net by default if it can not
> access tuntap, and -dummy-net by default for earlier versions). Of course
> tuntap requires that you have an actual ethernet card to work....
>
> BTW if you are using the Windows port, you might be better off using
> -dummy-net or -user-net ... I vaguely recall that one of the reasons
> -user-net was introduced was because it was so hard to set up networking
> with qemu when Windows was the host OS.
Can anyone confirm the same problems with -user-net as described here:
https://savannah.nongnu.org/bugs/?func=detailitem&item_id=9388
http://www.poure.com/screenshots/qemu_temp_6.png
A Debian SID guest with user-net seems to loose network packets. On the
contrary, Tun networking works fine. Please note that this is not qemu-fast
but qemu system emulator.
Cheers,
Jean-Michel
next prev parent reply other threads:[~2004-06-24 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 13:03 [Qemu-devel] Clarification about qemu-fast (was segfaults in fc1) Thomas Munn
2004-06-23 12:05 ` David
2004-06-23 16:50 ` Jim C. Brown
2004-06-23 19:22 ` John R. Hogerhuis
2004-06-24 6:36 ` Jean-Michel POURE [this message]
2004-06-24 9:08 ` Christof Petig
2004-06-24 21:48 ` John R. Hogerhuis
2004-06-23 15:12 ` Antony T Curtis
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=200406240836.41050.jm@poure.com \
--to=jm@poure.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.