Hello, I have created a KVM Virtual machine containing a Virtual function from a Emulex NC553 Physical function. I am unable to ping to other machines on the network. I have tried using Fedora 17 and RHEL6.3. On these OS's, "ifconfig eth<X>" on the virtual functions shows there are bytes being transmitted. But the eth<X> is receiving 0 bytes. Dmesg shows be2net driver emitted these messages (in the VM, the be2net device is at 00:09.0) as the ping is going on: On RHEL6.2, I am able to ping successfully to the other machines. be2net 0000:00:09.0: This domain(VM) is not permitted to execute this cmd (opcode 34) be2net 0000:00:09.0: This domain(VM) is not permitted to execute this cmd (opcode 34) be2net 0000:00:09.0: This domain(VM) is not permitted to execute this cmd (opcode 34) be2net 0000:00:09.0: This domain(VM) is not permitted to execute this cmd (opcode 34) be2net 0000:00:09.0: This domain(VM) is not permitted to execute this cmd (opcode 34) Anybody knows how to resolve this problem? Is there a newer be2net driver that fix this problem? Driver version info in RHEL6.3: # modinfo be2net filename: /lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/benet/be2net.ko license: GPL author: ServerEngines Corporation description: ServerEngines BladeEngine 10Gbps NIC Driver 4.1.307r version: 4.1.307r srcversion: 7076CA6C80C3CD968BAFFFC alias: pci:v000010DFd00000720sv*sd*bc*sc*i* alias: pci:v000010DFd0000E228sv*sd*bc*sc*i* alias: pci:v000010DFd0000E220sv*sd*bc*sc*i* alias: pci:v000019A2d00000710sv*sd*bc*sc*i* alias: pci:v000019A2d00000700sv*sd*bc*sc*i* alias: pci:v000019A2d00000221sv*sd*bc*sc*i* alias: pci:v000019A2d00000211sv*sd*bc*sc*i* depends: vermagic: 2.6.32-279.el6.x86_64 SMP mod_unload modversions parm: num_vfs:Number of PCI VFs to initialize (uint) parm: multi_rxq:Obsolete and used only for compatibility (bool) parm: rx_frag_size:Size of a fragment that holds rcvd data. (ushort) The VM is running on a HP BL460 G7 blade. -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
