public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Will Trives <will@trivescon.com.au>
Cc: kvm-devel@lists.sourceforge.net, Dor Laor <dor.laor@gmail.com>
Subject: Re: Virtio with multiple devices of the same type
Date: Wed, 13 Feb 2008 09:24:56 +0200	[thread overview]
Message-ID: <47B29B48.1070901@qumranet.com> (raw)
In-Reply-To: <1202873568.3319.280.camel@athas>

Will Trives wrote:
> Hello guys,
>
> Bug: A virtual machine/guest can only have one virtio block device and
> one virtio network device.
>
> Example command line: 
>
> qemu-system-x86_64 -drive file=disk.qcow2,if=virtio,boot=on -net nic,model=virtio,macaddr=50:18:99:55:4E:43 -net tap -net nic,model=virtio,macaddr=51:17:99:55:4D:43 -net tap 
>   

You need to place the two nics on separate qemu vlans:

qemu-system-x86_64 -drive file=disk.qcow2,if=virtio,boot=on -net nic,model=virtio,macaddr=50:18:99:55:4E:43.vlan=0 -net tap,vlan=0 -net nic,model=virtio,macaddr=51:17:99:55:4D:43,vlan=1 -net tap,vlan=1

(a qemu vlan is just a virtual ethernet segment, not 802.3q (or whatever it's called) vlan)). 


Ideally it should work without this, but there's a bug in one of the 
virtio optimizations that prevents it from working correctly.

-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      parent reply	other threads:[~2008-02-13  7:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  3:32 Virtio with multiple devices of the same type Will Trives
2008-02-13  5:17 ` Anthony Liguori
2008-02-13  7:24 ` Avi Kivity [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=47B29B48.1070901@qumranet.com \
    --to=avi@qumranet.com \
    --cc=dor.laor@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=will@trivescon.com.au \
    /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