Mirai Misaka

Im happy to report that the issue seems to be fixed, at least sort of. I just tried it last week again and was kinda supprised that the win10 VM (I440fx)(Driver:Quadro 511.65 Typ DCH) just installed the driver and worked. On a Win 11 VM on Q-35 i had to install the driver manuelly, worked but crashed every like 20 minutes. not sure if that was because of the vm type: Q35 or if the vm was just broke, stopped woking completly after a bit of testing soooo... new win11 vm on I440fx and everything works perfekt for days. so i deem this as fixed, not sure if unraid changed something or MS / Nvidia. But im happy now, hope this helps others that had the same issue. (Everything on 6.10-RC2)

Hi @jonp, i tried Installing the Windows VM from scratch, still got the same Code 43 error. i tried different Q35 and i440fx versions, and both BIOS versions. (on sea bios no GPU at all, not the 620 and not the 1650, vnc was fine), used a fresh Iso for win 10 and the latest Virt io drivers (virtio-win-0.1.208-1.iso)and lastest drivers, both the normal and Quadro driver from Nvidia but found that i could not install the virt io drivers on qemu 6.1 (both on i440fx and q35), needed that change to 4.2, installation worked fine there and switched back to 6.1 but tried of course 4.2 and even 2.4 as well, all the same issue in the end: p620 code 43 and the 1650 worked fine except sea bios. the 1650 is the primary GPU, i use a script that runs on startup to make it work for vm's 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 but use that since ages and always worked. TBH: i settled to use the 620 just for plex, works fine for that and don't have that much time to work on this issue anyway, would still like to solve it, not just for me (having options is always nice) but also for other people that might run into the same issue but its not a high priority for me any more. (there is still the possibility that my GPU itself has a wired bug, because otherwise way more people would have the same issue, but it did work in any other use case and machine) Of course if anyone has a suggestion on what I could try, I will gladly do it but that might take some time, the RL keeps rolling… But thank you all for your time and help

i updated the BIOS, that is always a good idea but unfortunatly that did not solve the issue, (Quadro driver 472.39 but works with the 1650 without issue) I also tried to set the Pcie gen but im not sure if my Mainboard let me even do this, could at least not find the option for that. But it should be Gen 3 anyway AFAIK. I setteld on using the P620 for plex Transcoding, does a fine job there, but would like to use it as an display output as well. The GTX1650 works fine with and without the Bios dump file on all vm's p620 does not have an Vbios dump file The 1650 is on the primary slot and the P620 on the secondary, if i replace it with an old gt710, it works fine on that slot. i will attach an updated diagnostic just in case there is something usefull in it Thank you all for your time and recommandations hiiragi-diagnostics-20211108-2111.zip

tryed again with rc2 today, same issue, and also with using Q35-4.2

Okay little update An other User did had trouble getting his 1030 to work in a vm on 6.10-rc1. But it was his first time setting up a vm so that does not really mean anything. Because I wondered if maybe the GPU architecture is the problem I replaced the GT710 with a GTX1080ti in 6.10-rc1 the 1080ti just worked fine, every time. 620 still c43 I went back to 6.9.2 and 620 did work again, then I tired something different and I know I may should have wrote the earlier but the driver that I use is the geforce driver, because the P620 did always work fine with it. After I encountered the 620 c43 in 6.10-rc1 I tried to reinstall the driver and I tried the proper quadro one (471.41) no matter how often I tried to install the quadro driver it did not work. With the 1080ti as soon windows saw it, it loaded the geforce driver anyway but when I install the quadro driver (471.41) in 6.9.2 on the p620 and update to 6.10-rc1 it does work!!! Multiple reboots of the vm and the p620 did work fine with the vm that was on quadro drivers before the update to 6.10-rc1 booted the vm with the 1080ti, windows switched back to the geforce driver (471.68), 1080ti=fine Back on the p620 and it was on c43 again. Was not able to install the quadro driver again restored to 6.9.2 first boot of vm with both gpu’s in did shut down after a few second on its own. Second boot of vm, was fine. Both gpus worked fine and were automatically on the geforce driver 471.68

