onyxdrew

Yeah when I was screwing around my system reset the cmos settings as one time I locked it up... I had thought I had saved teh profile but it doesn't appear to have worked. I'm burned out of it for now, will pick it up again next week maybe. Not sure why the updated QEMU would have much impact either?

No output, updated driver with Windows Update instead of downloading from AMD.com... back to good-ole error 43

Just installed windows fresh again to be sure, and here it is after all the Windows updates:

Next step woudl be revert my USB stick back to 6.9.2, I did take a backup... see if it truly would just work again with that version of QEMU/etc.

Yeah, my point is that you never got output, and maybe never used the version of the driver I was using? Not sure if I ever got the bios messages/etc or if the VM would only display after it got Windows started, I never paid attention to that. No, it showed up as the same AMD device the whole time. I noticed It was good to go in Device Manager right before I installed driver. I might start over and not install any driver and see what it does.

I wonder if its related to the AMD GPU drivers? I downloaded the latest, you might have as well, maybe I was on a slightly older version before? The GPU only shows error 43 after driver install.

I tried using my dumped bios, GPU shows up, but still 43 error with Windows... Interesting fact, Win 11 will boot even with error 43 on GPU, Win 10 does not.

I also haven't touched my bios since I installed the 5700G. There is one newer version but unrelated changes.

dmesg doesn't update, but syslog shows this: May 18 17:50:00 UNRAID kernel: vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x19@0x270 May 18 17:50:00 UNRAID kernel: vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x1b@0x2d0 May 18 17:50:00 UNRAID kernel: vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x25@0x400 May 18 17:50:00 UNRAID kernel: vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x26@0x410 May 18 17:50:00 UNRAID kernel: vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x27@0x440

Nevermind, I found it... 9/24 just like yours:

Nope, I cannot get it to do anything on HDMI output since upgrade. I installed Windows about 100 times today getting fresh starts on new VMs to try different approaches, nothing worked. I tried to get the bios dumped directly from my chip, and was unsuccessful with that too. GPUZ doesn't work, nor does Space Invadors process, nor SIV. I tried it in Windows 11 and Windows 10. Its frustrating how hard this is, when it seems like it should just work. If I had to do it again, I would probably have tried to go with Intel instead of AMD... but I already had the x570 board.

What version of VIRTIO was everyone else using? Maybe that's part of the key? I didn't record which one I was on when things were working, but pretty sure it was virtio-win-0.1.190-1.iso Maybe one of the drivers I loaded as part of that was key? I just tried a new Win10 VM with 190 and it still didn't work though.

Also the latest VIRTIO drivers I cannot get it to let me install the entire package, I have to deselect a few items to make it not fail and roll back installation. I did try going back to my previous version of VIRTIO as well with Win10 to make the VM exactly how it was working in 6.9.2.

Maybe there is a step I did before that I'm missing now, but at least with the new release 6.10 I cannot get any config to boot and work with APU. I tried exactly how I had it with Q35-5.1, I tried the latest Q35.6-2 as well as i440fx-6.2. I tried Seabios like before, I tried Win 11 with on QVMF-TPM, nothing working now at all, fresh OS load each time. It's crazy how temperamental this stuff is, good thing I pretty much gave up on this being an actual usable thing, as even when it worked, the performance wasn't good enough.

FYI, I upgraded to 6.10.0 last night, and my VM no longer boots. Even without the GPU attached Windows BSOD and says inaccessible boot device. I'm going to rebuild today on Windows 11 I think and try that.