@miggymac

Thanks for the tips,
if you have time
and you want to try "browservice"
https://github.com/ttalvitie/browservice

here you can already find the image for raspberry
with "browservice" preconfigured at startup.

https://www.mediafire.com/file/bu9ksr6 ... bian_Browservice.rar/file


here is the tool for the sdcard if necessary
https://www.raspberrypi.com/software/

add :
wpa_supplicant.conf
in the same directory:
example:

country=IT
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid=""
scan_ssid=1
psk=""
key_mgmt=WPA-PSK
}

Instead
on your old operating system with outdated browser.

example manual
IP
192.168.0.14
mask
255.255.255.0

type from your old browser (Odyssey)

192.168.0.15:8080
or
192.168.0.15:8080/goto/google.it
or
192.168.0.15:8080/goto/youtube.it

clearly it is ONLY if you feel like testing it out of curiosity.

I don't take responsibility

you can use the ethernet cable or wifi (depends on the model).

Thanks again for your suggestion.
I appreciate it

@All

My topic is OT
but it is related to qemu emulation for AmigaOS 4.1

Does anyone know how the exact command line to emulate a RaspBerry
Pi or Pi2 with "qemu"

I would need it to create a dedicated "browservice".

Thank you.

@all

I changed Linux distribution
nothing in particular
but I like it and I also don't have to disable the Nvidia Nouveau drivers because the distribution already has the drivers being installed.
even if in the end there are just a few steps to do.
And few things installed
Ideal for me who only use it for qemu.
I just had to add the packages to compile qemu including the annoying "meson"

And light and I notice that it is faster than "kali"
Also now I can compile directly from the qemu master branch.
Without mistakes.

Other than that the idea of creating a sharing directory was a simple additional option.

With the ramdisk configuration I thought it was possible to choose a "raw" filesystem but I couldn't find anything on the subject although there is certainly something out there to read.

Now qemu no longer gives the "floating point" error
But if I try to initialize the ramdisk it tells me that it cannot initialize RDB "0"

It would also be fine in fat32 for sharing or some compatible format.
But it doesn't matter it was just something more to add.

On the other hand, why not try it when it takes a few minutes to restore the Linux backup, it costs nothing and is fun

Thanks for all the suggestions.

Since I'm here I wanted to ask if "aiostrems" still works for you and twitchTV doesn't seem to work for me anymore.
While YT.rexx works fine.

This is the distro I'm using:
https://pop.system76.com/

@balaton
once again thank you for your work.

I'll write it here if it might be found interesting by others too
otherwise it's not important.

sudo mkdir -p /media/ramdisk
sudo mount -t tmpfs -o size=2048M tmpfs /media/ramdisk

sudo fdisk -l
we obtain:

/dev/ram0

then we add:
-drive format=raw,file=/dev/ram0

è "hdtoolbox" recognizes the new "virtual partition created with the ramdisk" ready to be initialized

at that point "qemu" comes out giving me the error:
"floating point error"

Not knowing AmigaOS I really don't know if it is possible to manage this type of volume by mounting them in other ways

Or if there is some utility in AmigaOS that can handle all this.

If anyone finds it interesting, we could look into it further.

by modifying "fstab" it can be made permanent or simply the volume disappears upon reboot.

@Maijestro

the ideal would be to find a way with qemu to share a directory with linux for exchanging files on the fly.

using only qemu
something similar could be done by mounting a "shared virtual hd"
always with a similar command for example:

-drive format=raw,file=/dev/sdd2

I did it some time ago with a program similar to this:

http://radeonramdisk.com/software_downloads.php

It worked well and was very fast
I had put the entire AmigaOS 4.1 Classic directly into "RAM"
WinUAE

it was very fast

But it could be done with a shared virtual-hd without using RAM.

But I don't remember the exact command I used in qemu 3.1 version

With "Browservice" the page is displayed correctly with Odyssey.

now I'm trying the new "sdl" maybe with a bit of luck it works "UAE" it already works with the -7447 cpu but it's not perfect
with some betas who wrote "kas1e" is "FlynnTheAvatar"
but at the moment they only work with an 8bit screen
waiting for a 32bit video driver but that will take time.

And I don't think they want to adapt it for 16bit screens.
and if it is possible

