From: Avi Kivity <avi@redhat.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: Sasha Levin <levinsasha928@gmail.com>, kvm@vger.kernel.org
Subject: Re: SR-IOV and KVM?
Date: Mon, 27 Jun 2011 17:40:53 +0300 [thread overview]
Message-ID: <4E089675.5050903@redhat.com> (raw)
In-Reply-To: <4E089069.7080507@genband.com>
On 06/27/2011 05:15 PM, Chris Friesen wrote:
>
> Maybe it's just a documentation thing. I'm just getting into KVM and
> trying to figure everything out, and I don't see a step-by-step guide
> to configuring a host/guest system with either SR-IOV or Intel's VMDq.
You can use virt-manager; it has a GUI for that. Once you're
comfortable with it you can drop down to virsh command line and from
there to raw qemu command line / monitor.
>
> For SR-IOV I assume I need to configure the PF in the host, enable
> some number of VFs, pass through a VF to each guest and load the vf
> driver. Is that right?
I think all that is needed is to prevent the host from binding to the
guest - not sure.
> Do I need to configure a software bridge to allow the guests to talk
> to each other?
S/R-IOV networking is beyond my knowledge - I think it depends on your
switch, sometimes it will loop back packets to other guests, other times
the NIC itself will do that. It may just work, so try it out.
> I assume the passthrough require VT-d support in the hardware and host
> kernel--is that correct?
>
Yes. Recent kernels have that.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-06-27 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 21:10 SR-IOV and KVM? Chris Friesen
2011-06-25 1:09 ` lidong chen
2011-06-25 1:13 ` Sasha Levin
2011-06-27 14:15 ` Chris Friesen
2011-06-27 14:40 ` Avi Kivity [this message]
2011-06-27 15:15 ` David Ahern
2011-06-27 15:34 ` Steve Dobbelstein
2011-06-25 8:53 ` Troels Arvin
2011-06-27 4:23 ` David Ahern
2011-06-27 8:18 ` Troels Arvin
2011-06-27 14:59 ` David Ahern
2011-06-28 20:09 ` Troels Arvin
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=4E089675.5050903@redhat.com \
--to=avi@redhat.com \
--cc=chris.friesen@genband.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
/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