What the fastest possible x64 emulation way of OS4 today ?

@redfox

Thank you with all my heart.
I have spent the last 8 years every moment with her.
And this counted as if we had spent our entire lives together.

I left all work and projects
Our projects together.

She just fell asleep she didn't notice anything.
Because she was sleeping she was only 24 hours in a center for this type of treatment.

And like when we wake up in the morning we realize that we are there.
Otherwise we wouldn't realize it if we never woke up again.

I don't want to add more to this.
Now everything I see is turned off for me from the sky to the meadows and everything in between.

But I'm not angry with people, on the contrary I'm more open but I notice that people are always in a hurry who knows what they'll have to do.

Living simply is the most beautiful thing.

And I've been volunteering for a long time and this helps me somehow
but if I see that a person is better then I'm happy.

And when it's my turn, I'll think of her

In the end she told me enjoy your life because you are not immortal.
She was braver than me.

My thoughts on this end here. Thank you


Today I will switch everything to SSD if I can, so Qemu accesses the partition directly.

It should work as with WinUAE "x76" and then "hide" to initialize the disk.

I want to see if the speed increases.
And then with TrueImage I do the backup so you can restore it very quickly.

@white

Ciao Paolo ecco perchè non vedevo più i tuoi aggiornamenti di stato su whatsapp, credimi se ti dico che eravate bellissimi!
Non lo sapevo e sto apprendendo solo ora, mi dispiace moltissimo sentite condoglianze.
Un abbraccio forte forte.

@flash
Dino grazie molte.

Solved the problem of the external Ip andress now I can get a real IP that can be reached by Ping the Scans for example with NMap nmap -p 22 192.168.80.1 now they work and port 22 is open it is reachable.

So the problem for AmiCygnix I still don't understand what it is because now the problem of the EXPORT DISPLAY remains
doing 192.168.80.1:0.0 tells me that it can't open the display even though now the authentication succeeds without problems.

qemu:

qemu-system-ppc -cpu max -cpu 7447 -smp 1,sockets=1,cores=1,threads=1 -L pc-bios -M pegasos2 -bios /home/white/Scaricati/pegasos2.rom -m 1024 -serial stdio -device sm501 -drive if=none,id=hd,file=/home/white/Scaricati/16gb.raw,format=raw -device ide-hd,drive=hd,bus=ide.1 -device rtl8139,netdev=vmnet8 -netdev user,id=vmnet8 -nodefaults -display sdl,gl=on -vga none

I used VMnet8 drivers directly from VMWare as with WinUAE
(( in this case the version of VMWare for linux ))

There is no need to issue any additional commands before using qemu.

above the command line.

Unlike tap0 the connection is very fast without any "LAG" it is instantaneous.

Always use a static IP for example:
192.168.80.1
255.255.255.0
192.168.80.1
192.168.80.1

and you will get an external IP address without any error.

Unfortunately it doesn't work with RTL8029 but only with RTL8139.
So probably qemu side there are some problems with RTL8029.

A small note:
With AmyCygnix I use the RTL8029 driver to make it work. (winuae)

Here again a short benchmark with Lame Wave to mp3 10MB and Quake Timedemo3 to compare.





@white

I'm afraid I can't help you with that, I still don't understand what you're doing all this for?

Is it to get a faster internet connection or to stream YouTube videos lossless under AmigaOs4.1?

Otherwise I have now found a way to transfer my data from the host to the guest system. The whole thing works with smb2, it is logged in like a harddisk under AmigaOs4.1.

@Maijestro

It makes me laugh,
Maybe I can't make myself understood

I leave you 2 links maybe you can try:
indeed perhaps only you can try
https://eschwan.home.ktk.de/amiga/AmiCygnix.php?lang=en
http://os4depot.net/index.php?function=search&tool=simple


Then by default you get an IP address that looks like this 10.0.2.15 if you use RTL8139 in emulation this IP is behind an emulated router that you can't handle in emulation as a real external IP address.
You have to try it on AmigaOS it is useless to use other systems because it is useless to test with other systems.

With AmiCygnix you can use for example "Firefox" not "TimberWolf" but the latest version of Firefox for example the one used in Linux you can also use "WaterFox" and many other applications installed on Linux like FFPlay Gedit with the Linux Terminal to do many other things.
You basically use AmigaOS but you can use applications written for Linux.

To do this with AmigaOS in emulation you need to have a real external IP.

Also Amicygnix itself has standalone applications like "Gimp" and other applications to use them you don't need an external IP for that.

And a standalone X11.

Now there is this solution on:
http://zero.eik.bme.hu/~balaton/qemu/amiga/