but I'm the one doing something wrong
every time I have to download "sdl" if I use Odyssey or "IBrowse"
the page is not displayed correctly to download the latest "sdl" version
And I have to use "firefox linux or windows" every time to download the file and then import it in the form of "iso" to be able to install the sdl file.

It seems strange to me that the file is not accessible with the Amiga Browser given that it is a file for the Amiga.

under the ASSETS heading the field is empty to be able to download the file with Odyssey or IBrowse

Does it happen to you too ?

@balaton

Yes it is exactly as you described.
That's why I had to give chmod 777 every time

at every reboot to access the AmigaOS partition
and the qemu command line didn't work normally.

so in summary
better a completely dedicated SSD in case you want to opt for this choice.

@joerg

Let me explain better but I repeat this has been happening for many years also with Workbench 3.1 but I had forgotten.

I use GParted
Main partition "Linux ext4"
Extended partition "left unformatted" or directly using the "Amiga" partition create function with Gparted"
All perfect .

Well if I go to format the partition to make it go back to being an "ext4" partition everything will seem normal.
But in reality the AmigaOS (SFS) system is always present even after formatting the partition with GParted again in "ext4"
In practice, the only way to permanently delete AmigaOS from the disk is to recreate a new partition table in "ext4" of the entire disk.

"does not create new partition"
but the disk must be completely reinitialized with a new "partition table"

but it's nothing important anyway.

but the proof is that if you try to move files it will tell you that the partition is full even though GParted clearly shows that the partition is empty because it has just been formatted.

@Maijestro

I read about the improvements

I have to go back to AmigaONE again.
I had a problem with the latest kernel released for Linux.
Even though I've solved it now.
As I had already mentioned previously.
I still can't compile the version of qemu on the official site.

So I continue to compile from the "balaton" channel and everything works.

So I'll be back to try AmigaONE again.

I also noticed that using the SSD with AmigaOS there are some problems.

In practice, if I create both the "ext4" partition and the SFS partition dedicated to AmigaOS on the same SSD, for some reason it seems that the two filesystems create problems for the "partition table"
If used on the same disc, but this is nothing new, it also happened a long time ago.
Even with 3.xx somehow even if you format a partition previously used with SFS it creates problems.
You need to completely recreate the "partition table"
Otherwise SFS seems somehow "immune" to formatting.
He continues to be present all the same.

Even after formatting with another filesystem.
Maybe "joerg" could answer this.

simplified explanation
format everything goes fine (ext4)
but if I use qemu I use that partition
AmigaOs is still present although it obviously shouldn't be like this because the partition has been formatted.


So the ideal use is to have 2 separate disks, one entirely dedicated to "Linux" and another only for "AmigaOS". In this case there will be no problems.

here is an example in .py
for creating a .hdf (raw)

#!/usr/bin/env python3

"""
Copyright 2021 Tiago Epifanio

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
"""

import getopt
import sys
import re
import math

ABOUT_TEXT = '\
HDF Create v0.1\n\
Copyright 2021 Tiago Epifanio\n\
\n\
Licensed under the Apache License, Version 2.0 (the "License");\n\
you may not use this file except in compliance with the License.\n\
You may obtain a copy of the License at\n\
\n\
http://www.apache.org/licenses/LICENSE-2.0\n\
\n\
Unless required by applicable law or agreed to in writing, software\n\
distributed under the License is distributed on an "AS IS" BASIS,\n\
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n\
See the License for the specific language governing permissions and\n\
limitations under the License.\n\
'

HELP = '\
HDF Create v0.1\n\
Copyright 2021 Tiago Epifanio\n\
This is free software, and you are welcome to redistribute it\n\
under certain conditions; type \'python3 hdfcreate --about\' for details.\n\n\
Usage: python3 hdfcreate.py [OPTIONS]\n\n\
Options:\n\
-t, --type TYPE\n\
TYPE: raw (Single partition)\n\
rdb (Partitionable Hard Drive Image)\n\
-s, --size SYZE\n\
-f, --filename\n\
-h, --help\n\n\
Example 1 - create a single partition file with 32GiB:\n\
python3 hdfcreate.py --type raw --size 32G --filename myhd.hdf\n\n\
Example 1 - create a partitionable hard drive with 512MiB:\n\
python3 hdfcreate.py --type rdb --size 512M --filename myhd.hdf\n\
'

