Cannot get GPU passthrough to VM, exhausted my knowledge


ogsirbe

Recommended Posts

Hello all,

 

I have exhausted my knowledge and just don't know what to do. I've watched every single Spaceinvader video, I'm scoured these forums, and I just can't figure out what the issue is. I have made sure my GPU was in its own IOMMU group, I made sure that I dumped my bios correctly. I made sure that my XML code matched SpaceInvaders. I've tried different vbios, I've tried different machine types, I've tried balance power and power saving mode. I'm just not sure what to do or where to go. Unfortunately my knowledge in Linux isn't vast. So I am having a difficult time reading through my System logs. 

 

Every time I try and boot my Windows 10 VM with my GTX 980 as the passthrough, I cannot get a connection and it instantly fills my Memory Log to 100%. I have to restart my server every time I boot this VM (I don't boot it up anymore, not until I'm able to solve the issue). If anyone can take the time out and help or by guiding me to the right errors to look at, I would appreciate it! But I am lost and will admit I have exhausted my knowledge and feel as if I'm in over my head.

 

https://pastebin.com/Dc2dkn86 Here is my syslog1 paste

https://pastebin.com/R46eKvbf Here is my syslog2 paste

 

Feb 9 16:18:21 BMserver kernel: vfio-pci 0000:05:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem

Feb 9 16:18:21 BMserver kernel: br0: port 2(vnet0) entered blocking state

Feb 9 16:18:21 BMserver kernel: br0: port 2(vnet0) entered disabled state

Feb 9 16:18:21 BMserver kernel: device vnet0 entered promiscuous mode

Feb 9 16:18:21 BMserver kernel: br0: port 2(vnet0) entered blocking state

Feb 9 16:18:21 BMserver kernel: br0: port 2(vnet0) entered forwarding state

Feb 9 16:18:22 BMserver avahi-daemon[9184]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:feb9:44d2.

Feb 9 16:18:22 BMserver avahi-daemon[9184]: New relevant interface vnet0.IPv6 for mDNS.

Feb 9 16:18:22 BMserver avahi-daemon[9184]: Registering new address record for fe80::fc54:ff:feb9:44d2 on vnet0.*.

Feb 9 16:18:22 BMserver kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x1e@0x258

Feb 9 16:18:22 BMserver kernel: vfio_ecap_init: 0000:05:00.0 hiding ecap 0x19@0x900

Feb 9 16:18:22 BMserver kernel: vfio-pci 0000:05:00.0: BAR 3: can't reserve [mem 0xd0000000-0xd1ffffff 64bit pref]

Feb 9 16:18:22 BMserver kernel: vfio-pci 0000:05:00.0: No more image in the PCI ROM

Feb 9 16:18:22 BMserver acpid: input device has been disconnected, fd 5

Feb 9 16:18:22 BMserver acpid: input device has been disconnected, fd 6

Feb 9 16:18:22 BMserver acpid: input device has been disconnected, fd 7

Feb 9 16:18:33 BMserver kernel: usb 2-1.2: reset low-speed USB device number 4 using ehci-pci

Feb 9 16:18:33 BMserver kernel: usb 2-1.4: reset low-speed USB device number 6 using ehci-pci

Feb 9 16:18:54 BMserver kernel: vfio-pci 0000:05:00.0: BAR 3: can't reserve [mem 0xd0000000-0xd1ffffff 64bit pref]

### [PREVIOUS LINE REPEATED 390589 TIMES] ###

 

 

Feb 9 18:22:17 BMserver kernel: vfio-pci 0000:05:00.0: BAR 3: can't reserve [mem 0xd0000000-0xd1ffffff 64bit pref]

Feb 9 18:22:17 BMserver kernel: vfio-pci 0000:05:00.0: No more image in the PCI ROM

Feb 9 18:22:17 BMserver kernel: vfio-pci 0000:05:00.1: enabling device (0100 -> 0102)

Feb 9 18:22:17 BMserver acpid: input device has been disconnected, fd 5

Feb 9 18:22:17 BMserver acpid: input device has been disconnected, fd 6

Feb 9 18:22:17 BMserver acpid: input device has been disconnected, fd 7

Feb 9 18:22:17 BMserver avahi-daemon[9184]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe05:6a4a.

Feb 9 18:22:17 BMserver avahi-daemon[9184]: New relevant interface vnet0.IPv6 for mDNS.

Feb 9 18:22:17 BMserver avahi-daemon[9184]: Registering new address record for fe80::fc54:ff:fe05:6a4a on vnet0.*.

Feb 9 18:22:20 BMserver kernel: vfio-pci 0000:05:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem

Feb 9 18:22:34 BMserver kernel: vfio-pci 0000:05:00.0: BAR 3: can't reserve [mem 0xd0000000-0xd1ffffff 64bit pref]

### [PREVIOUS LINE REPEATED 485036 TIMES] ###

 

 

Feb 9 18:22:51 BMserver kernel: vfio-pci 0000:05:00.0: BAR 3: can't reserve [mem 0xd0000000-0xd1ffffff 64bit pref]

### [PREVIOUS LINE REPEATED 154370 TIMES] ###

 

This is the only section where my untrained eye keeps going to. It makes sense that this issue started when I began messing with passing through my GPU to a VM. And I'm seeing the IOMMU grouping 05:00:00, then obviously I see how many times the line repeats, which leads me to believe it's what's insta filling my Memory Log

 

 

Edited by ogsirbe
Link to comment
  • 4 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.