Masterbob221 Posted July 10, 2020 Posted July 10, 2020 for my vm using gpu passthrough i have tried starting it up and it up and nothing shows on my display please help me! Â my setup is 3900x x570 aorus elite gtx 1660ti Quote
meep Posted July 10, 2020 Posted July 10, 2020 22 minutes ago, Masterbob221 said: for my vm using gpu passthrough i have tried starting it up and it up and nothing shows on my display please help me!  my setup is 3900x x570 aorus elite gtx 1660ti Hi there  to ensure you get help, you will need to provide more information, specifically;  1. What have you done so far? What guides have you followed? 2. What OS have you installed in the VM? 3. Does the vm work ok with vnc display? 4. Share your vm xml 5. Share any details from the vm log file 6. What other devices are in your system. Is the gpu the only one?  to get started with troubleshooting, I would suggest the following; 1. Remove the gpu passthrough 2. Boot the vm using vnc 3. Open netplwiz (if Windows) and allow users logon without entering password. This will ensure your system boots to desktop and does not get stuck at a logon prompt you cannot see. 4 Install splashtop streamer in the vm. 5 install splashtop viewer on some other system 6. Reboot the vm, still in vnc mode, and ensure you can access it using splashtop 7. Shutdown the vm, and add back the gpu passthrough, ensuring you follow all advice about bios dumps, not splitting the video and audio devices etc.  now when your system boots, even if your display is dark, you should be able to access the vm via splashtop and see what’s going on. I suspect you’ll see an error -43 when you view the gpu in device manager.  if the above does not work, you may need to be lame familiar with virt-manager docker which will allow finer control over vm configuration and troubleshooting.     Quote
Masterbob221 Posted July 10, 2020 Author Posted July 10, 2020 31 minutes ago, meep said: Hi there  to ensure you get help, you will need to provide more information, specifically;  1. What have you done so far? What guides have you followed? 2. What OS have you installed in the VM? 3. Does the vm work ok with vnc display? 4. Share your vm xml 5. Share any details from the vm log file 6. What other devices are in your system. Is the gpu the only one?  to get started with troubleshooting, I would suggest the following; 1. Remove the gpu passthrough 2. Boot the vm using vnc 3. Open netplwiz (if Windows) and allow users logon without entering password. This will ensure your system boots to desktop and does not get stuck at a logon prompt you cannot see. 4 Install splashtop streamer in the vm. 5 install splashtop viewer on some other system 6. Reboot the vm, still in vnc mode, and ensure you can access it using splashtop 7. Shutdown the vm, and add back the gpu passthrough, ensuring you follow all advice about bios dumps, not splitting the video and audio devices etc.  now when your system boots, even if your display is dark, you should be able to access the vm via splashtop and see what’s going on. I suspect you’ll see an error -43 when you view the gpu in device manager.  if the above does not work, you may need to be lame familiar with virt-manager docker which will allow finer control over vm configuration and troubleshooting.  i followed spaceinvader one guide i have windows 10 it works using vnc idk what xml is latest log is: display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=33,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -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 virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -blockdev '{"driver":"file","filename":"/mnt/disk2/steph pc/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Windows.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-cd,bus=ide.0,unit=0,drive=libvirt-2-format,id=ide0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.173-2.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \ -netdev tap,fd=35,id=hostnet0,vhost=on,vhostfd=36 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:ef:fd:47,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=38,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -device vfio-pci,host=0000:03:00.0,id=hostdev0,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:03:00.1,id=hostdev1,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-07-10 10:38:18.887+0000: Domain id=16 is tainted: high-privileges 2020-07-10 10:38:18.887+0000: Domain id=16 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2020-07-10T10:38:20.599380Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.1, depends on group 24 which is not owned. 2020-07-10T10:38:45.586009Z qemu-system-x86_64: terminating on signal 15 from pid 3490 (/usr/sbin/libvirtd) 2020-07-10 10:38:45.986+0000: shutting down, reason=destroyed  with using splashtop it doesnt show up when not on vnc    Quote
meep Posted July 10, 2020 Posted July 10, 2020 When editing you VM, look at the top right of the page. See a toggle widget labeled 'form view'? Switch this to XML vide. This shows the VM configuration data in a code (XML) view. Please paste that here.  Please also paste the 'PCI Devices and IOMMU Groups' section when you navigate to Tools->System Devices  The fact that Splashtop is not enabled when you boot with GPU only indicates that your system is not booting, but you cannot see why.  My advice here would be to install the VIRT-Manager docker, add a QXL adapter alongside your GPU, edit the VM XML to ensure this new adapter is the first to init and observe the boot process in VIRT-Manager.  However, the fact that you are not aware of what your VM XML is means that's quite a hill to climb! Le's start with the XML and PCI IOMMU device listing first and take it from there.  Quote
Masterbob221 Posted July 10, 2020 Author Posted July 10, 2020 7 minutes ago, meep said: When editing you VM, look at the top right of the page. See a toggle widget labeled 'form view'? Switch this to XML vide. This shows the VM configuration data in a code (XML) view. Please paste that here.  Please also paste the 'PCI Devices and IOMMU Groups' section when you navigate to Tools->System Devices  The fact that Splashtop is not enabled when you boot with GPU only indicates that your system is not booting, but you cannot see why.  My advice here would be to install the VIRT-Manager docker, add a QXL adapter alongside your GPU, edit the VM XML to ensure this new adapter is the first to init and observe the boot process in VIRT-Manager.  However, the fact that you are not aware of what your VM XML is means that's quite a hill to climb! Le's start with the XML and PCI IOMMU device listing first and take it from there.  my iommu groups are OMMU 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.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 2:[1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 3:[1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4:[1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 5:[1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 6:[1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 7:[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 8:[1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 9:[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 10:[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 11:[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 12:[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 13:[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 14:[1022:57ad] 01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream IOMMU group 15:[1022:57a3] 02:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 16:[1022:57a3] 02:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 17:[1022:57a3] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 18:[1022:57a3] 02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 19:[1022:57a4] 02:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 20:[1022:57a4] 02:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 21:[1022:57a4] 02:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 22:[10de:2182] 03:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] (rev a1) IOMMU group 23:[10de:1aeb] 03:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1) IOMMU group 24:[10de:1aec] 03:00.2 USB controller: NVIDIA Corporation Device 1aec (rev a1) IOMMU group 25:[10de:1aed] 03:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] (rev a1) IOMMU group 26:[8086:24fb] 04:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) IOMMU group 27:[8086:1539] 05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 28:[10ec:8125] 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller IOMMU group 29:[1022:1485] 07:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 30:[1022:149c] 07:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 31:[1022:149c] 07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 32:[1022:7901] 08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 33:[1022:7901] 09:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 34:[1022:148a] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 35:[1022:1485] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 36:[1022:1486] 0b:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 37:[1022:149c] 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 38:[1022:1487] 0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller IOMMU group 39:[1022:7901] 0c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 40:[1022:7901] 0d:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)  CPU Thread Pairings Pair 1:cpu 0 / cpu 12 Pair 2:cpu 1 / cpu 13 Pair 3:cpu 2 / cpu 14 Pair 4:cpu 3 / cpu 15 Pair 5:cpu 4 / cpu 16 Pair 6:cpu 5 / cpu 17 Pair 7:cpu 6 / cpu 18 Pair 8:cpu 7 / cpu 19 Pair 9:cpu 8 / cpu 20 Pair 10:cpu 9 / cpu 21 Pair 11:cpu 10 / cpu 22 Pair 12:cpu 11 / cpu 23  USB Devices Bus 001 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002:ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 003:ID 046d:c539 Logitech, Inc. USB Receiver Bus 003 Device 004:ID 1532:0504 Razer USA, Ltd USB2.0 Hub Bus 003 Device 005:ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 006:ID 048d:8297 Integrated Technology Express, Inc. ITE Device(8595) Bus 003 Device 007:ID 1532:0204 Razer USA, Ltd USB Receiver Bus 004 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002:ID 8087:0aa7 Intel Corp. Bus 005 Device 003:ID 05e3:0608 Genesys Logic, Inc. Hub Bus 006 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 002:ID 0930:1400 Toshiba Corp. Memory Stick 2GB Bus 008 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub  SCSI Devices [0:0:0:0]disk TOSHIBA TOSHIBA USB DRV PMAP /dev/sda 15.5GB [4:0:0:0]disk ATA ST4000VN008-2DR1 SC60 /dev/sdb 4.00TB [6:0:0:0]disk ATA WDC WD10EZEX-60W 1A01 /dev/sdc 1.00TB [10:0:0:0]disk ATA Samsung SSD 860 4B6Q /dev/sdd 500GB  xml:  <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'>  <name>steph pc</name>  <uuid>6cc62df6-1674-4192-0d43-1f674f5ff4a8</uuid>  <metadata>   <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>  </metadata>  <memory unit='KiB'>13107200</memory>  <currentMemory unit='KiB'>13107200</currentMemory>  <memoryBacking>   <nosharepages/>  </memoryBacking>  <vcpu placement='static'>10</vcpu>  <cputune>   <vcpupin vcpu='0' cpuset='2'/>   <vcpupin vcpu='1' cpuset='14'/>   <vcpupin vcpu='2' cpuset='4'/>   <vcpupin vcpu='3' cpuset='16'/>   <vcpupin vcpu='4' cpuset='6'/>   <vcpupin vcpu='5' cpuset='18'/>   <vcpupin vcpu='6' cpuset='8'/>   <vcpupin vcpu='7' cpuset='20'/>   <vcpupin vcpu='8' cpuset='10'/>   <vcpupin vcpu='9' cpuset='22'/>  </cputune>  <os>   <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type>   <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>   <nvram>/etc/libvirt/qemu/nvram/6cc62df6-1674-4192-0d43-1f674f5ff4a8_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='5' threads='2'/>   <cache mode='passthrough'/>   <feature policy='require' name='topoext'/>  </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='disk'>    <driver name='qemu' type='raw' cache='writeback'/>    <source file='/mnt/disk2/steph pc/vdisk1.img'/>    <target dev='hdc' bus='virtio'/>    <boot order='1'/>    <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>   </disk>   <disk type='file' device='cdrom'>    <driver name='qemu' type='raw'/>    <source file='/mnt/user/isos/Windows.iso'/>    <target dev='hda' bus='ide'/>    <readonly/>    <boot order='2'/>    <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.173-2.iso'/>    <target dev='hdb' bus='ide'/>    <readonly/>    <address type='drive' controller='0' bus='0' target='0' unit='1'/>   </disk>   <controller type='usb' index='0' model='ich9-ehci1'>    <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>   </controller>   <controller type='usb' index='0' model='ich9-uhci1'>    <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'>    <master startport='2'/>    <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>   </controller>   <controller type='usb' index='0' model='ich9-uhci3'>    <master startport='4'/>    <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>   </controller>   <controller type='pci' index='0' model='pci-root'/>   <controller type='ide' index='0'>    <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>   </controller>   <controller type='virtio-serial' index='0'>    <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>   </controller>   <interface type='bridge'>    <mac address='52:54:00:ef:fd:47'/>    <source bridge='br0'/>    <model type='virtio'/>    <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>   </interface>   <serial type='pty'>    <target type='isa-serial' port='0'>     <model name='isa-serial'/>    </target>   </serial>   <console type='pty'>    <target type='serial' port='0'/>   </console>   <channel type='unix'>    <target type='virtio' name='org.qemu.guest_agent.0'/>    <address type='virtio-serial' controller='0' bus='0' port='1'/>   </channel>   <input type='tablet' bus='usb'>    <address type='usb' bus='0' port='1'/>   </input>   <input type='mouse' bus='ps2'/>   <input type='keyboard' bus='ps2'/>   <hostdev mode='subsystem' type='pci' managed='yes'>    <driver name='vfio'/>    <source>     <address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>    </source>    <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>   </hostdev>   <hostdev mode='subsystem' type='pci' managed='yes'>    <driver name='vfio'/>    <source>     <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/>    </source>    <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>   </hostdev>   <memballoon model='none'/>  </devices> </domain>  i am very new to this and in the past have only used vnc, i was wondering if to make this more easy you could hop in a call with me for a quick minute. My discord tag is Nic#3482 Quote
meep Posted July 10, 2020 Posted July 10, 2020 Hey @Masterbob221  Good to chat with you just now. For others, to go over what we discussed;  1. You set up a new VM using SeaBios 2. You made edits to XML to ensure that GPU Video & Audio devices are not split across two virtual slots (don't forget the 'multifunction' tag)  If when your VM comes up, you still don't have picture, you can try following SpaceInvaderOnes more recent videos on obtaining, editing and passing through a ROM Bios file for your specific card.  If you do get a picture, but have issues installing nVidia drivers or see a -43 error in Device Manager, you can add the configuration to your XML that I outline here.  Good luck!  Quote
Masterbob221 Posted July 10, 2020 Author Posted July 10, 2020 20 minutes ago, meep said: Hey @Masterbob221  Good to chat with you just now. For others, to go over what we discussed;  1. You set up a new VM using SeaBios 2. You made edits to XML to ensure that GPU Video & Audio devices are not split across two virtual slots (don't forget the 'multifunction' tag)  If when your VM comes up, you still don't have picture, you can try following SpaceInvaderOnes more recent videos on obtaining, editing and passing through a ROM Bios file for your specific card.  If you do get a picture, but have issues installing nVidia drivers or see a -43 error in Device Manager, you can add the configuration to your XML that I outline here.  Good luck!  it all works now just for some reason my mouse didnt passthrough ill work that out tommorow. id like to reiterate my gratefulness for your support and if there is a way to + rep you please let me know and id be happy to do it! Quote
meep Posted July 10, 2020 Posted July 10, 2020 9 minutes ago, Masterbob221 said: it all works now just for some reason my mouse didnt passthrough ill work that out tommorow. id like to reiterate my gratefulness for your support and if there is a way to + rep you please let me know and id be happy to do it! Great to hear it’s working for you. Thanks are enough, just pay it forward sometime! Quote
Recommended Posts
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.