QEMU GPU vfio-pci pass through

@themamboman
You could set the bochs-display to full screen either with Ctrl-Alt-F or with a QEMU command line option so the mouse capture works on the full screen. As for the slowness it was found before but I don't know the reason. You run it with bboot which means the card's BIOS wasn't run so it was only init by the AtomBIOS parsed in the AmigaOS driver. This may be enough but it's possible the card needs to be init first by its BIOS so you could try using pegasos2.rom (then you still need bboot with bboot.fth to fix IRQs and 64bit BARs). Also look in Linux logs for vgaarb logs to make sure the passed through card's VGA ports are selected and not shadowed by some other card (this is what does not work with Intel integrated GPUs) because then the card's BIOS may not correctly run.
To debug the PCIE_CONFIG_SPACE_SIZE assert issue you could run QEMU under gdb (add gdb --args before the QEMU command then start in (gdb) with 'run') then you get a gdb prompt at the assert and can do backtrace to see where this was called. There a few places vfio calls this but I don't know how to fix that, you can try reporting at the QEMU mailing list or bug tracker with the QEMU command, backtrace and the error you get describing how you got the error.

@white
You may want the opposite, not using resizeable BAR with older RX card but make sure it's not using resizable BAR when passed through. One way to make sure is to disable it in BIOS but if your other card needs it this may not work. Consider that AmigaOS is 32 bit so can't access things above 4GB so you have to make sure the passed card can be mapped within the 4GB limit. That's why above 4GB decoding and resizeable BAR options may interfere. You could search for passing through GPUs to 32 bit (older) Windows guests, the problems may be similar with those than with AmigaOS. I don't know much about this so I can't help. I think getting an older RadeonHD card should be less problematic for pass through at first than getting the newest and biggest card AmigaOS can support but you can try it.

Why did you need UAE for AmiStore? Doesn't that run on AOS4 in QEMU too?

@balaton
Thanks for the advice.
Why did you need UAE for AmiStore? Doesn't that run on AOS4 in QEMU too ?