ZBalaton wrote it after I talked to him about it:

How to set up QEMU networking
The simplest is to use the slip/user networking which can be enabled as e.g. -netdev user,id=net0 -device rtl8139,netdev=net0 (see the QEMU docs for more information). If you want to access services on the guest, ports can be forwarded with the hostfwd option.
For more advanced setups the tap networking can be used which is like a virtual network cable connecting a tap device on the host to the emulated card in the guest. This needs some setup on the host machine first. On Linux you can create a tap device as root (set username to your user name, otherwise QEMU needs to run as root):

# ip tuntap add user <username> mode tap
# ip link set tap0 up
# ip addr add 192.168.0.1/24 dev tap0

Then you can attach a virtual network card to that tap interface as -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -device ne2k_pci,netdev=net0 and set an IP address (i.e. 192.168.0.2) in the guest (adjust these IP addresses as needed). Then you can communicate between host and guest or set up routing on the host. Alternatively, instead of assigning IP addresses you can create a bridge on the host and add the tap device to that to allow the guest to access the same physical network the host is attached to as if it were a real machine.

This solution is not perfect based on my tests on AmigaOS
There are some lags that I couldn't get past.

Having an external IP is not needed to have a faster connection.
The speed is the same now with "vmnet8"

It is used to use AmiCygnix and use Linux applications directly on AmigaOS.

Now I make a video
I thought I had managed to explain myself.

Clearly the users of this forum know what I'm talking about.
But they are able to use it because they are not using an emulation.

(( But the test must be done in emulation like all the other tests done in emulation ))

However I'm more and more convinced that it's the graphics driver currently used by qemu
which fails to open the screen on AmiCygnix.

because if I do :
export DISPLAY=:0

all applications show up on the linux screen without any problem.

but when i try to export DISPLAY=IP-AMIGA:0.0

everything works, the sound is heard but nothing is displayed on the screen.

As for the 4.1 Qemu emulation, it's simply extraordinary.

All the applications I'm using work very well.

And the first time I can see Youtube videos without shots directly using Odyssey without YT for example.

E-UAE works perfectly

In short, a great job.

Clearly still missing support for an ATI card
But now it's really fast including TwitchTV and everything.

@whiteQuote:

The screen output of 16 bit brings of course very many restrictions, but I am glad that was already helped e.g. with MilkyTacker this works now with the new SDL2 under Qemu Pegasos 2 AmigaOs4.1. I had seen it earlier in one of your videos that you had to patch it. Maybe ScummVM will run soon too....

Quote:

I agree with you the Qemu Pegasos 2 is a really very powerful emulation, I have a lot of fun with them and opening windows ,programs ,tool is really very fast.

Quote:

Hans de Ruiter could probably be the only one to help, he has driven the graphics driver development on the AmigaOs4.1, but it will not be in his interest to support an emulation. I think he will concentrate on real hardware since he is also working with A-EON. But you never know maybe one day something like this will be included in the Enhancer package 2.x I'm dreaming again

@white

I have something for you, you may want to test it. smarkusg has compiled ffmpeg with libshine and libmp3lame under AmigaOs4.1. It is not FPU dependent and should be very fast.

ffmpeg

Message to Hyperion/A-Eon

Consider a special OS4 or extended driver version for QEMU Peg2 virtual board, I’m quite sure you’ll sell many thousand pieces if price is low.
Support Zoltan Balaton in developing QEMU virtual boards.
My2cents.

@flash

Or perhaps there are ways to target qemu in a more direct way so that less specific hardware needs to be emulated (like peg2, audio hardware or specific gfx cards).

An OS4 qemu native edition if you will.

@Maijestro

I've done a quick test of that version on real hardware.
It seems it lacks amigaos path handling and doesn't like the ":" in a path.

But it's cool to see latest version of softs on our systems ;)

@Petrol

I could ask him if he would compile it with all the dependencies. He chose the easiest way, it is only for testing purposes to improve the Qemu FPU emulation. Since this version makes no use of the FPU it is of course incredibly fast compared to the version of Os4Depot under Qemu AmigaOs4.1, but certainly on real hardware like AmigaOne x1000 x5000 it should run much better.

@Maijestro

I was doing some tests because I have old virtual hd that I used with winuae and therefore without support for voodoo3.

If you have the AmigaOS Final Edition 53.71 Classic cd
replace in your Pegasos2 ISO:

these files:
diskcache.library.kmod
SmartFilesystem

in kickstart:
now you should be using SFS for OS4.

Test and let me know, you'll probably have to install from scratch.
To try, create a small virtual hd so you let me know.

It seems to me that everything is faster.