DISK_TYPE_RAW = "raw"
DISK_TYPE_RDB = "rdb"
DISK_TYPES = [DISK_TYPE_RAW,DISK_TYPE_RDB]

def create_disk(size, filename = "out.hdf", disktype = "raw"):
if disktype not in DISK_TYPES:
print("Invalid type. Valid types are: raw, rdb.")

size_regex = re.compile('(\d+)([bkmgBKMG]{0,1}$)')

m = size_regex.match(size)

if m:
size = int(m.group(1))
unit = m.group(2)
else:
print("Invalid size.")
sys.exit(1)

if (unit in ("k","K")):
size *= 1024
elif (unit in ("m","M")):
size *= 1024 * 1024
elif (unit in ("g","G")):
size *= 1024 * 1024 * 1024

try:
f = open(filename, "wb")
except Exception:
print("Error opening file.")
sys.exit(1)

if (disktype == DISK_TYPE_RDB):
size = size - 4
f.write(b"rdsk")

blocksize = 1024 * 1024 * 10; #10MiB
written = 0

for i in range(0, size // (blocksize)):
f.write(b"\0" * blocksize)
written += blocksize
print("\rProgress: " + str(math.floor(written / size * 100)) + "%",end='',flush=True)

f.write(b"\0" * (size % blocksize))

print("\rProgress: 100%")
def main(argv):
if len(argv) == 0:
print(HELP)
sys.exit(1)

disktype = None
size = None
filename = None

try:
opts, args = getopt.getopt(argv[0:],"t:s:f:h",["type=","size=","filename=","about","help"])
except getopt.GetoptError:
print(HELP)
sys.exit(1)

for opt, arg in opts:
if opt in ("-t", "--type"):
disktype = arg
elif opt in ("-s", "--size"):
size = arg
elif opt in ("-f", "--filename"):
filename = arg
elif opt in ("-h", "--help"):
print(HELP)
sys.exit(1)
elif opt in ("--about"):
print(ABOUT_TEXT)
sys.exit(1)

if size is None:
print("Size not specified. Use -s parameter to specify size.")
sys.exit(1)

create_disk(size, filename, disktype)

if __name__ == "__main__":
try:
main(sys.argv[1:])
except Exception as ex:
print('Error: ' + str(ex))

Once you have chosen how to build your distribution and related dependencies for qemu etc.

and having a stable repository to refer to for qemu updates (for updates dedicated to the evolution of qemu for AmigaOS)
this is a practically already complete start menu.

Scripts for creating hdf and everything else have also been added here.

It works perfectly in this case with FS-UAE

With a little work you can boot graphics animations and everything else.

menu.sh
----------------

#!/bin/bash
trap '' 2
sudo /usr/bin/setfont /usr/share/consolefonts/Lat7-Terminus24x16.psf
function Amiga500() {
echo ""
echo "Loading Amiga 500 Setup..."
startx /usr/bin/fs-uae -c /amiga/Configurations/amiga500.fs-uae --fullscreen > /dev/null 2>&1 &
echo ""
tput reset
}

function Amiga1200() {
echo ""
echo "Loading Amiga 1200 Setup..."
echo ""
startx /usr/bin/fs-uae -c /amiga/Configurations/amiga1200.fs-uae --fullscreen > /dev/null 2>&1 &
echo ""
tput reset
}

function Amiga3000() {
echo ""
echo "Loading Amiga 3000 Setup..."
echo ""
startx /usr/bin/fs-uae -c /amiga/Configurations/amiga3000.fs-uae --fullscreen > /dev/null 2>&1 &
echo ""
tput reset
}

function Amiga4000() {
echo ""
echo "Loading Amiga 4000 Setup..."
echo ""
startx /usr/bin/fs-uae -c /amiga/Configurations/amiga4000.fs-uae --fullscreen > /dev/null 2>&1 &
echo ""
tput reset
}

function Amiga400041() {
echo ""
echo "Loading Amiga 4000 OS 4.1 Setup..."
echo ""
cd /home/amiga/fs-uae3.2
startx ./fs-uae -c /amiga/Configurations/A4000-PPC.fs-uae --fullscreen > /dev/null 2>&1 &
echo ""
tput reset
}

function Arosm68k() {
echo ""
echo "Loading Aros M68K Setup..."
echo ""
startx /usr/bin/fs-uae -c /amiga/Configurations/AROS-One.fs-uae --fullscreen > /dev/null 2>&1 &
echo ""
tput reset
}

function FS-Launch() {
echo ""
echo "Loading FS-UAE-Launcher..."
echo ""
startx /usr/bin/fs-uae-launcher > /dev/null 2>&1 &
echo ""
tput reset
}


##
# Color Variables
##
green='\e[32m'
blue='\e[34m'
clear='\e[0m'
yellow='\033[0;33m'

##
# Color Functions
##

ColorGreen(){
echo -ne $green$1$clear
}
ColorBlue(){
echo -ne $blue$1$clear
}

ColorYellow(){
echo -ne $yellow$1$clear
}

menu(){
tput reset
echo -ne ""
echo -ne "My ip address is: "; hostname -I | cut -f1 -d' '
echo -ne "
AmiDeb Menu (V1.0)

$(ColorGreen '1)') Basic Amiga 500/2000 Setup
$(ColorGreen '2)') Basic Amiga 1200 Setup
$(ColorGreen '3)') Amiga 3000 Setup
$(ColorGreen '4)') Amiga 4000 Setup
$(ColorGreen '5)') Amiga 4000 OS 4.1 Setup
$(ColorGreen '6)') Aros One M68K
$(ColorGreen '7)') FS-Uae Launcher

$(ColorGreen 'u)') Utilities Menu

Choose an option: "
read a
case $a in
1) Amiga500 ; menu ;;
2) Amiga1200 ; menu ;;
3) Amiga3000 ; menu ;;
4) Amiga4000 ; menu ;;
5) Amiga400041 ; menu ;;
6) Arosm68k ; menu ;;
7) FS-Launch ; menu ;;
u) configmenu ; menu ;;
*) echo -e $red"Wrong option."$clear; tput reset;menu;;
esac
}

