All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Plesner Jacobsen <apj@mutt.dk>
To: kvm@vger.kernel.org
Subject: Re: Trouble understanding net config options
Date: Thu, 16 Jul 2009 01:07:30 +0200	[thread overview]
Message-ID: <20090715230730.GY2455@nerd.dk> (raw)
In-Reply-To: <f02c30210907151554i6904c41fn1ef2a9043d94cd6@mail.gmail.com>

On Wed, Jul 15, 2009 at 05:54:14PM -0500, Michael Jinks wrote:
> 
> Now I want to bring up a VM with two NICs, one attached to tap12
> (bridge 0), the other on tap11 (bridge 1), but I think I've
> misunderstood the versious "-net" options as described in the kvm man
> page.  It *seems* to say that the way to map a specific tap to a
> specific guest NIC is to say, "-net nic" followed by "-net
> tap,name=<name of the tap from the host OS's perspective>", and repeat
> that sequence for each nic to appear within the VM.
> 
> So, here's the full command line I tried, based on that reading:
> 
>   # kvm -m 512M -net nic -net tap,name=tap11 -net nic -net
> tap,name=tap12 -hda /vmstore/wee -vnc :11 -cdrom
> /path/to/my/Windows.iso -boot d

The parameter is "ifname", not "name".

-- 
Andreas

  parent reply	other threads:[~2009-07-15 23:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 22:54 Trouble understanding net config options Michael Jinks
2009-07-15 23:05 ` Stephane Bakhos
2009-07-15 23:08   ` Michael Jinks
2009-07-15 23:12     ` Stephane Bakhos
2009-07-15 23:12   ` Andreas Plesner Jacobsen
2009-07-15 23:17     ` Michael Jinks
2009-07-15 23:24       ` Chris Webb
2009-07-15 23:41         ` Michael Jinks
2009-07-16  0:03           ` Charles Duffy
2009-07-15 23:48     ` Andreas Plesner Jacobsen
2009-07-15 23:07 ` Andreas Plesner Jacobsen [this message]
2009-07-15 23:22   ` Michael Jinks
2009-07-15 23:27     ` Stephane Bakhos
2009-07-15 23:35     ` Andreas Plesner Jacobsen
2009-07-15 23:42       ` Michael Jinks

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=20090715230730.GY2455@nerd.dk \
    --to=apj@mutt.dk \
    --cc=kvm@vger.kernel.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.