Thanx for posting to our site.
First let me address the changing of the MTU size. On that particular device, the MTU for the PF and the VF's must be the same. In fact you should be able to change the MTU for the PF, nothing will actually happen when you try and change it on the VF.
Not being able to create > 32 VF's sounds a bit odd. I would update your BIOS.
As for Dom0 communicating with a VF - can you try it without doing any VLAN and bonding in the VM and let me know what you find.
Thanks for your answer, much appreciated.
About the MTU size, it's a problem for me to set dom0 PF's at 9000 because that requires to change all our virtual bridges to 9000 as well, and for some reason the vlaned netfront interface don't work anymore.
Anyways, re focusing on the dom0 not being able to communicate with the local vm, i broke the bond, used a non vlan network, still the exact same issue.
Any other idea?
I kind of solved my issue, but not fully, let me explain.
First, here are the versions i use:
OVS303 with default kernel 18.104.22.168-45xen and latest intel ixgbe drivers (well almost ) 3.12.6 (i created them with rpmbuild).
Guest OS is OEL6.3 kernel 2.6.32-400 with latest ixgbevf drivers 2.7.12
In our architecture we have a bond made of 2 PFs, and each PF has 31 VF. I assign one VF of each PF to my system and recreate the bond. Each PF is connected to different switches.
Anyways, when i look at the supposedly inactive switch, its table contains the mac address of my VF !
I just failed over the port to the active switch and it worked.
I'm wondering if SR-IOV is asking my switch to failover sometimes...
When I look at the dom0, i find these messages: "VF Reset msg received from vf" anytime i bring up the vm.
maybe that's related...
So, i know what's the problem, but i dont know the source of the issue... what is causing the bonding to switch VF...
1 of 1 people found this helpful
Aaah, that piece of information is important
Bonding of PF's has some special considerations that must be taken into account. I suggest you take a look at a paper I wrote last year:
That should shed some light on your challenges.