From: Anand Kumria <wildfire@progsoc.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: NETDEV WATCHDOG: eth0: transmit timed out
Date: Sat, 08 Jan 2005 21:14:10 +1100 [thread overview]
Message-ID: <pan.2005.01.08.10.14.08.445168@progsoc.org> (raw)
In-Reply-To: 1104980983.29588.66.camel@localhost.localdomain
On Thu, 06 Jan 2005 04:09:43 +0100, Horst Schlonz wrote:
> Am Mittwoch, den 05.01.2005, 20:53 -0500 schrieb Jim C. Brown:
>> On Thu, Jan 06, 2005 at 02:34:02AM +0100, Horst Schlonz wrote:
>> > > Did you try a linux guest where the kernel is configured with
>> > > CONFIG_NE2000? This together with together with "qemu -isa"?
>> > >
>> > >
>> > it's configured as a module. loading ne module fails due to missing
>> > parameters and probably to missing isapnptools.
>> >
>> > well, let's try knoppix...
>> > loadind ne fails (ne.c: You must supply "io=0xNNN" value(s) for ISA
>> > cards).
>> > pnpdump reveals "No board found"
>> > > This together with together with "qemu -isa"?
>>
>> Sounds like you forgot the -isa option. If you put that in, then
>> something inside of qemu is clearly broken.
>>
>>
> i have compiled the latest snapshot of qemu (qemu-snapshot-2005-01-04_23)
> and my dead simple network configuration in my orginal post works now. i
> can ping and i am confident, that the neat stuff (vde) will now work too.
>
> there is probably something wrong with this qemu-package:
Indeed, noted as Debian bugs 283166 and 285752.
bugs.debian.org/package-name (in this case bugs.debian.org/qemu) is often
a good first step to see if anyone else has had the same issue.
Anand
--
linux.conf.au 2005 - http://lca2005.linux.org.au/ - Birthplace of Tux
April 18th to 23rd - http://lca2005.linux.org.au/ - LINUX
Canberra, Australia - http://lca2005.linux.org.au/ - Get bitten!
next prev parent reply other threads:[~2005-01-08 10:22 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
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 ` Anand Kumria [this message]
2005-01-06 2:41 ` 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=pan.2005.01.08.10.14.08.445168@progsoc.org \
--to=wildfire@progsoc.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).