@flash
Haven't read all of the Forth in your script but looking at case 5 I see -initrd which is a QEMU option and does not work from Pegasos firmware. From Forth you should call bboot.fth not bboot which then loads bboot and Kickstart.zip but if you don't have those on hd:0 then you also have to replace that to the right partition in bboot.fth. This is documented in the BBoot README. So it should probably just be

5 of " /pci/ide/disk@0,0:0 bboot.fth" endof

@AmigaNG
Quote:
Yes, -vga none disables the default VGA which does not work with AmigaOS and -device sm501 adds the sm501 which is functionally the same as sm502 that's found on sam460ex so AmigaOS has a driver for it but it's only on the Sam460EX install CD so has to be added manually for other machines. BBoot loads modules from the file specified in -initrd which is Kickstart.zip so the driver needs to be added there. All AmigaOS boot loaders read Kicklayout file from Kickstart dir to find what to load so only copying a file there is not enough it also has to be added to Kicklayout as described on my page.

Kyvos should do that so unless you somehow replaced the Kickstart.zip I don't know how could you break it. Or maybe you managed to get Kyvos generate a Kickstart.zip before you had the siliconmotion502 driver lha then it did not regenerate it when you downloaded that. Maybe delete the whole VM and start again now that you have all needed files.

@AmigaNG
Quote:
You also need to add it to Kicklayout, just adding the file won't load it. BBoot prints what it loads so you can check if siliconmotion502.chip was in the list.

Quote:
Only needed for AmigaOS versions before 4.1FE (i.e. original 4.1) the final edition should have new enough PCIGraphics.card version.

Quote:
Maybe haven't read the right documentation. I've tried to make navigation easier by adding links at the top on my page. Go to https://qmiga.codeberg.page/ (in my signature in all my posts). Select OS and machine you want to run which should take you to AmigaOS section where there's a link saying See separate page describing the easiest way to install AmigaOS using BBoot Then just read that page and follow what's written there. I've already linked to this page above but you read a different page with a more complex older method (which should also work but the newer BBoot way is simpler).

@Mlehto
Quote:
Have you read my summary on this link (also linked from https://qmiga.codeberg.page/#faq the last one about gfx emulation)? The virtio-gpu does not emulate any real GPU but is designed to efficiently communicate between guest and host to pass 3D operations from the guest (which needs a guest driver to talk to this device). Then on the host side these commands are passed on to a 3D renderer that uses the hosts's 3D API. As QEMU runs on the host as an application, it uses the host's drivers like any other app but the guest sees a virtio-gpu-pci card which it has to drive with its own driver but it does not need to know about the real GPU on the host.

Quote:
As the guest driver only passes the commands to the host and does not do any rendering it should be comparable to a passed through GPU or even faster if it avoids the limitations that we currently have with passed through GPUs. The amount of work to talk to a virtio-gpu is about the same as to drive a real GPU as it works quite similarly. The difference is that the commands are not executed by a dedicated real GPU but sent to the host so it can share the host's GPU with other apps and does not need a dedicated GPU or drivers for that GPU in the guest.

@n3m3
As I said I never tried 3D so don't know much about it but if I remember correctly there was a picture about AmigaOS 3D stuff somewhere (in one of sailor's articles on intuitionbase) that listed what libraries are related to what. I'd suggest to find that guide and picture about 3D on AmigaOS to try to make sense of the mess of libraries and drivers. I think there are multiple 3D APIs and different apps need different ones so may need to enable software rendering differently for those to use without a GPU. In any case you won't get hardware accelerated 3D on QEMU unless you use a passed through GPU or with virtio-gpu in the future if there will be a driver for that. You can run 3D apps but need software rendering enabled version. For Warp3D apps Wazp3D can do that, I have no idea on 3DNova or GLES or whatever else is there.

