
Solarflare
Server
Adapter
User
Guide
SR
‐
IOV
Virtualization
Using
KVM
Issue
20
©
Solarflare
Communications
2017
333
03:00.2
Ethernet
controller:
Solarflare
Communications
Device
1903
(rev
01)
03:00.3
Ethernet
controller:
Solarflare
Communications
Device
1903
(rev
01)
03:00.4
Ethernet
controller:
Solarflare
Communications
Device
1903
(rev
01)
03:00.5
Ethernet
controller:
Solarflare
Communications
Device
1903
(rev
01)
4
To
identify
which
physical
port
a
given
network
interface
is
using:
#
cat
/sys/class/net/eth<N>/device/physical_port
5
To
identify
which
PF
a
given
VF
is
associated
with
use
the
following
command
(in
this
example
there
are
4
VFs
assigned
to
PF
eth4):
#
ip
link
show
19:
eth4:
<NO
‐
CARRIER,BROADCAST,MULTICAST,UP>
mtu
1500
qdisc
mq
state
DOWN
qlen
1000
link/ether
00:0f:53:21:00:61
brd
ff:ff:ff:ff:ff:ff
vf
0
MAC
76:c1:36:0a:be:2b
vf
1
MAC
1e:b8:a8:ea:c7:fb
vf
2
MAC
52:6e:32:3d:50:85
vf
3
MAC
b6:ad:a0:56:39:94
MAC
addresses
beginning
00:0f:53
are
Solarflare
designated
hardware
addresses.
MAC
addresses
assigned
to
VFs
in
the
above
example
output
have
been
randomly
generated
by
the
host.
MAC
addresses
visible
to
the
host
will
be
replaced
by
libvirt
‐
generated
MAC
addresses
in
a
VM.
7.3
KVM
Network
Architectures
This
section
identifies
SR
‐
IOV
and
the
Linux
KVM
virtualization
infrastructure
configurations
to
consume
adapter
port
Physical
Functions
(PF)
and
Virtual
Functions
(VF).
•
•
•
•
•
•
When
migration
is
not
a
consideration,
Solarflare
recommends
the
network
‐
hostdev
configuration
for
highest
throughput
and
lowest
latency
performance
KVM
libvirt
Bridged
The
traditional
method
of
configuring
networking
in
KVM
virtualized
environments
uses
the
para
‐
virtualized
(PV)
driver,
virtio
‐
net
,
in
the
virtual
machine
and
the
standard
Linux
bridge
in
the
host.
The
bridge
emulates
a
layer
2
learning
switch
to
replicate
multicast
and
broadcast
packets
in
software
and
supports
the
transport
of
network
traffic
between
VMs
and
the
physical
port.