qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lonnie Mendez <lmendez19@austin.rr.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu 0.8.2 and RTEMS
Date: Mon, 13 Nov 2006 16:33:14 -0600	[thread overview]
Message-ID: <1163457194.4427.13.camel@vaio> (raw)
In-Reply-To: <db7b3ca90611131406u7b95ab74x2fabf6e87c5e9ce8@mail.gmail.com>

On Mon, 2006-11-13 at 14:06 -0800, Jonathan Kalbfeld wrote:

> qemu -isa -nics 1 -n ~joel/qemu-work/qemu/qemu-kit/tunconfig.sh \
>    -macaddr 00:80:7F:22:61:77 -m 4 -serial stdio -fda
> /home/joel/qemu/grub144
> 
> I have this much of a command line which doesn't cause qemu to
> complain but it doesn't work either:
> 
> qemu -net nic,macaddr=00:80:7F:22:61:77,model=ne2k_isa \
>   -m 4 -fda /home/joel/qemu/grub144

    You need to specify a connection method for the nic.  qemu has vlans
now that organize the internal network.  The default qemu uses with no
-net arguments is -net nic,vlan=0 -net user,vlan=0.  This groups a nic
and a connection method (slirp) on vlan 0.  If you want to use tun/tap
networking specify -net tap instead (along with -net nic,...).  Your old
line might look like the below:

qemu -M isapc -net nic,macaddr=00:80:7F:22:61:77 -net
tap,script=~joel/qemu-work/qemu/qemu-kit/tunconfig.sh -m 4 -serial stdio
-fda /home/joel/qemu/grub144

Although I'm not sure what the old script format looks like - there are
example qemu-ifup scripts about the net.

> The qemu faq mentions using a tunctl program which I don't see.

Please link that page here so it can be reviewed for correctness.

      reply	other threads:[~2006-11-13 22:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4558E8E8.4090408@oarcorp.com>
2006-11-13 22:06 ` [Qemu-devel] qemu 0.8.2 and RTEMS Jonathan Kalbfeld
2006-11-13 22:33   ` Lonnie Mendez [this message]

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=1163457194.4427.13.camel@vaio \
    --to=lmendez19@austin.rr.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 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).