1 of 1 people found this helpful
Thanx for posting to our site.
The assignment of a VF that is on a PF which is part of a bond will not cause the error you are explaining. I actually posted a whitepaper just a few months ago about bonding and SR-IOV:
You may find that useful.
Regarding your issue - OVM is of course from Oracle. They have their own version of device drivers (PF). I would make sure you have the latest and greatest PF driver. In addition 5.6 is pretty old - if memory serves there were some kernel updates required for SR-IOV. Please make sure it is as up to date as can be, and get the latest drivers from sourceforge.
Have you tried a newer release lik Redhat 6.2? Just trying to narrow down the number of variables.
No luck ...
The OEL6.2 which has a Unbreakable kernel, does not allow me to see the device now.
It is removed from the list of "assignable devices" when the VM was booted, but cannot see at the VM level.
It seems on my OEL 56 that I can see it only if i boot on a Xen kernel... strange.
That looks to be the latest. I assume you also updated the VM (assuming you tried a newer release of RedHat).
Most likely something with your hypervisor. Unfortunately I don't have any experience with Oracle's VMM and their drivers, while based on ours are owned by them.
Hopefully somebody else in the community has an idea. In the meantime - you might try using Red Hat KVM as the VMM for testing purposes to provide a data point.
Seems if our blog is having issues today. I'll try to re-post my reply.
You have the latest PF (ixgbe) driver. Did you try a different VM with the latest VF(ixgvf) driver?
I've no experience with Oracle's VMM, and they own their version of the rivers. I'd try using a known solution - such as RHEL 6.2 KVM and see if that works in order to add a data point.
Perhaps somebody else in the community has more information as well.
On the same hypervisor, i finally managed to get this pci device visible.
I used a more recent linux distro version which has a more recent kernel (2.6.39). This distro comes with an updated version of the VF driver (2.0).
thanks for your help! I'm halfway there!
Now i am trying to configure the network, and I encounter more issues to use the VF's...
Let me recap my current configuration: 1 server with 1 82599 NIC (2 ports: eth0 and eth1), this server:
- runs the Xen hypervisor (4.1.2) with ixgbe driver
- the NIC mentioned above has 4 VF's per PF, total is 8 VF assignable to my VM
- the 2 PF's: eth0 and eth1 are in a bond group (bond0) in active/standby mode
- the Xen hypervisor has 3 virtual bridges, each one of them on a different VLAN - the VM's can be attached to one or more of these bridges in order to participate in the VLAN traffic
- the virtual bridges use bond0 to "go outside" of the server
- the VM is a PVM with 2.6.39 kernel and 2.x ixgbevf driver, it has 1 PCI device successfully assigned
However, when I configure the link, it's fine, the module gets loaded in the kernel, but the VF doesn't seem to "go out" (ping to the hypervisor on the same subnet doesn't work).
I've read the docs from this website and it seems actually fine to use a VF which PF is part of an active bond, so i'm a bit lost again.
Next step will be to break the bond and remove the virtual switches (that are not used anymore since I use the VF), and assign an IP address on the same subnet as the PF eth0, in order to simplify my network setup. Any other suggestion?