With kernel 4.9-rc1 the default vfio option still fails with the same errors but with <driver name='kvm'/> the virtual machine starts absolutely fine even though the vm log still shows
/var/log/libvirt/qemu/devsrv.log 2016-10-20T21:03:04.432081Z qemu-system-x86_64: -device pci- assign,configfd=30,host=03:10.0,id=hostdev0,bus=pci.0,addr=0x3: pci- assign: Invalid ROM. .. and syslog (just incase it helps) Oct 20 22:03:03 vmsrv2 kernel: [ 565.182587] pci-stub 0000:03:10.0: claimed by stub Oct 20 22:03:03 vmsrv2 kernel: [ 565.230673] igb 0000:02:00.0: setting MAC 52:54:00:ad:08:c6 on VF 0 Oct 20 22:03:03 vmsrv2 kernel: [ 565.230674] igb 0000:02:00.0: Reload the VF driver to make this change effective. Oct 20 22:03:03 vmsrv2 kernel: [ 565.345844] audit: type=1400 audit(1476997383.879:37): apparmor="STATUS" operation="profile_load" name="libvirt-dc50d250-3c1c-4f40-87d3-0b7b877e53fc" pid=8661 comm="apparmor_parser" Oct 20 22:03:03 vmsrv2 kernel: [ 565.345899] audit: type=1400 audit(1476997383.879:38): apparmor="STATUS" operation="profile_load" name="libvirt-dc50d250-3c1c-4f40-87d3-0b7b877e53fc//qemu_bridge_helper" pid=8661 comm="apparmor_parser" Oct 20 22:03:03 vmsrv2 kernel: [ 565.374016] qemu-system-x86: sending ioctl 5326 to a partition! Oct 20 22:03:03 vmsrv2 kernel: [ 565.389363] pci-stub 0000:03:10.0: enabling device (0000 -> 0002) Oct 20 22:03:04 vmsrv2 kernel: [ 565.892188] pci-stub 0000:03:10.0: kvm assign device Oct 20 22:03:04 vmsrv2 virtlogd[4936]: End of file while reading data: Input/output error Oct 20 22:03:06 vmsrv2 kernel: [ 568.138093] kvm: zapping shadow pages for mmio generation wraparound Oct 20 22:03:07 vmsrv2 kernel: [ 568.622496] kvm: zapping shadow pages for mmio generation wraparound Oct 20 22:03:16 vmsrv2 kernel: [ 578.167125] kvm [8663]: vcpu0, guest rIP: 0xffffffff81064486 unhandled rdmsr: 0x34 Oct 20 22:03:16 vmsrv2 kernel: [ 578.167186] kvm [8663]: vcpu0, guest rIP: 0xffffffff81064486 unhandled rdmsr: 0x606 Oct 20 22:03:16 vmsrv2 kernel: [ 578.448970] igb 0000:02:00.0: VF 0 attempted to override administratively set MAC address Oct 20 22:03:16 vmsrv2 kernel: [ 578.448970] Reload the VF driver to resume operations Oct 20 22:03:20 vmsrv2 kernel: [ 582.355187] kvm [8663]: vcpu0, guest rIP: 0xffffffff81064486 unhandled rdmsr: 0x611 Oct 20 22:03:20 vmsrv2 kernel: [ 582.355228] kvm [8663]: vcpu0, guest rIP: 0xffffffff81064486 unhandled rdmsr: 0x639 Oct 20 22:03:20 vmsrv2 kernel: [ 582.355251] kvm [8663]: vcpu0, guest rIP: 0xffffffff81064486 unhandled rdmsr: 0x641 Oct 20 22:03:20 vmsrv2 kernel: [ 582.355272] kvm [8663]: vcpu0, guest rIP: 0xffffffff81064486 unhandled rdmsr: 0x619 I also tried kernel 4.7 (only with vfio as you replied before I went any further) and the virtual machine started but with no networking and the logs filled with messages /var/log/libvirt/qemu/devsrv.log 2016-10-20T19:00:07.145137Z qemu-system-x86_64: vfio_region_read(0000:03:10.0:region0+0xc40, 4) failed: Device or resource busy /var/log/syslog Oct 20 20:00:07 vmsrv2 kernel: [ 2223.026336] vfio-pci 0000:03:10.0: BAR 0: can't reserve [mem 0xdf200000-0xdf203fff 64bit pref] These messages were repeated constantly until I shut the VM down. Should I just use the 4.9-rc1 kernel for now, is there a downside to that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633634 Title: sr-iov not working on ubuntu 16.04 kvm Status in linux package in Ubuntu: Confirmed Bug description: The exact same set up (hardware and commands I have made) worked perfectly on Ubuntu 14.04 but I can't get it working with 16.04. The only thing I have changed between the 2 setups is adding <driver name='kvm'/> to the network definition as the now default vfio also failed with qemu-system-x86_64: vfio_dma_map(0x55f1c4f8bb00, 0xfe000000, 0x4000, 0x7fa687700000) = -14 (Bad address) qemu: hardware error: vfio: DMA mapping failed, unable to continue If I am doing something wrong I apologise, this is my first bug report and I'm still relatively new to Linux. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-42-generic 4.4.0-42.62 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Oct 14 20:11 seq crw-rw---- 1 root audio 116, 33 Oct 14 20:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Oct 14 23:05:26 2016 HibernationDevice: RESUME=UUID=bb1632fb-69fe-4d67-bc51-8182d2546d91 InstallationDate: Installed on 2016-10-08 (6 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: FUJITSU PRIMERGY TX1310 M1 PciMultimedia: ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic root=UUID=07b95c7c-db77-4cee-8336-6f24b2072da6 ro pcie_aspm=off intel_iommu=on iommu=pt pci=assign-busses quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-42-generic N/A linux-backports-modules-4.4.0-42-generic N/A linux-firmware 1.157.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.4 R1.5.0 for D3219-A1x dmi.board.name: D3219-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3219-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: TX1310M1 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.5.0forD3219-A1x:bd09/15/2015:svnFUJITSU:pnPRIMERGYTX1310M1:pvr:rvnFUJITSU:rnD3219-A1:rvrS26361-D3219-A1:cvnFUJITSU:ct6:cvrTX1310M1: dmi.product.name: PRIMERGY TX1310 M1 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
