• Posts

  • Joined

  • Last visited

Everything posted by twiikker

  1. I'm having problem that unmanic is not doing anything. I have setup it like in guide and looked up setting and such and tried to manually make it scan library but nothing happens.
  2. I've had one guy whose card just wouldn't work at all as only GPU. He changed it to different card and it worked without problems. Everything seems to be in order in your VM xml. I don't know if some cards have just bioses which wont work. I guess you have also tried with latest drivers? After 465 they should have beta virtualizion support. Havent checked it myself yet.
  3. ip link #to find ethernet port dhcpcd ens1 #set dhcp up ping #test connection use ip link to find out what is your interface name
  4. Happens to everyone you can also use some other vnc client like tightvnc so you can keep browser addons intact.
  5. Well. I just tried with latest arch image and only problem with my guide was that i didnt tell to select install iso. It booted to shell first and then after selecting iso it booted to install media without problem. So what exactly happens after you have made new VM and connected to it? Its just black screen or what?
  6. VNC remote is exactly what i mean and it should connect with default setting and only those changes which i have mentioned in guide. Haven't tried with latest version and do you have virtualizion enabled in bios and your computer supports it?
  7. did you map gpu soundcard also and are gpu and gpu soundcard on same iommu group?
  8. Does that windows 10 vm work normally without gpu passtrough? Im pretty sure that its upto something with that cpu and you need to figure some workaround over that. Many people seems to have same problem. Like by just googling kvm threadripper and that error.
  9. what cpu you have? Googled a bit that those tainted errors shouldnt matter but not sure about those other errors. My log also gets there errors at end but my boot time to login screen is ~25 seconds. So errors after that is propably what you should research. 2020-11-15 10:16:20.255+0000: Domain id=3 is tainted: high-privileges 2020-11-15 10:16:20.255+0000: Domain id=3 is tainted: custom-argv 2020-11-15 10:16:20.255+0000: Domain id=3 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0)
  10. Finally got it back working. So flashing back to older bios fixed my problems.
  11. Actually dont know if latest bios is the root cause since i cant get rid of error 43 currently. I though it was since my installation was old and i dont have extra activation key for that test machine which i made this guide. I don't think that i have changed anything else which would affect that. Have to double check bios settings if something in there has been changed. Agesa firmware.
  12. My bluescreen problem was fixed by those qemu commands. My bluescreens wasnt just random. I couldnt even boot into install media fully without those commands.
  13. I haven't had need to improve vnc performance as it is better than what i would even need so i don't have anything on that, sorry.
  14. I think that qxl in unraid and qxl inside VM are completely separate thing. Like qxl in unraid connects straight to KVM engine and not to the OS. And when you installed that package inside VM it distrupted the connection somehow. For fixing it you could try to boot into install media mount disks like in guide, chroot to /mnt and remove that qxl package.
  15. Thanks! Had those ucode thigys other way around and missed rest of comment
  16. Updated this to use Q35-5.0 and systemd-boot
  17. Well.. nothing else comes to my mind than double checking that virtualizion is enabled in bios (SVM Mode and SR-IOV). GPU is in own IOMMU group and trying again fresh with new windows installation and hoping it gets passed trough.
  18. Did you do that hexeditor thing where you remove nvflash part of that vbios?
  19. yeah that guide is 4 years old. It doesn't give you full vbios. Like i tried that with my card and it gave vbios of size ~100kb and gpuz gives 250kb. That vbios what you get from unraid console works on archlinux for me but wont do anything on windows VM.
  20. You mean that when you have that GPU in other windows computer you cant dump it from GPU-Z?
  21. Your latest xml post doesnt have rom included. My example <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/vbios/gt1030-gpuz.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev>
  22. I made guide for passing through my 1030 with 3700x for windows 10 today. Maybe it has something to help you.
  23. Hi. Here is how i did it with official drivers. My setup. Unraid 6.9.0-beta30 AMD 3700x / GT1030 ASUS TUF B550M PLUS / BIOS:0805 / AGESA combo V2 PI Latest bios with AGESA combo V2 PI did not work. got same error43 with it. Requirements. 1. Dumped vbios rom with GPUZ and removed nvflash header with hexeditor. I had to dump mine even though techpowerup had exact model but i have 2 years newer revision. Guide for making that dump: 2. Having your GPU in own IOMMU group Info about that: My example at Tools>System Devices IOMMU group 18: [1022:43ea] 03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea [10de:1d01] 04:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1) [10de:0fb8] 04:00.1 Audio device: NVIDIA Corporation GP108 High Definition Audio Controller (rev a1) 3. UEFI / BIOS Settings: Have virtualizion enabled in bios and other setting to help separating IOMMU groups. My example. Tweaker -> Advanced CPU Settings -> SVM Mode -> Enable Settings -> Miscellaneous -> IOMMU -> Enable Settings -> AMD CBS -> ACS Enable -> Enable Settings -> AMD CBS -> Enable AER Cap -> Enable There is also SR-IOV setting somewhere. There is also PCIe ACS override setting in unraid to help separate IOMMU groups. Setting>VM Manager and select advanced view. Installation Create VM: Add VM>Windows 10 CPU Mode: Host Passtrough Machine: Q35-5.x BIOS: OVMF Select OS install ISO. I used Windows 10 1909 version. Download and select Virtio ISO. I used virtio-win-0.1.185.iso. Select suitable disk size. 50G on mine. Graphics as VNC. Uncheck start VM after creation. Create. Edit and change to xml view. Add this under <apic/> tag <ioapic driver='kvm'/> Change hyper-V settings to look like this and add kvm setting after it: <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='1234567890ab'/> </hyperv> <kvm> <hidden state='on'/> </kvm> In my case for ryzen i need to apply fix for bluescreen KERNEL SECURITY CHECK ISSUE. Add this to end of xml between </devices> and </domain> <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,kvm=off,hv_vendor_id=null,topoext=on,invtsc=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vpindex,hv-synic,hv-stimer,hv-reset,hv-frequencies,host-cache-info=on,l3-cache=off,-amd-stibp'/> <qemu:arg value='-machine'/> <qemu:arg value='q35,kernel_irqchip=on'/> </qemu:commandline> As for others you can try these lines if those are enough. <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='host,kvm=off,hv_vendor_id=null'/> <qemu:arg value='-machine'/> <qemu:arg value='q35,kernel_irqchip=on'/> </qemu:commandline> UPDATE Start VM and take VNC connection ASAP to be able to press any key. Select language preferences next and install. I don't have product key (set it after install) Select your windows version. (My case 10 Pro) Accept terms. Custom: Install Windows only (advanced) Load driver>Browse>virtio-win-0.1.185>amd64>w10 Red Hat VirtIO SCSI controller>Next Load driver>Browse>virtio-win-0.1.185>NetKVM>w10>amd64 Red Hat VirtIO Ethernet Adapter>Next (You can add network later after installation also) Select drive and next. Set your personal account and privacy settings You should be at your windows 10 desktop now. Open start menu and type compmgmt.msc and open. Open Device Manager. On my case there are 2 devices without drivers. Right click on driverless device and select update driver>Browse my computer>select whole virtio disk. Enable RDP Write "This PC" on start menu > right click on it > properties From right press "Change settings" > Take note on Full Computer Name > remote tab Check "Allow remote connections" > uncheck tab below it > OK. Test rdp connection to VM. If it doesnt work. Fix it before you continue. Shutdown VM. Edit VM in form view. Press + on VNC selection to add another graphics card. select your GPU and select vbios for your card. select nvidia audio controller as sound card if it is in same IOMMU group. (Optionally select attached KB+mouse) Update Now go back to edit and change to xml view. Add those qemu commandlines again which we did earlier as basic view gets rid of them. Disable VNC by removing <graphics> and </graphics> and everything between them. Same on <video> and </video>. Update. Start VM You should see it boot on attached monitor. Use RDP or kb+mouse to install gpu drivers. I use 399.24 version. Haven't tested on later versions. I get error after installation that there drivers are not suitable but seems to work fine. You should have now Windows 10 VM with gpu passtrough. Hope this helps! Twiikker TROUBLESHOOTING: qemu-system-x86_64: vfio_region_write(0000:04:00.0:region1+0xa8ec8, 0x0,8) failed: Device or resource busy vfio-pci 0000:04:00.0: BAR 1: can't reserve [mem 0xd0000000-0xdfffffff 64bit pref] make this type of script and run everytime array starts or manually run from console. #!/bin/bash echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind