qemu amigaos 4.1 sudo without no audio

@white
Quote:
Only if your monitor have multiple inputs or you use a monitor switcher because the two GPUs have their own outputs so you'll need to plug them somewhere to see their picture. You have two machines: your host and the virtual machine that now uses it's own graphics card so you need two monitors to view the output of two machines or any other way you would use to view two machines. That's why it's called a virtual machine, because it's like a real one just lives inside the host machine and not a physical one.

I think the QEMU_AUDIO_* env variables were removed in later QEMU versions and won't work in current version regardless of what ChatGPT told you. To configure audio backend in QEMU now you have to use the -audio option but that's not normally needed. If you haven't set any QEMU_AUDIO variables then they aren't there. You can check with set | grep QEMU and if that returns nothing then it's some other env variable needed by pipewire that needs to be preserved for sudo.

Edit: Here's the commit that removed QEMU_AUDIO_DRV almost 2 years ago.

.

.

@white
Quote:
Apparently you did not understand the explanation. How would you make a video on one machine of the monitor of another machine? So this won't work the way you might think. You would either need to make video on the guest but vokoscreenNG does not run there or maybe you need a video capture card where you plug the guest's GPU so you can view it on the host in a window then you can make a video of that. Remember that you have two separate machines with their own video cards. Forget that one of these is a virtual machine in the host, it still behaves like a separate machine.
Quote:
I don't even understand that. You can't use a single monitor with vfio-pci as the guest uses a dedicated GPU different from the GPU of the host. I doubt you did that with FS-UAE as it can't use vfio pass through of real GPU as far as I know. The only way to use a single monitor is to use separate inputs on the monitor and you then can switch between the two machines but can't view them on the same screen (unless your monitor does picture in picture but you can't record that).

.

@white
Did your monitor come with a manual? Maybe try reading that. As I said think of it like having two machines each with their own graphics card. You can connect two machines to this monitor and then you can view one of them by selecting the input you want to watch. Some monitors can even show multiple inputs at the same time often called picture in picture but that only happens in the monitor so you can't record that in the host that way.
You get lost because you're not specifying your goal clearly. Is your goal to view both machines on one monitor (then a monitor with multiple inputs will do but you can only view one at a time) or view both without having to switch on the same screen (then a monitor that can show multiple inputs is needed) or is it to record the guest (in that case you need to digitise the output of the virtual machine and show that on the host so you need a capture card in the host for that).

.

.

@white
Quote:
So ChatGPT suggested this but it can't explain why? Can it even tell you what the opion does or where it got it from? It looks like ChatGPT managed to help you by chance and not because of any intelligence. The 'set | grep QEMU' verified that you have no enviroment variables related to QEMU so this has nothing to do with QEMU_AUDIO_DRV mentioned by ChatGPT. Also all the other env variables it mentioned are irrelevant. Pipewire or Pulseaudio or whatever your distro uses may depend on some environment variables though to know where and how to connect and these are not preserved in sudo unless using this option. I don't know which variables may those be but one of the lot printed by the 'set' command without |grep. And it's not '--preserve-env qemu-ppc' but 'sudo --preserve-env' as it's an option to sudo, the qemu-system-ppc is another argument to sudo here which is the command to run.

.

@white
If you only use the Radeon card for AmigaOS then you don't need drivers for it on the host. To be able to pass it through to the guest, it has to be unbound from host drivers and assigned to vfio-pci driver so the host won't use it anyway and the drivers are blacklisted to not load before vfio-pci, so it does not matter if they are installed or not. That driver won't be used anyway, but better not to install them at all, just to make sure they won't interfere with vfio-pci. So no, you don't need Radeon drivers for Linux.

I don't understand what is your problem. You said your monitor has 2 HDMI inputs (and some others). Can't you just plug in both cards in different inputs and select which one to view in the monitor's menu? It's documented in the monitors manual and if you search for it there are other detailed docs on how to do this so why do you make your life more complicated with additional switch box? But if the cats need it or you find your life too boring otherwise then it's up to you.

.

.

.

.

@white
If the Radeon card is assigned to vfio-pci driver there should be nothing displayed on it until QEMU starts. Do you do the vfio-pci setup in some script running when you log in or how can you get picture on it when you don't even have drivers for it installed on the host? If you set up the modprobe config as I described it on my vfio page there should be no picture on the Radeon card from the host as it's assigned to vfio-pci from the start. If the bootup during BIOS/UEFI happens on that card then there could be an option in the setup to change that or you can swap the cards until you get your primary display on the NVidia card.
The bochs-display is just to get mouse and keyboard input in case you don't pass through those to guest but you will not get output on the host in any way. The guest is using the Radeon card and outputs via that, the host is using the NVidia card and outputs via that. You have two separate outputs which you can view on a single monitor if you plug both into inputs on that monitor and then you can switch between them on the monitor.

@white
Quote:Not sure if I understand your problem, but it sounds like
- BIOS/UEFI, and probably Linux text mode, is running on the Radeon.
- Linux gfx mode uses the Nvidia. -> You have to switch monitors, or the input on a single monitor with 2 HDMI inputs in the monitor menu.
- QEmu uses the Radeon. -> You have to switch monitors, or the input source on a single monitor with 2 inputs, again.
If that's correct check your BIOS/UEFI settings and change it to use the Nvidia instead of the Radeon.
If that doesn't work for some reason physically swap the gfx cards between the 2 PCIe slots and the BIOS/UEFI should use the other one.

.

@white
If you don't want to use Linux, except for running QEmu, why not simply start QEmu automatically?
That way you have the BIOS and QEmu output on the same (Radeon) monitor and can even leave the Nvidia HDMI cable unconnected.
There would still be some Linux output on the Nvidia before QEmu is started, but nothing you need to see.

That's basically what @smarkusg did, check Project - hardware to run AOS4 for 35 euro on QEMU 10 + GPU passthrough.

.