@AmigaNG
Quote:
Maybe within the directory you gave for the VM (or what Kyvos selects automatically, I don't know how it works, never tried)? But I'd look for it where other files like disk images are.

@n3m3
I have never tried 3D but AFAIK Wazp3D is a software renderer compatible to Warp3D so you can use that already with sm501 and it should work for simpler 3D games (it's slower being software and running in the emulated guest). Some people tested Wazp3D in the past and should work. The virtio-gpu driver would give hardware accelerated 3D using the host's GPU so that should work better for games that need that. Or if your host is Linux and can use vfio-pci passthrough you can already get hardware accelerated 3D by passing through a card that AmigaOS supports (certain Radeon models) which also works today as tested by others. So the virtio-gpu would add ability to use the hosts GPU for 3D without needing a separate card for the guest (even if that GPU has no AmigaOS driver such as NVidia) but that's not ready yet as said above or better 2D than possible with sm501 (more colors and maybe some 2D accel but sm501 also has some of that) which is ready but unreleased so nobody can use it yet other than beta testers who got it. Therefore you're maybe not missing much yet until the 3D part is ready.

@afxgroup
Thanks!

@AmigaNG
Do you have the siliconmotion502.chip driver in Kickstart.zip?

@afxgroup
Does anybody have this documentation? It would help improving the emulation in QEMU.

@Mlehto
I think it should work on all targets as virtio-gpu-pci is an emulated graphics card in QEMU that you can add to any machine (the same way as you can add sm501 for example). You just need a driver in the guest to use it. AFAIK from posts here Hans developed it on pegasos2 so that and amigaone should work but I think sam460ex too should have no problem. Only issue is that we need the driver (and maybe an updated pegasos2 kernel if that did not make it in the last update) released which does not seem to happen for a while and no info on when this might happen. Hans said above that he's working on 3D so that's not ready yet, maybe they are waiting for that to be finished before releasing the driver, even if the current version already supports 2D probably better than sm501 (at least it has 32 bit depth) so that might be useful in itself, maybe as a light version included in the OS like the RadeonHD 2D only version on the install CD.

@dwolfman
I don't know what Kyvos does but if it follows the steps written in my docs page at this link that only takes the updated kernel for the siliconmotion502.chip driver to run to be able to install from the CD that does not have the SM502 driver on the amigaone/pegasos2 versions (the sam460ex does not need this step as that already has the SM502 driver on the CD). After installing AmigaOS you still need to install the updates and then regenerate the Kickstart.zip from the updated Kickstart directory from the VM to reach the newest version. Kyvos probably can't do this because it can't install the update in the VM and the Kickstart.zip should match the version on the harddisk or CD that you boot from so these should be updated together otherwise the CD might not boot with updated Kickstart. First install update in the VM then make new Kickstart.zip from the updated system before rebooting it and use that afterwards and do this after each update that changes Kickstart files (you may need to re-add the siliconmotion502.chip driver to Kicklayout if it's removed by the update so check that first before making a zip). I don't know how much of this Kyvos can automate but maybe it only uses the update for the initial Kickstart creation so the only new file you should see there is the kernel.

@walkero
Quote:
I think it was a stripped down Linux distro with MacOnLinux for Pegasos: this here (there may be other versions). I have never tried if it works but if you want to run MacOS on QEMU maybe go to emaculation.com instead and install MacOS on mac99 which may run better (we even enabled SMP for it but that's not in upstream QEMU and does not help AmigaOS or MorphOS anyway). So I don't know how molk would be generally usful other than historical peculiarity. It may be overkill to add it to Kyvos just so you can try it once or do you have a use for it other than it would be cool to see it running?
By the way if you want more users you may consider adding MacOS and MacOSX support and announce it on emaculation.com, they might be interested in a QEMU GUI too.

@n3m3
And what is your problem exactly and how to reproduce that so others could try if it works on their machine or not? Does using -audiodev sdl instead of alsa helps at all? (I don't know how to do that on Kyvos but you can either edit config or run QEMU from a script.)

@NinjaCyborg
There's a link in my signature but that seems to have some issues currently. The longer version of that is http://zero.eik.bme.hu/~balaton/qemu/amiga/

@NinjaCyborg
Unless your MacBook Pro has a compatible AMD/ATI graphics card you can pass through to the guest or you can connect one to it this won't work. The vfio-pci pass through needs a graphics card to assign to the guest.

@n3m3
A faster machine would definitely help. If you don't want to try to find what causes the issues you see and tweak it more then there's not much else to do. Trying different audio backends or ES1370 instead of via-ac97 might still worth a try and compiling QEMU with additional optimisation could help a bit but maybe not much. I think pulsaudio/pipewire can add latency but should not produce choppy sound but I haven't tested that. Plain ALSA with latest QEMU or jack should have lower latency and may work better. You can also try tweaking the sound buffer options as shown above by Mlehto and see if that helps. It also depends on what you play sound with in AmigaOS so does this happen with all sound or just the app you want to use?

@smarkusg
It might be difficult to give one number to check if your machine is fast enough because it also depends on what you want to do with it. It might be fast enough e.g. for software development which isn't time critical (the compilation would take longer but succeeds and you can use it on a laptop) but not fast enough to run a game or other time critical stuff. It also depends if the time critical app is using more FPU or software rendering or can do with integer only. Kinda like is A1222 fast enough? Depends on what you run on it.

@NinjaCyborg
That's MorphOS that ties license to specific machine. AmigaOS license is for one copy of the software not tied to specific machine so I think it could be transferred but it's tied to the registration of the serial so once somebody registered it they have it and there's no way (I know of) to transfer it to somebody else. So people who bought machines which are now non-functional may still have a license but they don't use it and cannot sell it. But the license is also for specific AmigaOS versions so if you have an amigaone or pegasos2 license it's only for that version.

@NinjaCyborg
Quote:
I did without Kyvos but I think several others also did successfully run it. Have you seen other posts on this forum?
Quote:
It may not be the fastest on a 10+ year old machine (especially if you got the slower i5 version of that) but for simple things it should work.