configmenu(){
tput reset
echo -ne ""
echo -ne "My ip address is: "; hostname -I | cut -f1 -d' '
echo -ne "

AmiDeb Utilities Menu

$(ColorYellow '0)') Shutdown System
$(ColorYellow '1)') Reboot System
$(ColorYellow '2)') Apt Update
$(ColorYellow '3)') Apt Upgrade
$(ColorYellow '4)') Apt Dist Upgrade
$(ColorYellow '5)') Start command shell
$(ColorYellow '6)') Edit WIFI/Network Connection
$(ColorYellow '7)') Create 1Gb HDF File (1G.hdf)
$(ColorYellow '8)') Create 2Gb HDF File (2G.hdf)

$(ColorGreen 'q)') Quit to AmiDeb Main Menu

Choose an option: "
read a
case $a in
0) sudo /usr/sbin/shutdown -h now ;;
1) sudo /usr/sbin/shutdown -r now ;;
2) sudo apt-get update ; configmenu ;;
3) sudo apt-get upgrade ; configmenu ;;
4) sudo apt-get dist-upgrade ; configmenu ;;
5) sudo -u amiga -s ; configmenu ;;
6) sudo nmtui ; configmenu ;;
7) sudo -u amiga python3 /home/amiga/hdfcreate.py -t rdb -s 1G -f /amiga/'Hard Drives'/1G.hdf ; configmenu ;;
8) sudo -u amiga python3 /home/amiga/hdfcreate.py -t rdb -s 2G -f /amiga/'Hard Drives'/2G.hdf ; configmenu ;;
q) menu ;;
*) echo -e $red"Wrong option."$clear; tput reset;menu;;
esac
}

# Call the menu function
menu
----------------------------------

then possibly all the reference scripts follow.

@balaton
Here's an account that resembles what happens to me
data 13 September 2023.

https://www.mail-archive.com/qemu-devel@nongnu.org/msg988673.html

@balaton

Thank you
but I don't know how to do it,
I never reported any errors.
if not to say it directly to you.

I use qemu as a simple user

note:
I imagine that as soon as the Windows x64 version is compiled the same error will happen.

@balaton

I tried the various options
down to the simple:
./configure --target-list=ppc-softmmu

the problem remains (qemu 8.1.1)

