Kyvos was updated

@derfs
I haven't seen that USB error with Update 2 when following my AmigaOS with BBoot guide posted at the URL in my signature which I have tested and can say that works. I haven't tested other ways or Kyvos so don't know about that just guessing. I can't easily have a look at the Kyvos docs if it can't be downloaded freely without hassle so don't know what's in the latest version. I've only seen an early version once but I forgot that too.

@walkero
I think it's safest to always use Kickstart.zip matching the installed system or CD only updating the files that are needed to do the install and update Kickstart.zip after each update. That way problems or spurious errors (that you may or may not ignore) can be avoided. So my guide recommends that way. Maybe we need a simpler way to update Kickstart.zip but it should not be too difficult to do that after each update. At least users would be trained to not forget that after the next update.

I really need to update my web pages but I rarely come to that when there are other things to do like improving code instead. But I'll eventually get to that. Although it seems people know about Kyvos probably more than about my pages and QEMU now.

@balaton
Quote:

To be honest with you, I do not expect that users will do it, as they haven't done it the past 2 years. If the whole process would be easy, tools like Kyvos would not be necessary.

In my view the errors that need to be ignored are minor, against doing the kickstart.zip file manually, knowing what exactly to change and updating the kicklayout as well.

I do not know if there could be a version of bboot that could boot the system and let the kickstart modules to be loaded from the OS hard disk. This way, no mambo jumbo would be needed.

Quote:

The manual as well as the Kyvos application are freely available to everyone. Now, sure, it requires you to use a fake email to get access to the files.

You know, the most requested feature is that Kyvos do all the installation automatically without the user needing to do anything, just provide the files. This is something I am thinking to add at some point as soon as I solve some blocks. Users need as less manual steps as possible, and I believe that Kyvos provides that, but it can get better. But it is also a new tool, with just a few months being released.

@walkero

Hi,

Tried Kyvos last month on Linux. The emulation didn't work, apparently because the Qemu I installed was too old (K-L told me).
Maybe you could add a check on the Qemu version that is found in the OS.

Then I abandoned the idea. I should try again...

Bye

Hello everybody,

I trust all is well in the OS4 community lately.

I am running the latest Kyvos version 1.6.1 on my Mac M1 silicon on the latest version of MacOS Tahoe 26.0.1.

In addition, I am running on the latest Homebrew version on my Mac with all the casks/formaule up to date as of today.

I am also running on the latest QEMU 10.1.2.

I had a look at the supplied Kyvos 1.6 manual and tried to best of my ability to follow the instructions as best as I can.

I have unsuccessful and successful attempts to get OS4.1 more or less working.

I have installed the Pegasus 2 ISO file for OS 4.1FE using the automatic Kyvos VM creation wizard successfully.

However I am not sure to why the automatic VM creation wizard did not automatically install Update 1,2 and 3 as I had the files in the same directory as the ISO file.

Also I have not changed the file names of the updates too.

It look like I am running on a Pegasus 2 with Amiga OS 4.1 from 2014 on kickstart version: 54.30 and workbench version 53.14 without any updates added.

Question 1: Any ideas how to get the Kyvos VM creation wizard to automatically install update 1,2 and 3?

I played around with the Kyvos SMB section.

I tried various attempts to configure the MacOS file sharing settings and checking Homebrew to install Samba but I still cant get OS4.1 to detect a shared folder on my Mac.

Question 2: Any ideas on how to get SMB working in OS4 under Kyvos?

I attempted to created a 2nd hard drive file using the Kyvos HDD creation wizard under OS4 VM and also mapping it successfully.

The 2nd hard drive file is detected fine on the OS4 media tool box application, and I tried to follow the exact similar process as if you were using the installation process to install OS4.1 instead I created partition as DH2 using SFS00 and check marking auto mount, bootable and boot priority is still 0.

Each time I reboot the VM, OS4.1 still cannot detect DH2 for some unknown reason.

Question 3: Any ideas on what I am doing wrong in getting the 2nd hard drive to be detected in OS4.1. I tried various size of 2GB, 4GB and 20GB but still no luck?

Any suggestion, assistance and feedback would be appreciated.

Thank you.

@Boabster
Firstly, thank you for using Kyvos.

Quote:

Kyvos is a frontend for qemu, that helps users to create a virtual environment to run AmigaOS 4, MorphOS and AROS. It is not possible for Kyvos to access the virtual hard disks and make any changes to them. That's why Kyvos cannot (for now) make any changes to the OS that is running in the Virtual Machine, which means it cannot apply the updates. The updates are needed for the required kickstart.zip file to be created so that the users do not need to do it themselves.

Quote:

Not possible for now. If that was possible, the manual would say so, wouldn't it?

Quote:

I am sorry but I cannot help you much with it. Maybe someone who might have already done something like that.

Quote:

There are some generic guidelines in the manual but as stated there, this is something that can vary from system to system, and the user needs to figure it out how it can be done. Generally speaking, if you make a folder available using samba then it should be accessible by the qemu as well as described in the Kyvos manual.

Quote:

If you do not intend to install the system on that partition, and boot from it, there is no need to set it as bootable.

Quote:

Did you format this partition? From the System > Format utility, if you see the partition there, you could format it.

Also check the System > Mounter and see if that is showing up there as well.

Quote:

I cannot be sure, to be honest. If you could share any screenshots of the mediatoolbox and the configuration you did there, that would be helpful.

@walkero

One suggest.

Concerning Sam460 OS4 (probably Mos too) emulation, setting the USB media, the whole command is translated as "-drive if=none,id=ufat,format=raw,file=fat:rw:myshreddir -device usb-storage,drive=ufat". As known and as stated in the Balton Qemu support webpage, this does not work hanging the boot. To avoid this, only the first half of the command should be reported in the qemu string while the second half should be activated via console. Sure to teaching anything new, it is just to clarify the context.
I think this exception should be handled by kyvos by including the first half of the command (if Usb media is set) and adding a messagebox before running qemu to remember to activate the console and then imputing the second half of the command to activate the usb sharing. Even better I do not know if there is a way to run a sort of batch under OS4 or Qemu consol to do that semiautomatically.

At the moment to do this I copied the qemu string generated by kyvos to a batch and modifying it according above description. This is quite boring not having the possibility to run the emulation directly from kyvos unless I remove the Usb media.

Thank for your great work.

@ilbarbax
Thank you for that recommendation. I will add it in my todo list and will have a look on it for sure.
I am sorry for the inconvenience you are experiencing. I will do my best to cover it, although I understand that it is not avoidable to have the user to do some manual work. Maybe consider using a samba share, which doesn't have a file size limit, or sharing file using ftp.

@ilbarbax
I hope to have an updated sam460ex u-boot in the next QEMU release (that will be out before Xmas) that should fix this but I haven't finished it yet and this week is the last to merge things before the release freeze so if it does not get in then will only be in release after 10.2 due next year. Until then QEMU has -monitor option to redirect the monitor to anything which management apps can use to control the virtual machine and QEMU also has some JSON based interface called QMP if I'm not mistaken for this but I don't know much about that. It should be described somewhere in https://www.qemu.org/docs/master/interop/qmp-spec.html

Great news thanks

@balaton
Thank you so much for your continued work on qemu code. I appreciate it.

After I got Kyvos 1.6.1, I deleted the "temp" VM again and created a new one using the automatic mode. This time it worked and included the Update 3 files like it should.

Not sure what happened before, but this time it worked, and I booted the old VM after copying kickstart.zip over, with all the new stuff showing up like it should.

@ilbarbax
If you need u-boot under QEMU for sam460 based on u-boot-2015.c where
"-drive if=none,id=ufat,format=raw,file=fat:rw:myshreddir -device usb-storage,drive=ufat" works, let me know via PM.

I once compiled this u-boot for my own needs. I don't want to provide a link here.
It works fine for me, but it may not work correctly on other emulation configurations.
It is better for those who do not need experimental things to use u-boot under QEMU provided with the QEMU sources/package.

screen 1 -> https://ibb.co/Df3PWRWy
screen 2 - > https://ibb.co/Jjd0KzvT

@everyone
A new version of Kyvos 1.7.0 just got released. Read more about it at https://ko-fi.com/post/Kyvos-1-7-0-released-R6R81NHQWD

Here is what changed

## 1.7.0 [2025-10-27]
### Added
- Added binary for Linux 32bit Arm systems, like a RaspberryPi
- Added a way to duplicate a VM in the right-click menu

### Changed
- Changed the "AmigaOS4.1 FinalEdition Update 3" to be mandatory when AmigaOS 4.1FE Pegasos2 or AmigaOne system is created
- Changed the hash of the "AmigaOS4.1FinalEditionUpdate2-53.14.lha" to be the latest one from Hyperion's website
- In the welcome window, the Continue button remains enabled even if a dependency is missing. This is necessary for 32bit systems which do not have the qemu-system-x64 available. It is up to the user to take the risk to continue, instead of blocking him.

### Updated
- Updated the manual fixing issues, made the usage of update3 more clear in various places, added more sections and more questions in the FAQ section

Kyvos and its manual is provided free of charge, but if you like it, please consider a donation. You can get Kyvos at https://ko-fi.com/s/6476fdadd2

There are plenty of things in my to-do list, which can be found at https://pms.walkero.gr/projects/kyvos/roadmap