( I couldn't understand the question, sorry )



I accidentally found an answer from Asus three weeks ago

It would be nice in an upcoming BIOS update to enable full IOMMU group separation for B550-Plus mobo.

Asus moderator response:

We apologize for the delayed response due to a public holiday in our region and any inconvenience this may have caused.
We also appreciate your valuable feedback. Currently, the TUF GAMING B550-PLUS only supports the IOMMU setting.
I will forward your feedback to the relevant teams for further evaluation and consideration in future developments.



link Asus:
https://zentalk.asus.com/t5/motherboar ... -iommu-groups/td-p/463136

@white
Quote:
Sorry that was a question for @themamboman who mentioned this in post #58.

Also GPUs usually have two subdevices, one for the HDMI sound part. If these two are in one IOMMU group then you don't need other patches just pass both of them. You only may need kernel patch if your motherboard puts more slots in one IOMMU group but even in that case you can try plugging the card to be passed through in another slot to see if that has different IOMMU group with just the card in it. (If you only have two slots where the card fits then this may not be ideal.)

@white
The tests that did show the screen open were with the XFX RX 580. I have yet to get the Sapphire R9 270X to do anything other than reboot my computer when I launch qemu. It's on the latest firmware as well.

@balaton
I realized that I needed to get Enhancer and AmiStore had it less expensive and I was on my Windows side so I just launched AmigaOS4.1 in WinUAE since I had that set up.

I then copied the files out to USB, rebooted to Linux, copied them out, and rebuilt Kickstart.zip with them in place. Just a convenience thing.

Thanks for the suggestions on using pegasos2.rom. I'll try that next. I thought I had tried it and ran into an issue. I'll update. Thanks for all the help!

@balaton

Just tried using the bboot.fth script.

I had to use rdbtool to create a new disk image and copy over the files to the new drive in order to get the pegasos2.rom bios to see them: (modified slightly from your pegasos2 subpage



when it got to the point I could manually enter commands:



(Doing this without the vfio passthrough parts, and only using -device sm501, it booted okay (just no external graphics.

Switching by removing the sm501 and inserting the vfio devices:


I never get the opportunity to enter the boot command. Here is the output:

@themamboman

I didn't bother asking this question but what is the file
( bboot.fth script ) and where can it be found ?

Thanks

Installed Garuda-Linux Zen kernel on SSD 500gb
No problem installing qemu.
It also has the Nvidia proprietary drivers preinstalled.

Essential version just to use it for qemu.

In fact, unlike for example Ubuntu or PoP-OS or Kali, it immediately recognized my old Wi-Fi adapter TP-Link TL-WN722N V.1 which is now a few years old.

With the other distros I had to first use the ethernet cable and then manually install TP-Link TL-WN722N V.1

But as usual as with other Linux distributions the mouse occasionally freezes or jerks with qemu (AmigaOS 4.1 Pegasos).
Or it does not move entirely on the screen but only up to half.

Obviously this only happens with qemu (AmigaOS 4.1 Pegasos).
Certainly not within the Linux-Garuda Desktop.

This does not happen for example with the qemu version of Windows 10 the mouse works perfectly.

I also tried another simple mouse and it's the same same problem.

So just a note to add to this post.
The mouse I use is this:
GXT 970 that I use without problems with KVM if I emulate other machines.

@white
BBoot and also its README.
For the mouse did you try -display sdl or -display gtk? These may work differently.

@themamboman
I assume you also have -vga none in the command line to disable the default VGA card. Such errors also happen with the QEMU default vgabios which the BIOS emulators in these AmigaNG firmwares cannot run because it has some opcodes that are specific to i386 but these are apparently not emulated in these firmwares. If your card BIOS has the same problem then this could be an issue but maybe it ran enough dispite the errors to init the card. Even if you don't see a prompt you may be able to enter commands. If you see a new error for each keypress it may still work so you can try blindly entering the boot command or to get the prompt on serial try (there needs to be a space after both quotes) to redirect the firmware to serial so you can enter commands there.
If the firmware finds a VGA device it will use that for output and default to serial only if there's no VGA device. The sm501 is not VGA so with -vga none -device sm501 you'd get a prompt on serial. With passed through VGA you would see output on that but if the VGA BIOS does not work there might be no output but you could redirect it to serial with the above command or enter the boot command without seeing the output.
To check what ROM the card is using try 'info qtree' in the QEMU monitor and check that it has rombar=1 and has no romfile. If it's using the QEMU vgabios you may need to add rombar=1 or dump the rom and use that with romfile but I think by default it should use the ROM from the card so could be it has the same issue as the QEMU vgabios and the card is too new for the old BIOS emulator in the pegasos2 firmware.

@balaton

currently this is my syntax:

qemu-system-ppc -M pegasos2 -kernel /home/amigaos/Scaricati/bboot-0.7/bboot -initrd /home/amigaos/Scaricati/Kickstart.zip -vga none -device sm501 -drive if=none,id=cd -m 2048 -device ide-cd,drive=cd,bus=ide.1 -drive if=none,id=hd,file=/home/amigaos/Scaricati/32gb.raw,format=raw -device ide-hd,drive=hd,bus=ide.0 -device rtl8139,netdev=network01 -netdev user,id=network01 -drive if=none,id=hd1,file=/home/amigaos/Scaricati/coffin.raw,format=raw -device ide-hd,drive=hd1,bus=ide.1 -display gtk,zoom-to-fit=on -full-screen

I would like to fix this problem because it makes my tests ineffective.
Your version took work and testing.
And sometimes I hate to report these problems.
But they are there.
And I could dedicate myself to other tests instead of thinking about the mouse.

@white
What if you replace -display gtk with -display sdl?

@balaton

Now I have to go to the vet for the cat

Today I will try SDL but I remember that I had changed SDL to -display gtk
because the videos did not go full screen and if I used Emotion first in full screen and then went back to window Emotion occupied 1/4 of the screen in a disproportionate way and it did not go back to normal this also happened with UAE and other applications.

Anyway today I try again with SDL to be more precise.

MAC systems were immune to this.

@balaton

In summary here I made 2 screenshots
in the first one is with -display SDL or SDL,on
-display sdl,gl=on or (off)
or only
-display sdl
it's the same it doesn't change the result it also opens games like Quake in 4:3 format everything opens in 4:3 with black bands on the sides.

You can notice instead that using GTK the screen opens at the correct resolution 16:9 Emotion Quake etc. etc.

And that's why GTK seems to be the best solution for screen resolution.

We talked about this a long time ago
I would like an opinion from @themamboman since we use similar systems Ryzen 5600 and Ryzen 5800 I imagine he also has this problem.

I hope to find a resolution.
@Balaton
Clearly your opinion is also very important don't misunderstand me maybe in the meantime a solution has been found that I'm not aware of.

With -display SDL
the command:
zoom-to-fit=on -full-screen ( Does Not Work ).

you will be able to notice the black bands if you enlarge the images





@balaton
thanks for the link (bboot)

@themamboman

SDL has been tested as well as GTK with the following cards NVidia:
1060 6gb
rtx 2060 6gb
rtx 4060 8gb

the problems are always the same regardless of the video card.
and from the drivers used over time and from the updated versions of the proprietary NVidia drivers that came out over time.

Would you be so kind as to post me your command line syntax that you used before doing the GPU Passthrough tests.

I assume though that you use RYZEN 5600 and RADEON cards from what I can understand.

Thanks

Time passes inexorably and I would say that I have used AmigaOS in its time. 30 years have passed now.
I will return to the topic of emulation when I see more concrete developments.
So good work to everyone.
In the hope of seeing new developments from everyone.

Today I ordered 2x 16gb ( CORSAIR VENGEANCE RGB PRO 3600MHz 32GB ) they are not the best but they are what I was looking for and for the price paid they are fine.

I can not even say anything about the driver ( sm501 ) after all it was not designed for AmigaOS 4.1 but it was an intuition for emulation.
And it's clear that it has its flaws.

Okay see you soon

Give him the strength to sing your hymns.
He will work until he breaks his back.
He will plow these immense fields.
He will sow and reap the fruits of his labor.
He will cut down woods, build houses and raise livestock.
And when at nightfall he returns to his home destroyed by fatigue, joyful and happy, he will come to your temple to sing your glory, O Lord.
Thank you for having taken our brother back into your flock.
Make him worthy of your mercy and Illuminate his ephemeral existence with the light of his spirit.

"Brother Tobias"



I like to be ironic, who knows if anyone has ever seen this film, they're old now

Sorry for silence. Been super busy on other projects.
So, the suggestion for using bochs-display to be fullscreen to capture mouse worked. At the same time, I noticed my mouse was way more responsive. However, installation of AmigaOS was still very slow. In fact, I didn't get to finish it, I gave up since it was taking so long.

I did swap to another RX 580 that I had (MSI brand), so I'm not sure if this contributed to the better/speedier mouse response. I will try again with a preinstalled Amiga OS4.1FE harddrive image.

I tried SDL and GTK and they were great. I personally am not trying to get the super-fast emulation, I just want to be able to use Warp3D Nova and the CANDI wallpaper apps that need real hardware. I'm also considering an older card like HD 7750 or so to see if those work.

I'll put in my results when that happens.

@themamboman

It would be useful to know if you only use Radeon cards with SDL and GTK or also NVidia cards.
But I guess answers are not your strong point
It takes too much effort probably.

As well as writing your own qemu syntax without GPU Passthrough
you know how it is forums are also for exchanging experiences.

.

Not being a user with real Hardware for AmigaOS.
I do not worry about buying a video card that is compatible with games or with porting like Quake 3 Arena etc.

Using ( qemu ) if I also have to buy the new firmware ( pegasos2 ) it is not a problem.

I would just like to understand if for example an R9 270 2Gb supports 32bit and Composite.

Because my interest is not for games but for the use of the operating system.

Is anyone trying this type of emulation ?
Thanks.

Because maybe I do not understand at what point the emulator is.

or if qemu is no longer developed for various reasons.


Thanks.