i was able to recreate the problem. i first checked the GPU again, its fine: after the i took my main PC apart and tested it with a separate stick, first on 6.10-rc1 and after it from 6.9.2 this time i got issues on both, that was not the exact same as i was having on my real server. then i deleted everything on the test machine again and started from 6.9.0, brought the vm to post with that p620 and worked my way up from there. i think the new QEMU version is causing this, but i'm not sure: i will post my "test report" here for more details what i did, maybe that does help the devs save some time: and sorry for typos etc. it really late... test with separate system: all drives removed just on empty 1TB NVME for array and USB stick for boot of unraid 2 gpu's primary slot GT710 secondary P620 first test new stick directly with 6.10-rc1 non UEFI GT710 worked, p620 did not, no display output, when paired together with the GT710 it did boot up on the GT710 and Showed the P620 with Code 43. erased the stick (not ssd) and put 6.9.2 on it, Same issue, did manage to bring the P620 online with deinstalling it together with driver in Device Manager. but after vm restart P620 was code 43 again, that trick did not work twice. marked the p620 in system devices together with its sound part and binded to vfio, rebooted, no effect --------------------------------------- Erased the stick again but this time on 6.9.0 with UEFI and secure erased the SSD. there are 2 gpu's in the system (primary slot GT710 and Secondary P620, both with displays attached to them) unraid always chooses the P620 as primary GPU. if i try to start the vm on the primary GPU i got a messed up display on that. back in the day i had that error as well, fixed it it with the following command: 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 i did put it on the User script plugin (aside of APPS the only installed plugin during testing) if triggers, primary GPU can function without problems. Vm under P620 booted 5 times without any issue. (had a minor issue with the P620 during testing on 6.9.0, did just select the GPU itself and not the Sound card. Result: first vm boot was fine, after it, GPU didn't trigger on vm boot. added the Sound card of the GPU and all was fine after that) -------------------------------------------- updated to 6.9.2: Works as 6.9.0. When primary GPU is used without the script: log fills up with: "Aug 10 22:43:49 Tower kernel: vfio-pci 0000:24:00.0: BAR 1: can't reserve [mem 0xc0000000-0xcfffffff 64bit pref]" both gpu's the same, most likely did that as well on 6.9.0 so i hues known issue: Vm under P620 booted 5 times without any issue. script is set to auto on start up of array (like on Main server) tested safe mode boot, no gui,no plugins: Passed reboot and Vm boot test again: passed everything normal -------------------------------------------- updated to 6.10-RC1 set Password, didn't log in, VM tab reads Libvirt service Failed to start. did log in into my servers. vm tab still dead restart array, vm tab still dead found issue, stopped array, enabled users shares and start array back up, vm tab is back vm boot on 620, vm did boot but issue is back that gpu is showing display output but locked to 600×800 P620 is back at c43 vm does boot up with 620 every time but always locked to 600×800 code 43 unlike direct testing of 6.10-rc1 in non uefi mode, there was no display output what so ever disabled trigger for script on startup, and reboot issue is like on 6.9.2, error log fill up and screen is messed up. re- anabled script trigger and reboot vm boot up like before 600×800 stopped vm's deleted libvirt and re setup the vm now the network driver is gone removed the virt io drivers and reinstalled them vm reboot, network back up but gpu is not deinstalled gpu in device manager with drivers and reinstalled it, no change ------------------------------------------- restored to 6.9.2 login screen is still like 6.10-rc1 pw the same tried to start vm: Execution error: unsupported configuration: Emulator '/usr/local/sbin/qemu' does not support machine type 'pc-i440fx-6.0' deleted libvirt re setup vm vm on P620 works normal vm booted fine multiple times QEMU version the problem? ----------------------------------- back to 6.10-rc1 boot vm, again gpu locked at 600×800 code 43 changed machine in the vm tab to i440fx-6.0 (from5.1) no change still c43 changed to q35-6.0 internal error: Bus 0 must be PCI for integrated PIIX3 USB or IDE controllers ! Not valid! created new vm wit q35-6.0 same issue changed first vm to i440fx-5.0 same issue done for today