I also tried -cpu 7447A brings the CPU to revision 1.2
instead of 1.1. always with the same speed apparently.

Let me know maybe it's helpful.

CPU speed* instructions L1 cache L2 cache
601 60-120 MHz 3 per cycle 32 KB external to 1 MB
603 75-160 MHz 2 per cycle 2x8 KB
603e 100-300 MHz 2 per cycle 2x16 KB
604 100-180 MHz 4 per cycle 2x16 KB external to 1 MB
604e 166-233 MHz 6 per cycle 2x32 KB external to 1 MB
604ev 250-350 MHz 6 per cycle 2x32 KB external to 1 MB
G3/750 200-450 MHz 3 per cycle 2x32 KB external to 1 MB
750CX 366-466 MHz 3 per cycle 2x32 KB 256 MB onboard
750CXe 400-700 MHz 3 per cycle 2x32 KB 256 MB onboard
750FX 600-900 MHz 3 per cycle 2x32 KB 512 MB onboard
750GX 733-1100 MHz 3 per cycle 2x32 KB 1024 MB onboard
G4/7400 350-600 MHz 19 per cycle+ 2x32 KB supports 2 MB L2 cache
7410 466-533 MHz 20 per cycle+ 2x32 KB supports 1 MB L2 cache
7450 667-733 MHz 20 per cycle+ 2x32 KB 256 KB onboard, up to 2 MB L3
7455 600-1420 MHz 20 per cycle+ 2x32 KB 256 KB onboard, up to 2 MB L3
7447A 600-1500 MHz 20 per cycle+ 2x32 KB 512 KB onboard, no L3 cache
7457 867-1267 MHz 20 per cycle+ 2x32 KB 512 KB onboard, up to 4 MB L3
7457 used in some third-party Mac upgrades, never by Apple
7448 1.0-1.7 GHz 20 per cycle+ 2x32 KB 1024 KB onboard, no L3 cache

@white

I'm not sure what this test is good for, SFS already works very well under my system. I installed the last version of Enhancer Software 2.2.

It is of course possible that the enhancer version accesses other routines that do not exist under Qemu.

Tonight I will test the Classic version under Qemu and test read and write access.

Thanks for the information.

@white

Apparently -cpu 7457 under Qemu is the best choice at the moment, I did some tests with Lame and Quake timedemo. With Lame test and -cpu 7457 I first get 20 seconds decoding, that's really remarkable, with Quake timedemo I'm not far from 30 FPS software rendering that's impressive. Also this CPU is fully supported under AmigaOs4.1 Ranger/Altivec etc.

Unfortunately I don't have a comparison with WinUae, but it will probably be much slower.

Also with the SFS version of the Classic Edition I could not see any difference to the version of Enhancer.

Is there a good tool for AmigaOs 4.1 to test read and write accesses?

Lame G4 Test




Quake Timedemo

@Maijestro
Yesterday I did a test to install SFS. I used the one that comes with OS4.1 FE Pegasos version and worked fine. Of course, I needed to have a small FFS partition for the amigaboot.of. But the system boots from the SFS just fine.

My biggest issue still is the RTL8139, which haven't solved yet, no matter if I use an older device.

@walkero

We need to be able to reproduce it somehow to be able to improve it, as already mentioned here it works very well. I also don't know your hardware configuration, since you are developing under AmigaOs4.1 we can actually exclude a faulty setup of the network under AmigaOs4.1.

Someone with a real Pegasos 2 and a rtl8139 network card could possibly help and maybe confirm that the driver causes problems under AmigaOs4.1, but someone with such a configuration will be hard to find.

Otherwise we would have to start debugging it to solve the problem.

@Maijestro
Thank you for your reply

Quote:

I have an internet connection and browsing websites with IBrowse works quite well. But if I stream online radio with AmigaAmp then the network card halts after a few seconds. This seems to be a problem with Qemu because even if I restart OS4 this problem remains.

Quote:

Yes

Quote:

Yes, and I have the same behaviour.

Quote:



Quote:

I use the final as released from Manjaro repo.

Quote:

Latest Linux Manjaro

Quote:

Why this would be necessary?

Quote:

Are you able to stream online radio or video just fine?

I will continue searching for a solution. I am glad that emulated OS4 environments are getting better and better.

@walkeroQuote:

hmm strange I have no problems with the internet and streaming. I made you a little video it works very well here at the moment.

@walkero

We could investigate the problem further, but we would need someone running a real Pegasos 2 with an rtl8139 network card to rule out the driver under AmigaOs4.1, but finding this configuration will be very difficult.

Otherwise the only way is to debug it via Qemu to get more information.