VM Broken after upgrading GPU


Recommended Posts

Computer Specs:

 

Motherboard: Gigabyte X570 Aorus Pro Wifi

CPU: AMD Ryzen 3900x

GPU: MSI RTX 2070 Super Armor

 

Note: I gave 2 cores and 2 threads to the VM. WHen the screen is black Only 1 core is being used and its at 100%.

 

Everything was working fine until i switched my GPU  from 980GTX to RTX 2070 Super.

I keep getting a black screen when I boot into windows. Weird thing is that the monitor is getting a signal because the led light on my monitor is blue (goes orange if no signal). So, I deleted the VM and created a new one with a fresh install of Windows 10. As soon as it installs the drivers. The screen goes black. At first i thought it was frozen so I restarted and as soon as windows boots up screen goes black again. This time I left it there and in about 10 minutes. The screens come back with the drivers being installed. THis happens everytime I restart this VM.

 

Machine Type: Q35 3.1

BIOS: OVMF

Boot Type: Legacy

 

IOMMU group 0:    [1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 1:    [1022:1483] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
IOMMU group 2:    [1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
IOMMU group 3:    [1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 4:    [1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 5:    [1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
IOMMU group 6:    [1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 7:    [1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 8:    [1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 9:    [1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 10:    [1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
IOMMU group 11:    [1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 12:    [1022:1484] 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 13:    [1022:1484] 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
IOMMU group 14:    [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
IOMMU group 15:    [1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0
[1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1
[1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2
[1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3
[1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4
[1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5
[1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6
[1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7
IOMMU group 16:    [1987:5012] 01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01)
IOMMU group 17:    [1022:57ad] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57ad
IOMMU group 18:    [1022:57a3] 03:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3
IOMMU group 19:    [1022:57a3] 03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3
IOMMU group 20:    [1022:57a3] 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3
IOMMU group 21:    [1022:57a4] 03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4
IOMMU group 22:    [1022:57a4] 03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4
IOMMU group 23:    [1022:57a4] 03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4
IOMMU group 24:    [1000:0072] 04:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
IOMMU group 25:    [8086:2723] 05:00.0 Network controller: Intel Corporation Device 2723 (rev 1a)
IOMMU group 26:    [8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
IOMMU group 27:    [1022:1485] 07:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
[1022:149c] 07:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
[1022:149c] 07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
IOMMU group 28:    [1022:7901] 08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
IOMMU group 29:    [1022:7901] 09:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

 

I have all devices in group 30 stubbed:

IOMMU group 30:    [10de:1e84] 0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1e84 (rev a1)
[10de:10f8] 0a:00.1 Audio device: NVIDIA Corporation Device 10f8 (rev a1)
[10de:1ad8] 0a:00.2 USB controller: NVIDIA Corporation Device 1ad8 (rev a1)
[10de:1ad9] 0a:00.3 Serial bus controller [0c80]: NVIDIA Corporation Device 1ad9 (rev a1)

 

IOMMU group 31:    [1022:148a] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
IOMMU group 32:    [1022:1485] 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
[1022:1486] 0c:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
[1022:149c] 0c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
[1022:1487] 0c:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
IOMMU group 33:    [1022:7901] 0d:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
IOMMU group 34:    [1022:7901] 0e:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
 

 

My XML:

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='1'>
  <name>Windows 10 www.facebppk</name>
  <uuid>526aea6d-9ceg-01f4-65e4-7811fb9f1ae5</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>10485760</memory>
  <currentMemory unit='KiB'>10485760</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='14'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='15'/>
    <vcpupin vcpu='4' cpuset='4'/>
    <vcpupin vcpu='5' cpuset='16'/>
    <vcpupin vcpu='6' cpuset='5'/>
    <vcpupin vcpu='7' cpuset='17'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-3.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/526aea6d-9ceg-01f4-65e4-7811fb9f1ae5_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none'>
    <topology sockets='1' cores='8' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Win10_1903_V1_English_x64.iso'/>
      <backingStore/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <alias name='sata0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.160-1.iso'/>
      <backingStore/>
      <target dev='hdb' bus='sata'/>
      <readonly/>
      <alias name='sata0-0-1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7239045B53'/>
      <backingStore/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <alias name='sata0-0-2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-CT500MX500SSD1_1752E108D9BD'/>
      <backingStore/>
      <target dev='hdd' bus='virtio'/>
      <alias name='virtio-disk3'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-CT2000MX500SSD1_1920E2045697'/>
      <backingStore/>
      <target dev='hde' bus='virtio'/>
      <alias name='virtio-disk4'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/ata-WDC_WD3003FZEX-00Z4SA0_WD-WCC132352776'/>
      <backingStore/>
      <target dev='hdf' bus='virtio'/>
      <alias name='virtio-disk5'/>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </disk>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x8'/>
      <alias name='pci.1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x9'/>
      <alias name='pci.2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x13'/>
      <alias name='pci.3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0xb'/>
      <alias name='pci.4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0xc'/>
      <alias name='pci.5'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
    </controller>
    <controller type='pci' index='6' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='6' port='0xd'/>
      <alias name='pci.6'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
    </controller>
    <controller type='pci' index='7' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='7' port='0xe'/>
      <alias name='pci.7'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/>
    </controller>
    <controller type='pci' index='8' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='8' port='0xf'/>
      <alias name='pci.8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/>
    </controller>
    <controller type='pci' index='9' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='9' port='0x10'/>
      <alias name='pci.9'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='10' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='10' port='0xa'/>
      <alias name='pci.10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:d8:0c:3a'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10 www.faceb/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'>
      <alias name='input0'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input1'/>
    </input>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev0'/>
      <rom file='/mnt/user/Virtual Machines/msi2070supereditted.rom'/>
      <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0a' slot='0x00' function='0x1'/>
      </source>
      <alias name='hostdev1'/>
      <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
      </source>
      <alias name='hostdev2'/>
      <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0a' slot='0x00' function='0x2'/>
      </source>
      <alias name='hostdev3'/>
      <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x0a' slot='0x00' function='0x3'/>
      </source>
      <alias name='hostdev4'/>
      <address type='pci' domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc53f'/>
        <address bus='1' device='4'/>
      </source>
      <alias name='hostdev5'/>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1b1c'/>
        <product id='0x1b2d'/>
        <address bus='5' device='2'/>
      </source>
      <alias name='hostdev6'/>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0xb58e'/>
        <product id='0x9e84'/>
        <address bus='3' device='5'/>
      </source>
      <alias name='hostdev7'/>
      <address type='usb' bus='0' port='3'/>
    </hostdev>
    <memballoon model='none'/>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>
 

Edited by Sleepyme
Link to comment
22 hours ago, jonp said:

Have you tried setting the VM back to i440fx now that you're using the new GPU?

No dice.

 

Now when installing the drivers. The screen goes black and 10 or so minutes later the vm pauses. If i resume i get this error: "internal error: unable to execute QEMU command 'cont': Resetting the virtual machine required"

 

I tried updating motherboard bios to latest beta version as well and samething happens.

Link to comment

When the VM Paused I checked the logs:

-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \
-device ahci,id=sata0,bus=pci.0,addr=0x3 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \
-drive file=/dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7239045B53,format=raw,if=none,id=drive-virtio-disk2,cache=writeback \
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \
-drive file=/mnt/user/isos/Win10_1903_V1_English_x64.iso,format=raw,if=none,id=drive-sata0-0-0,readonly=on \
-device ide-cd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2 \
-drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-sata0-0-1,readonly=on \
-device ide-cd,bus=sata0.1,drive=drive-sata0-0-1,id=sata0-0-1 \
-netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:d6:40:fc,bus=pci.0,addr=0x2 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=37,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device 'vfio-pci,host=0000:0a:00.0,id=hostdev0,bus=pci.0,addr=0x6,romfile=/mnt/user/Virtual Machines/msi2070supereditted.rom' \
-device vfio-pci,host=0000:0a:00.1,id=hostdev1,bus=pci.0,addr=0x8 \
-device vfio-pci,host=0000:0a:00.2,id=hostdev2,bus=pci.0,addr=0x9 \
-device vfio-pci,host=0000:0a:00.3,id=hostdev3,bus=pci.0,addr=0xa \
-device usb-host,hostbus=1,hostaddr=4,id=hostdev4,bus=usb.0,port=1 \
-device usb-host,hostbus=1,hostaddr=2,id=hostdev5,bus=usb.0,port=2 \
-device usb-host,hostbus=5,hostaddr=2,id=hostdev6,bus=usb.0,port=3 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2019-10-19 03:42:34.136+0000: Domain id=4 is tainted: high-privileges
2019-10-19 03:42:34.136+0000: Domain id=4 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2019-10-19T04:06:01.256711Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0a:00.3) Unrecoverable error detected. Please collect any data possible and then kill the guest
2019-10-19T04:06:01.270521Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0a:00.2) Unrecoverable error detected. Please collect any data possible and then kill the guest
2019-10-19T04:06:01.270532Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0a:00.1) Unrecoverable error detected. Please collect any data possible and then kill the guest
2019-10-19T04:06:01.270539Z qemu-system-x86_64: vfio_err_notifier_handler(0000:0a:00.0) Unrecoverable error detected. Please collect any data possible
and then kill the guest

 

The highlighted text in the VM log has something to do with my video card:

 

IOMMU group 32:[10de:1e84] 0a:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] (rev a1)

IOMMU group 33:[10de:10f8] 0a:00.1 Audio device: NVIDIA Corporation Device 10f8 (rev a1)

IOMMU group 34:[10de:1ad8] 0a:00.2 USB controller: NVIDIA Corporation Device 1ad8 (rev a1)

IOMMU group 35:[10de:1ad9] 0a:00.3 Serial bus controller [0c80]: NVIDIA Corporation Device 1ad9 (rev a1)

Link to comment

I hate to say this, but it could be an issue with the GPU itself.  Some GPUs don't like being assigned to VMs for one reason or another.  The only brand I've trusted so far has been EVGA.  I've seen issues with Gigabyte, MSI, and ASUS branded cards, though to be honest, its been a while.  We've also not tested the SUPER class of RTX cards yet, but since they are based on the same tech as the 2080 Ti's we've tested, I'm fairly certain its not a chipset-specific issue.

 

Do you have another GPU you could test with or are you within the return window for that card?  If so, I'd recommend an EVGA replacement over that MSI device.

Link to comment

For what it's worth, I have the following card working well, moved from a Vega 56 due to the reset bug making my life more difficult than it needed to be.

 

MSI Gaming GeForce RTX 2060 Super 8GB GDRR6 256-bit HDMI/DP G-SYNC Turing Architecture Overclocked Graphics Card (RTX 2060 Super Armor OC).

Link to comment
1 hour ago, harshl said:

For what it's worth, I have the following card working well, moved from a Vega 56 due to the reset bug making my life more difficult than it needed to be.

 

MSI Gaming GeForce RTX 2060 Super 8GB GDRR6 256-bit HDMI/DP G-SYNC Turing Architecture Overclocked Graphics Card (RTX 2060 Super Armor OC).

Yeah I'm still struggling with mine. It works but it just takes forever for windows to load (atleast 10 minutes) and during that 10 minutes 1 cpu core will be at 100% usuage alternating between other cores every so often. What motherboard do you use?

 

Note: i tried another operating system abd they all do the same thing (windows 7, linux) so its not the os. Like as soon as the drivers are loaded the screen goes black.

Link to comment
5 hours ago, jonp said:

I hate to say this, but it could be an issue with the GPU itself.  Some GPUs don't like being assigned to VMs for one reason or another.  The only brand I've trusted so far has been EVGA.  I've seen issues with Gigabyte, MSI, and ASUS branded cards, though to be honest, its been a while.  We've also not tested the SUPER class of RTX cards yet, but since they are based on the same tech as the 2080 Ti's we've tested, I'm fairly certain its not a chipset-specific issue.

 

Do you have another GPU you could test with or are you within the return window for that card?  If so, I'd recommend an EVGA replacement over that MSI device.

Unfortunately i can't return it.

Link to comment
6 minutes ago, Sleepyme said:

Yeah I'm still struggling with mine. It works but it just takes forever for windows to load (atleast 10 minutes) and during that 10 minutes 1 cpu core will be at 100% usuage alternating between other cores every so often. What motherboard do you use?

 

Note: i tried another operating system abd they all do the same thing (windows 7, linux) so its not the os. Like as soon as the drivers are loaded the screen goes black.

ASRock Z390 Taichi Bios - Version P4.00. Dated: 03/13/2019

Intel® Core™ i9-9900K

 

Been super solid for me so far. Hope your able to figure something out.

Link to comment

Been playing with some BIOS settings and if I have PCIE AER enabled. I get the following errors in my logs. And windows won't boot. It gets stuck on the black screen for 10 minutes then VM pauses. If I disable PCIE AER Windows will boot but it  just takes forever.... I wonder if this is a BIOS issue.

 

Oct 22 15:21:10 Vault001 kernel: pcieport 0000:00:03.1: AER: Uncorrected (Non-Fatal) error received: 0000:00:03.1
Oct 22 15:21:10 Vault001 kernel: pcieport 0000:00:03.1: AER: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
Oct 22 15:21:10 Vault001 kernel: pcieport 0000:00:03.1: AER: device [1022:1483] error status/mask=00100000/04400000
Oct 22 15:21:10 Vault001 kernel: pcieport 0000:00:03.1: AER: [20] UnsupReq (First)
Oct 22 15:21:10 Vault001 kernel: pcieport 0000:00:03.1: AER: TLP Header: 34000000 0a000010 00000000 00000000
Oct 22 15:21:10 Vault001 kernel: pcieport 0000:00:03.1: AER: Device recovery successful
 

This error is caused by:

IOMMU group 1:[1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 4:[1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

Edited by Sleepyme
Link to comment

You are using Q35 3.1 but I don't see this bit of code at the end of your xml before </domain>

  <qemu:commandline>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.speed=8'/>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.width=16'/>
  </qemu:commandline>

That bit of code coupling with the root port patch, makes your Q35 PCIe slot run at the right speed. Without that, you might have some unexpected issues with passing through devices.

 

Perhaps try adding that bit of code before </domain>

 

Alternatively, and preferably, update to 6.8.0-rc3. It has qemu 4.1 which has better PCIe support. I no longer need that bit of code in my VM template and things seem to be running fine so far.

Edited by testdasi
Link to comment
8 minutes ago, testdasi said:

You are using Q35 3.1 but I don't see this bit of code at the end of your xml before </domain>


  <qemu:commandline>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.speed=8'/>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.width=16'/>
  </qemu:commandline>

That bit of code coupling with the root port patch, makes your Q35 PCIe slot run at the right speed. Without that, you might have some unexpected issues with passing through devices.

 

Perhaps try adding that bit of code before </domain>

 

Alternatively, and preferably, update to 6.8.0-rc3. It has qemu 4.1 which has better PCIe support. I no longer need that bit of code in my VM template and things seem to be running fine so far.

Thanks! I will try that after work!

Link to comment
10 hours ago, testdasi said:

You are using Q35 3.1 but I don't see this bit of code at the end of your xml before </domain>


  <qemu:commandline>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.speed=8'/>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.width=16'/>
  </qemu:commandline>

That bit of code coupling with the root port patch, makes your Q35 PCIe slot run at the right speed. Without that, you might have some unexpected issues with passing through devices.

 

Perhaps try adding that bit of code before </domain>

 

Alternatively, and preferably, update to 6.8.0-rc3. It has qemu 4.1 which has better PCIe support. I no longer need that bit of code in my VM template and things seem to be running fine so far.

Hey! I just want to THANK YOU for suggesting me to update to 6.8.0-rc3 and switching to q35 4.1 because that totally fixed my issue!!!!!!

 

Thank you soooo much! My VM now loads up in under 5 seconds!

Link to comment

Windows booted right up after changing to q35 4.1. After playing Apex Legends for a few hours I got a blue screen: "Stop code: Kernel Security Check Failure." Then restarted computer and now its back to being slow at boot up. Gonna run a memtest.

Edited by Sleepyme
Link to comment
8 hours ago, Sleepyme said:

Windows booted right up after changing to q35 4.1. After playing Apex Legends for a few hours I got a blue screen: "Stop code: Kernel Security Check Failure." Then restarted computer and now its back to being slow at boot up. Gonna run a memtest.

That can sometimes happen due to driver corruption so I suggest also reinstall the Nvidia driver too.

Link to comment

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.