Skip to main content

Setting up SR-IOV in RHEL6 on PowerEdge servers

Dell Community: "RHEL 6 provides SR-IOV functionality on supported hardware which provides near native performance for virtualized guests.

Single-Root I/O Virtualization (SR-IOV) specification, introduced by PCI-SIG details how a single PCIe device can be shared between various virtualization guests. Devices capable of SR-IOV functionality support multiple virtual functions on top of the physical function. Virtual Function is enabled in hardware as a light weight PCIe function. Operating System cannot discover this function as it does not respond to the PCI bus scan and requires support in the host’s driver. As in PCIe pass-through, a Virtual function of a SR-IOV capable card can be directly assigned to the guest operating system. A virtual function driver running in the guest manages this device."
Labels:

Comments

Brian Johnson said…
If you want more information on SR-IOV check out Patrick Kutch's training video. Patrick and I work in the LAN Access Division at Intel and focus on I/O Virtualization technologies. We work with Red Hat and Dell to enable SR-IOV support. Check out the Intel(R) 82599 10Gb and 82576 1Gb Ethernet Controllers, both have SR-IOV support and drivers available in RHEL6.

http://www.youtube.com/watch?v=hRHsk8Nycdg

Brian Johnson
Intel Corp
November 23, 2010 at 8:10:00 PM GMT+1
Brian Johnson said…
Here is how to setup SR-IOV on 5.4.

http://communities.intel.com/community/wired/blog/2010/03/01/setting-up-red-hat-54-xen-for-sr-iov-using-the-intel-82576-gbe

We will look at updating for RHEL6.

Brian
November 23, 2010 at 8:15:00 PM GMT+1
Dreams said…
Ah schuks...
My servers are old:
#lspci | grep Eth
[...]
0c:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)

07:00.0 Ethernet controller: Intel Corporation 82575GB Gigabit Network Connection (rev 02)
November 24, 2010 at 9:14:00 AM GMT+1
Post a Comment

Popular posts from this blog

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.
1 comment
Read more

Tuning the nscd name cache daemon

I've been playing a bit with the nscd now and want to share some tips related to tuning the nscd.conf file. To see how the DNS cache is doing, use nscd -g. nscd configuration: 0 server debug level 26m 57s server runtime 5 current number of threads 32 maximum number of threads 0 number of times clients had to wait yes paranoia mode enabled 3600 restart internal passwd cache: no cache is enabled [other zero output removed] group cache: no cache is enabled [other zero output removed] hosts cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size 216064 total data pool size 1144 used data pool size 3600 seconds time to live for positive entries 20 seconds time to live for negative entries 66254 cache hi...
2 comments
Read more

Dell Linux - OMSA Hardware Monitoring

Just getting started using Dell's OpenManage Server Administrator (OMSA) on our Oracle Linux platform. There are some confusing instructions going around so it's not immediately clear what to do, hence my blogging here. :) There is a site on Dell - Hardware Monitoring , as well as a wiki with instruction on how to setup their OMSA tooling using yum or up2date. [update]My first update for their instructions: be sure your server has Internet access, as most servers will use a proxy or so. use export http_proxy=http://yourproxy.example.com:port to configure it just for the session, and setup up2date to use an HTTP proxy by editing the settings in /etc/sysconfig/rhn/up2date .
2 comments
Read more