m1012000

Members
  • Posts

    4
  • Joined

  • Last visited

m1012000's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Cheers limetech. So i tried as you advised with 0.1.189 and windows updates this on its own made no difference. I then wiped away the entire VM. Reinstalled from fresh with windows 10 pro 2004 media and received update errors. I then wiped away the VM once again and created from fresh once again however this time i went with i440fx-4.0 instead of i440fx-4.2 as i had previously. The VM is working and these are them configurable used: hyper-v enabled, OVMF,USB controller 2.0, vdisk with SATA/RAW. My network card is virtio-net (as i would see a GSO error in logs when using just "virtio"). Along side the VM changes i have append kernel arguments: "vfio-pci.ids=10de:1c02,10de:10f1 video=vesafb:off video=efifb:off". For the GPU vbios i dumped the vbios in another system and removed the nvflash header in a hex editor as per spaceinvader ones youtube guide. I used virtio-win-0.1.189 again for this build and fully updated.This this time my USB audio device and then passing through the GPU was also successful. Before tearing everything down and changing the virtual hardware template i would notice that if i pass through the GPU windows would have no audio outputs (not just the HDMI out but every audio device was missing) and if i stopped passing through the GPU then the USB audio device would automatically appear in outputs working as expected. What the single solution was i am not so sure either the hardware profile from 4.2 to 4.0 or wiping away the windows install completely would be my guess since that VM i had tried passing through the built in HD sound card thats very difficult to get functioning it would seem and may have impacted windows sound for anything else thus why i brought a USB device to then that didn't work either! Thanks for the reply/ help and the complete answer is for anyone else that may get some inspiration on a similar issue since i have spent days at it!
  2. I have found some odd behaviour around the VM piece. So i updated to beta 29 to help resolve many of the issues seen around passing through devices on a AMD Ryzen 3000 based system (3800x, Gigabyte gaming B350 v1). The new kernel changes in the backend fix many of issues seen with that type of build and QEMU meaning i can pass through a 1060 3GB geforce card without a problem. No see code 43 and so is a major step forward. However the audio devices will not passthrough correctly to the windows 10 VM. Under device manager the audio devices show without error installed (geforce audio, amd starship/matisse hd audio controller and a USB based sound device) however under sound and output/input devices it will not show any of them. Doesn't matter if its pci-e or USB based none of these work or result in a usable output device in sounds inputs/outputs. However if i roll back to 6.8.3 then the USB device above instantly works for example. Yet booting/running and passing through a GPU on a Ryzen 3000 based system without "vfio-pci.ids=10de:1c02,10de:10f1 video=vesafb:off video=efifb:off" was working fine. So its really odd its just the audio based devices. I doubt theres a easy fix right now so for now i may revert. Cheers tower-diagnostics-20200930-2101.zip
  3. True, still at least the info is public for future headless users. Monitor or none the choice is there.
  4. I found that most guides on youtube or otherwise blast past using EDID emulators or headless plugs (dongles) for displayport/HDMI. The dongle emulates having a monitor plugged in without the monitor actually being there. All the settings listed above would never be 100% for me personally and i would still get the dreaded code 43. Since i believe Nvidia's drivers/cards seem to look for a monitor being plugged in to stop virtualization on their consumer GPUs. Since using the dongles i have found getting code 43 much less likely or none existent. For me within unraid i use BIOS: OVMF, Machine: i440fx-4.2, Hyper-v: yes, Graphics rom BIOS (dumped from the GPU itself), pass through the Nvidia Audio as well (even if you wont use it). In KVM, Unraid and vmware ESXI i have seen similar behaviour cleared up by using the dongles. I use a Displayport dongle myself on a 1660 3GB but i have seen this work on 1080ti's for example. Here are some examples on amazon (i am in no way affiliated to these sellers or products.): Displayport example: https://www.amazon.co.uk/DP-DisplayPort-emulator-Headless-2560x1600/dp/B071LQHQMV/ref=asc_df_B071LQHQMV/?tag=googshopuk-21&linkCode=df0&hvadid=217971167670&hvpos=&hvnetw=g&hvrand=17762952164112151129&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=1007016&hvtargid=pla-412706487727&psc=1 HDMI example: https://www.amazon.co.uk/Headless-Display-Emulator-Headless-1920x1080-generation/dp/B06XT1Z9TF