[opensuse] Can't use SR-IOV on openSUSE 13.2
![](https://seccdn.libravatar.org/avatar/9e225f8a99b75427e9df150ef65bd92d.jpg?s=120&d=mm&r=g)
Hi All I have been using SLES11SP3 server, openSUSE 13.1 and 13.2 server. There 3 server have VT-d function and Intel 82576 or Intel I350T2 NIC. Today I tried to set up SR-IOV on openSUSE 13.2. The steps are below: 1. Add kernel option "intel_iommu=on pci=asign-busses" on boot loader with yast. 2. create the file /etc/modprobe.d/50-igb.conf. The content is below. options igb max_vfs=7 options loop max_loop=128 blacklist igbvf 3. create the file /etc/modules-load.d/igb.conf. The content is below. igb 4. Reboot. 5. check the lspci | grep "Ethe" and the output is below 01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 02:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.6 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.7 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 04:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10) So I added this vif "02:10:0" to Virtual machine, that OS is sles12. And start this vm. But the error is displayed below. error: Failed to start domain sles12 error: internal error: process exited while connecting to monitor: 2014-12-13T13:08:34.908734Z qemu-system-x86_64: -device vfio-pci,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x3: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver. 2014-12-13T13:08:34.908766Z qemu-system-x86_64: -device vfio-pci,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x3: vfio: failed to get group 1 2014-12-13T13:08:34.908781Z qemu-system-x86_64: -device vfio-pci,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x3: Device initialization failed. 2014-12-13T13:08:34.908796Z qemu-system-x86_64: -device vfio-pci,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x3: Device 'vfio-pci' could not be initialized So I changed the file /etc/libvirt/qemu.conf for the 3 parameter below: user=root group=rootclear_emulator_capabilities = 0 But nothing changed. But for SLES11SP3 and openSUSE 13.1 I can use SR-IOV for VM. So could you tell me the workaround for this problem? Cheers. Ryo-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
В Sat, 13 Dec 2014 22:27:23 +0900
Ryo Murakawa
Hi All
I have been using SLES11SP3 server, openSUSE 13.1 and 13.2 server. There 3 server have VT-d function and Intel 82576 or Intel I350T2 NIC.
Are server identical?
Today I tried to set up SR-IOV on openSUSE 13.2. The steps are below: 1. Add kernel option "intel_iommu=on pci=asign-busses" on boot loader with yast. 2. create the file /etc/modprobe.d/50-igb.conf. The content is below. options igb max_vfs=7 options loop max_loop=128 blacklist igbvf 3. create the file /etc/modules-load.d/igb.conf. The content is below. igb 4. Reboot. 5. check the lspci | grep "Ethe" and the output is below 01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 02:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.6 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.7 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 04:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)
So I added this vif "02:10:0" to Virtual machine, that OS is sles12. And start this vm.
Are you sure this is the correct vif name?
But the error is displayed below. error: Failed to start domain sles12 error: internal error: process exited while connecting to monitor: 2014-12-13T13:08:34.908734Z qemu-system-x86_64: -device vfio-pci,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x3: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver.
First you say 02:10.0 and here it complains about 02:10.1.
2014-12-13T13:08:34.908766Z qemu-system-x86_64: -device vfio-pci,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x3: vfio: failed to get group 1 2014-12-13T13:08:34.908781Z qemu-system-x86_64: -device vfio-pci,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x3: Device initialization failed. 2014-12-13T13:08:34.908796Z qemu-system-x86_64: -device vfio-pci,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x3: Device 'vfio-pci' could not be initialized
So I changed the file /etc/libvirt/qemu.conf for the 3 parameter below: user=root group=rootclear_emulator_capabilities = 0
But nothing changed. But for SLES11SP3 and openSUSE 13.1 I can use SR-IOV for VM. So could you tell me the workaround for this problem?
It is not clear whether you speak about the same physical host where you tried several versions or you speak about several different hosts. In the latter case hosts may well have different IO topology; you will need to follow what it says: "please ensure all devices within the iommu_group are bound to their vfio bus driver". See Documentation/vfio.txt in kernel source tree for description how to check IOMMU group assignment and to change driver bound to device. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/9e225f8a99b75427e9df150ef65bd92d.jpg?s=120&d=mm&r=g)
Hi
2014/12/14 1:51、Andrei Borzenkov
のメール: В Sat, 13 Dec 2014 22:27:23 +0900 Ryo Murakawa
пишет: Hi All
I have been using SLES11SP3 server, openSUSE 13.1 and 13.2 server. There 3 server have VT-d function and Intel 82576 or Intel I350T2 NIC.
Are server identical? Yes, Before openSUSE 13.2 I had used openSUSE 13.1 on this server and could use SR-IOV for VM on this server.
Today I tried to set up SR-IOV on openSUSE 13.2. The steps are below: 1. Add kernel option "intel_iommu=on pci=asign-busses" on boot loader with yast. 2. create the file /etc/modprobe.d/50-igb.conf. The content is below. options igb max_vfs=7 options loop max_loop=128 blacklist igbvf 3. create the file /etc/modules-load.d/igb.conf. The content is below. igb 4. Reboot. 5. check the lspci | grep "Ethe" and the output is below 01:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 01:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 02:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.6 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:10.7 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.4 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 02:11.5 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 04:00.0 Ethernet controller: Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10)
So I added this vif "02:10:0" to Virtual machine, that OS is sles12. And start this vm.
Are you sure this is the correct vif name? Yes, this vif name is correct.
But the error is displayed below. error: Failed to start domain sles12 error: internal error: process exited while connecting to monitor: 2014-12-13T13:08:34.908734Z qemu-system-x86_64: -device vfio-pci,host=02:10.1,id=hostdev0,bus=pci.0,addr=0x3: vfio: error, group 1 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver.
First you say 02:10.0 and here it complains about 02:10.1. Sorry, this is my mitake.
I can't find the workaround for this problem. Regards. Ryo
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andrei Borzenkov
-
Ryo Murakawa