sudo chmod 777 /run/user/$(id -u)/pulse/native && qemu-system-ppc -M amigaone -bios /home/white/Scaricati/Silicon/u-boot-amigaone.bin -device VGA,romfile=/home/white/Scaricati/Silicon/VGABIOS-lgpl-latest.bin -m 2048 -serial stdio -vga none -device sm501 -device rtl8139,netdev=mynet0 -netdev user,id=mynet0 -drive media=disk,format=raw,file=/home/white/Scaricati/Silicon/Update2-ONE-32gb.raw
Just add : && for those who have audio issues like me.
in the place of ;
Now I'll add the GPU back and try GPU pass-through.
As long as it works

Then I'll improve it.
I've already got everything ready

sudo chmod 777 /run/user/$(id -u)/pulse/native && qemu-system-ppc -M amigaone -m 2048 -bios /home/white/Scaricati/u-boot-amigaone.bin -serial stdio -drive media=disk,format=raw,file=/home/white/Scaricati/Silicon/Update2-ONE-32gb.raw -netdev user,id=net -device rtl8139,netdev=net -vga none -device vfio-pci,host=06:00.0,bus=pci.0,x-vga=on,multifunction=on -device vfio-pci,host=06:00.1,bus=pci.0 -device bochs-display,romfile=""
Response from CHAT-GPT:
Yes, the command you suggested should work correctly even with the && operator. Using && ensures that the second command is executed only if the first command (chmod) was successful.
The structure you wrote is correct, so if you want to run the two commands consecutively, here's what it might look like:
sudo chmod 777 /run/user/$(id -u)/pulse/native && qemu-system-ppc -M amigaone -m 2048 -bios /home/white/Scaricati/u-boot-amigaone.bin -serial stdio -drive media=disk,format=raw,file=/home/white/Scaricati/Silicon/Update2-ONE-32gb.raw -netdev user,id=net -device rtl8139,netdev=net -vga none -device vfio-pci,host=06:00.0,bus=pci.0,x-vga=on,multifunction=on -device vfio-pci,host=06:00.1,bus=pci.0 -device bochs-display,romfile=""
Additional details:
The chmod command sets the permissions for the /run/user/$(id -u)/pulse/native folder to 777, so anyone can read, write, and execute.
The qemu-system-ppc command starts a PPC (PowerPC) virtual machine with specific BIOS, network, and video configurations, and other PCI devices via vfio-pci.
Make sure that:
The vfio-pci devices are configured correctly and that access to the PCI devices (06:00.0 and 06:00.1) is authorized.
The /run/user/$(id -u)/pulse/native folder is accessible by your user, and that 777 permissions are appropriate for your use case.
If the commands are structured correctly and the system is configured to use vfio-pci and network devices, everything should work as expected.