From: "Jim C. Brown" <jbrown106@phreaker.net>
To: Magnus Damm <magnus.damm@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out
Date: Thu, 6 Jan 2005 16:57:14 -0500 [thread overview]
Message-ID: <20050106215714.GA21115@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <aec7e5c305010510253e87d651@mail.gmail.com>
On Wed, Jan 05, 2005 at 07:25:10PM +0100, Magnus Damm wrote:
> Have you tried to use -user-net?
>
> I am successfully using a custom 2.6.9-based distro in QEMU using
> "-nics 1 -user-net -isa", the guest kernel uses the NE2000 driver, the
> host is either a powerpc or a x86 running Linux. PCI is on my todo
> list.
PCI is better in general (tho as far as the NICs go it doesn't make much of a
difference). You shouldn't need to pass the -nics 1 option, as that is the
default.
>
> And I have only used the network to talk with the integrated TFTP server.
Is that the only use of the network that works correctly?
>
> / magnus
>
>
> _______________________________________________
> 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:[~2005-01-06 22:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 4:30 [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out Horst Schlonz
2005-01-05 15:43 ` Jim C. Brown
2005-01-05 15:50 ` Jim C. Brown
2005-01-05 18:12 ` Horst Schlonz
2005-01-05 18:25 ` Magnus Damm
2005-01-06 21:57 ` Jim C. Brown [this message]
2005-01-06 22:47 ` Magnus Damm
2005-01-05 19:50 ` Jim C. Brown
2005-01-05 20:06 ` Horst Schlonz
2005-01-05 21:33 ` Jim C. Brown
2005-01-06 0:27 ` Horst Schlonz
2005-01-06 0:58 ` Magnus Damm
2005-01-06 1:34 ` Horst Schlonz
2005-01-06 1:53 ` Jim C. Brown
2005-01-06 3:09 ` Horst Schlonz
2005-01-08 10:14 ` [Qemu-devel] " Anand Kumria
2005-01-06 2:41 ` [Qemu-devel] " Herbert Poetzl
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=20050106215714.GA21115@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--cc=magnus.damm@gmail.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.