Kyvos was updated

@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.

thanks for the reply - links would be useful. The machine is a top of the line i7.

@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/

@balaton

Thanks will check it out. I'm interested in booting into either a nice clean linux like elementary OS, or even a headless one like tiny linux and having it launch straight into OS4, with an option to also fire up a container with a UAE instance in it.

I am delighted to inform you that I just released a new version of Kyvos, with the following changes:

## 1.6.0 [2025-10-16]
### Added
- Added pid files to be saved in the .kyvos folder. This will be set on VM creation or update
- Added support for the "AmigaOS4.1 FinalEdition Update 3", if that is available (optional). Kyvos is looking for a file named "AmigaOS4.1FinalEditionUpdate3.lha". If that exists in the same folder as the AmigaOS 4.1 FE ISO, then it will be used when the kickstart.zip file is created.

### Changed
- Enabled the virtio-gpu options for Sam460 systems. This driver is not coming with Kyvos
- Changed old pidfile arguments to be saved to the ./kyvos folder under HOME

This can be found at https://ko-fi.com/s/6476fdadd2

@walkero

If you're interested, yesterday I released the new version of AROS One 64Bit. If you wish, you can add it to Kyvos.

Here you will find information and download links for AROS One 1.2 64Bit.

https://www.arosworld.org/infusions/fo ... d=1418&pid=9724#post_9724

@walkero

a couple of suggests (may be are already there)
1. would be useful, if possible to set, to have a button with the boot priority. I better explain, if I add a bootable CD in the media it automatically want to have the boot from it while in certain cases would be necessary to boot from the HD and have the CD just mounted.
2. the path of the VM is showed but can't be changed.

@AMIGASYSTEM
I will have a look into that. Thank you for your continuous work.

@ilbarbax
Thank you so much for you suggestions. Please have a look at my answers below.

1. Unfortunately, I haven't found a way to set boot priorities that it actually works. Whenever the AmigaOS ISO is used, it boots from that. It might be a limitation of using bboot, but I can be completely wrong on that.

2. In general, the path should not change. But if you move it somewhere else, you need to set up a new VM using the Advanced method and set everything based on the new place. But I will note that as a feature for a later release. At least to make it easier for the users. How crucial is it for you?

@walkero

thanks for your reply.
Concerning the VM path it is a not relevant need, simply I created all my emulations using a certain path, when created the OS4 one I forgot to change it so it remained kyvos. I wanted to uniform this set up with the others. I can regenerate a new VM correctly.

Another issue I got is that on my real Sam I have two hd one for os4 and the second for mos, I can see the mos hd from os4 and vice versa. Here I tried to load the mos hd img under os4 emulation using the 2nd hd or third hd but they are not mounted

@walkero

(1.6.0 released)

Awesome! I've been trying to manually update the kickstart.zip and so far all I get is the "guest hasn't initialized the screen" when I try it.

Looks like I'll have to make another A1 instance, then copy the new kickstart.zip over from it to my main entry.

A suggestion for future versions would be to have a button show somewhere to re-run that kickstart.zip creation process on an existing instance.

And once again I can't get the ko-fi site to work properly. Every so often, I go through the checkout process, only to have it hang and spin forever at the last step before it gives me the links to get the files.

And this time it's worse. Once before I got it to work by logging out of ko-fi, then back in. Now, I can't get logged in, it just sits there saying "logging in" after entering my email/password and clicking the Log In button.

I cleared all the browsing data, as well as any saved cookies for ko-fi, but no change.

Weird bit is if I wait a few days, then it will just work. Frustrating.

@dwolfman

Looks like something at Cloudflare is broken. Checking the dev tools in Edge and I see it is looping on trying to load some javascript modules over and over.

@ilbarbax

Quote:

How did you make the images from the hard disks? The AmigaOS 4 should see the MOS partitions just fine as long as they are based on SFS. Maybe the way the disk images were created prevents them to be mounted properly. Or, if you do not see them on workbench, try the Mounter tool under the System drawer, in case they are not auto-mounted.


@dwolfman

Quote:

That is a great idea. I will add it in my todo list. At least for now there is a workaround to do that as you described it. Create another VM and copy the kickstart.zip file, as long as you create the same type of system, i.e. create an AmigaOS 4 - Pegasos 2 to replace the same type of kickstart.

I am really sorry for your experience with Ko-fi page. Unfortunately, internet is getting worse every year. I hope that they will resolve these issues as soon as possible.

@walkero

I got a serious issue using different VM'.
Switching between the different VM for my tests the configurations remain corrupted. I mean the latest network setup remain in all subsequently opened VM invalidating the possibility to run them.
Also some other setup, such as the memory size, are suffering the same issue. I have to regenerate the the VM to be able to run them, but after few switching they get corrupted.
Not sure but it seems that the last in the list is the one not having issue, for me is OS4.

Where the data are saved?

Another issue is that I can't donwnload smb2fs53.6 I tried with netsurf,Odissey and IBrowse. I need it to have some shared disk with the host.

@walkero
Quote:There is nothing in the firmware to change it, it's AmigaOS which selects the default boot medium, and there is no difference on real and emulated systems either.
In the firmware, and possibly BBoot, you can only select from which media the kickstart modules are loaded, but once AmigaOS is started nothing from the firmware related to it is used.

CDs/DVDs/BDs, probably anything ATAPI, are using a boot priority of 5 (IIRC), the usual default boot priority of HD boot partitions is only 0.
To boot from HD/SSD/NVMe instead of CD/DVD/BD when both are available you'd have to change the boot priority for the HD/SSD/NVMe boot partition in MediaToolBox to 6 or higher.
Or use the "Early Startup Menu", enabled by pressing both mouse buttons or holding a modifier key (not sure anymore if it's CTRL, SHIFT or another one, there should be something like a bootmenu.doc for it), to select from which of the bootable partitions AmigaOS is started.
For multiple boot partitions on HD/SSD/MVMe you can use something like Kickstart/BootDevice (a text file with the partition name of the matching SYS:) as well, but that probably doesn't work for CDs/DVDs/BDs, at least not for unmodified AmigaOS 4.x install ISOs.

@ilbarbax
I have never seen that issue. I apologize for that experience. As you can imagine, I am switching between multiple VMs on my test environment all the time, especially when I am introducing new features.

Can you please write me down the steps that I need to follow to reproduce it? Try to create a new VM and write me what steps you followed until that breaks. That would be quite helpful.

@joerg
Thank you for that clarification and for explaining to me how it works. Quite helpful.