the only option that works is not giving the error:
qemu-system-ppc: ../ui/console.c:818: dpy_get_ui_info: "dpy_ui_info_supported(con)" assertion failed.
zsh: IOT instruction qemu-system-ppc -M pegasos2 -cpu 750cxe -accel tcg -kernel -initrd -m 2048


this,
it doesn't return any errors but I've never seen the point of using it:

qemu-system-ppc -M pegasos2 -cpu 750cxe -accel tcg -kernel /home/white/Downloads/bboot-0.4/bboot -initrd /home/white/Downloads/Kickstart.zip -m 2048 -serial stdio -device sm501 -netdev user, id=mynet0 -device rtl8139,netdev=mynet0 -drive format=raw,file=/dev/sdf -display sdl,gl=on -device virtio-gpu-gl-pci -vga none

I'll go back to using the branch:
git clone http://scm.osdn.net/gitroot/qmiga/qemu.git

@balaton

this is the error that appears with the official version (8.1.1)

I compiled as per the branch version:
git clone http://scm.osdn.net/gitroot/qmiga/qemu.git

but in this case:
git clone https://gitlab.com/qemu-project/qemu.git

Then:
./configure --target-list=ppc-softmmu --disable-dbus-display --enable-slirp --enable-lto --enable-sdl --enable-gtk

here is the error:

qemu-system-ppc: ../ui/console.c:818: dpy_get_ui_info: "dpy_ui_info_supported(con)" assertion failed.
zsh: IOT instruction qemu-system-ppc -M pegasos2 -cpu 750cxe -accel tcg -kernel -initrd -m 2048

--------------------------------------------------------------

with "qemu":
qemu-system-ppc -M pegasos2 -cpu 750cxe -accel tcg -kernel /home/white/Downloads/bboot-0.4/bboot -initrd /home/white/Downloads/Kickstart.zip -m 2048 -serial stdio -device sm501 - drive if=none,id=hd,file=/home/white/Scaricati/32gb.raw,format=raw -device ide-hd,drive=hd,bus=ide.1 -netdev user,id=mynet0 -device rtl8139 ,netdev=mynet0 -drive if=none,id=hd1,file=/home/white/Scaricati/coffin.raw,format=raw -device ide-hd,drive=hd1,bus=ide.1 -display gtk,zoom -to-fit=on -full-screen -vga none

without using a real HD for example.

@balaton

I also compiled the latest version of qemu
official (8.1.1).
Without problems.

But if I use emulation it gives me a series of errors.
And qemu doesn't work with Pegasos2
So I went back to the branch
git clone http://scm.osdn.net/gitroot/qmiga/qemu.git

If necessary, I'll recompile qemu 8.1.1 and I can be more precise.
Showing the error.

If it's useful.

@Maijestro

Today I wanted to test it

I used an old HD connecting it via USB
dedicating it completely to the Amiga.

So without using the SSD as an extended partition.

Just to see if everything worked.

Because I would like to get a small SSD so as to dedicate it completely for "qemu".

Doing:
create new partition table with "Gparted" you can directly choose "Amiga".

@Maijestro
How did you measure HD speed with AmigaOS ?

I tried "Disk Speed" on OSdepot
but it doesn't work for me.

It doesn't give me any speed and no tests start



This way, I can assign its ID to put in "fstab"
so as not to change its path at every restart.

@balaton
so it would be interesting to know
what would be the right settings that could be used
with the SFS/02 file system with an SSD disk

based on current emulation with qemu
it is its emulation of a real hard disk

always if in emulation a real disk
can be exploited efficiently
also maybe in the next versions of qemu (AmigaOS Pegasos2)
taking this into account.

or if this is already enclosed in qemu currently.

@Maijestro

No problem, I'm always happy to answer you.
Actually there are many ways to backup.
I use this one it's the simplest

You have to use "Dopus"
Download the version on "OSDepot"

And replace it with "Original Dopus" if you haven't already

Now that you use Real-HD you don't need WinUAE.

This is a practical example of how you should do it:

qemu-system-ppc -M pegasos2 -accel tcg -kernel /home/white/Downloads/bboot-0.4/bboot -initrd /home/white/Downloads/Kickstart.zip -m 2048 -serial stdio -device sm501 -netdev user, id=mynet0 -device rtl8139,netdev=mynet0 -vga none -cdrom /home/white/Scaricati/Pegasos2InstallCD-53.54.iso -drive if=none,id=hd,file=/home/white/Scaricati/32gb.raw, format=raw -device ide-hd,drive=hd,bus=ide.1 -drive format=raw,file=/dev/sdd2 -display gtk,zoom-to-fit=on -full-screen

boot from the Pegasos2 CD

use the right sequence as above

Simply prepare your REAL-HD with your partitions the same size or larger.
As you always have with HDToolBox
BOOT DH0 etc etc.
But don't install anything.
Only format the partitions as you have them in your virtual .RAW files

And copy with Dopus all the original partitions from your .RAW file for example into the HD-REAL partitions

If you have split the partitions into multiple .RAW files
always boot from CD and copy everything you need to copy to your "REAL" partitions

When you're done and you know everything is OK.
So you copied everything.

Start normally simple example:

qemu-system-ppc -M pegasos2 -accel tcg -kernel /home/white/Downloads/bboot-0.4/bboot -initrd /home/white/Downloads/Kickstart.zip -m 2048 -serial stdio -device sm501 -netdev user, id=mynet0 -device rtl8139,netdev=mynet0 -vga none -drive format=raw,file=/dev/sdd2 -display gtk,zoom-to-fit=on -full-screen


If you have problems I'll make a video for you to see.

Later you can always use Dopus to make backups if you are comfortable with it.

But I use TrueImage to backup real partitions, I can split I have only the Amiga-Real partition or Linux too together.
The recovery time is 5 minutes.
--------------------------------------

You can give me a screenshot as soon as you can

Of your SFS/02 HDToolBox settings
used blocks and masks of the filesystem file hexadecimal transfer.

I saw the ASCII file before booting AmigaOS in your video
but has the version of boot-0.4 been updated ?
--------------------------------------
@smarkusg
I would like to have your configuration file if possible of E-UAE for 3.2.
Although I will most likely use 3.1 because it is very fast.
But I would like to try it.

@balaton

you're right about pulse-audio had nothing to do with it

I solved it in a spartan way like this for now:
sudo fdisk -l

Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 2048 370204671 370202624 176.5G 83 Linux
/dev/sdd2 370204672 488396799 118192128 56.4G 1b Hidden W95 FAT32

Then:
sudo chmod -R 777 /dev/sdd2

and then:

qemu-system-ppc -M pegasos2 -accel tcg -kernel /home/white/Downloads/bboot-0.4/bboot -initrd /home/white/Downloads/Kickstart.zip -m 2048 -serial stdio -device sm501 -netdev user, id=mynet0 -device rtl8139,netdev=mynet0 -vga none -cdrom /home/white/Scaricati/AmigaOneInstallCD-53.54.iso -drive format=raw,file=/dev/sdd2

now the audio works and I don't need "root"

Now I'm moving everything to SSD and doing audio tests etc.

I need help assigning the right HARD-DISK (SSD) ID

with qemu from the command line

because every time I restart Linux the HARD-DISK (SSD) mount point can change.

so before using qemu

I have to see with:

sudo fdisk -l

/dev/sdd2

if it is changed for example with:

/dev/sde2

and redo:
sudo chmod -R 777 /dev/sde2

I think the right solution is the disk ID so as not to always repeat everything from scratch.


If I understand correctly, then once I have this information I can add it to:
/etc/fstab

Thank you.

@All
my problem is not creating a partition
I've been preparing real partitions for use with WinUAE for years.

My problem is "pulse-audio"

I currently use "kali" which I am comfortable with.
And light and configurable.
I eliminate the tools that I don't need and it lends itself to many modifications.

Now there are some X64 distributions that have "pulse-audio" in multi-user by default.

Can anyone recommend a distribution for X64 that doesn't have this problem related to pulse-audio ?

Any distribution is fine.
Just don't have this problem with "pulse-audio"

It takes 10 minutes to install a distribution and update it and install the dependencies needed by qemu.
Because I'm using Linux just for this.

Request ? (for qemu)
What Linux x64 distribution do you use that doesn't have the pulse-audio problem ?
And are you using a real hd ?

or is this guide useful for this purpose ?

https://linuxconfig.org/how-to-enable- ... ts-on-pulseaudio-in-linux