qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: stappers@stappers.nl (Geert Stappers)
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: linux-test-0.5.1.tar.gz seems outdated, but isn't
Date: Sat, 17 Jun 2006 08:17:42 +0200	[thread overview]
Message-ID: <20060617061742.GP29071@gpm.stappers.nl> (raw)
In-Reply-To: <20060616183705.GO29071@gpm.stappers.nl>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

On Fri, Jun 16, 2006 at 08:37:05PM +0200, Geert Stappers wrote:
   <snip/>
> 19:42 < stappers> pbrook: are you sure about
> 19:42 < stappers> < pbrook> Oh. That doesn't have the right ethernet drivers
>                   on it.
> 19:43 < pbrook> Fairly sure. It only has the isa ne2k drivers.
> 19:43 < stappers> the kernel config has CONFIG_NE2000 and qemu monitor reports
>                   ne2000 at `info network`
> 19:44 < pbrook> See above.
> 19:44 < pbrook> ne != ne2k_pci
> 19:44 < stappers> mmm
> 
> While editing, I wondered which "hardware" is in the Debian version of Qemu.
> 
>   CHIPS
That was a brainwave

20:45 < stappers> when I modify ` qemu linux.img -net nic -net tap`
20:46 < stappers> into `qemu linux.img -net nic,model=ne2k_isa -net tap` is
                  the error 'no such device' gone  :-)

So the trick is defining the NIC model as "ne2k_isa"

Should this default hardware detection be documented?


Cheers
Geert Stappers

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-06-17  6:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 18:37 [Qemu-devel] linux-test-0.5.1.tar.gz seems outdated Geert Stappers
2006-06-17  6:17 ` Geert Stappers [this message]
2006-06-17 16:05   ` [Qemu-devel] Re: linux-test-0.5.1.tar.gz seems outdated, but isn't Alex
2006-06-17 16:24   ` Alex

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=20060617061742.GP29071@gpm.stappers.nl \
    --to=stappers@stappers.nl \
    --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).