From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] eth0 problems
Date: Sat, 28 Aug 2004 20:33:35 -0400 [thread overview]
Message-ID: <20040829003335.GA15499@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200408281918.38859.menola@sbcglobal.net>
On Sat, Aug 28, 2004 at 07:18:38PM -0500, Joe Menola wrote:
> On Sat August 28 2004 6:04 pm, Lonnie Cumberland wrote:
> > No, the /etc/qemu-ifup does not exist and my host eth0 is there but the
> > guest linux.img eth0 does not show. Only the "lo" loopback.
>
> -user-net doesn't provide eth0 in your qemu host. It provides internet access
> only. To get full networking (eth0) you need to setup a tun device.
>
> -jm
>
>
Technically, tun doesn't provide eth0 for the host either. In fact, the
kernel documentation says you need to have eth0 first, or else you cant use
tuntap (that may no longer be true though, remember this is from the offical
kernel docs :). tuntap provides a tun0/tap0 device in the host and an eth0
device in the guest. user net should provide an eth0 as well, but it won't
add anything to the host.
If eth0 doesn't show, that may be due to lack of hardware support. Be sure
your kernel has support for the ne2k-pci module.
user net isn't just for internet access .. the guest can still access the LAN
or the WAN/intranet .. they just can't initiate a talk to it.
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2004-08-29 0:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 21:54 [Qemu-devel] eth0 problems Lonnie Cumberland
2004-08-28 23:13 ` Joe Menola
2004-08-28 23:04 ` Lonnie Cumberland
2004-08-29 0:18 ` Joe Menola
2004-08-29 0:33 ` Jim C. Brown [this message]
2004-08-29 0:43 ` Joe Menola
2004-08-29 1:03 ` Jim C. Brown
2004-08-29 0:55 ` Lonnie Cumberland
2004-08-29 1:54 ` Mark Williamson
2004-08-29 2:53 ` Joe Menola
2004-08-29 2:33 ` Lonnie Cumberland
2004-08-29 5:39 ` Joe Menola
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=20040829003335.GA15499@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--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).