Virtio SCSI driver for AmigaOS4.1FE on QEMU

I have upload the latest version of this device driver to https://os4depot.net/?function=showfil ... er/storage/virtioscsi.lha for everyone to try out.

Follow the installation guide in the link and have fun!

@derfs

Amazing work..

@derf

I tested it with Qemu/Pegasos, but it seems that I cannot get this driver to work.

I chose method 1 for the installation.

Method 1: Standard (copy to DEVS:)

1. Copy virtioscsi.device to DEVS: on your AmigaOS system.
2. Reboot.
3. The driver loads automatically at startup and announces all
discovered disks to mounter.library.

I start Qemu with the additional configuration

“-device virtio-scsi-pci,id=scsi0 -drive file=/Volumes/Data/AmigaOs4.1BackUp/GameBackUpHD/hd2SFS.img,format=raw,if=none,id=hd0 -device scsi-hd,drive=hd0,bus=scsi0.0”

It doesn't seem to work for me, and Mounter or MediaToolBox don't show me anything either.

@Maijestro
QEMU/KVM is required. You need to run Qemu on PPC. For example, you would need to install *Linux on your PPC machine and run QEMU there.

@Maijestro

You can try to run mounter manually, but you will have to change the tooltypes to point it to the correct device.

Most of my time has gone into checking it loads as a kickstart module, so DEVS: installation method may have an issue still. I will check over the weekend.

@smarkusg

This was built and tested using QEMU running on Win11 x64.

@derfs
Can't test now, but so you can mount some part of the windows's hdd inside of qemu without needs of "fat32 sticks" mount and transfer in fast manner any amount of data and have it appears in both win32 and qemu at the same time ?

@derfs
Quote:

OK. I misunderstood the description of the “QEMU/KVM” requirements.

I did a little test on Arm64 - Asahi Linux Fedora and macOS.
I checked it on Peg2 and A1 with bboot. Unfortunately, it doesn't work for me.
The only line from the AOS4 kernel debug is that the driver is loading. You can see it in the screenshot.



To be sure, I also checked if my qemu compilation works correctly with virtio on A1 with *Linux.
Everything works fine there.



My line: -device virtio-scsi-pci,id=scsi0 -drive file=smtest.hdf,if=none,id=hd0 -device scsi-hd,drive=hd0,bus=scsi0.0

*) Don't pay attention to my startup with “nvme”. I checked without it (removed from Kicklayout), clean command lines, etc...
I added the screen because it was my last attempt.

I hope this will be helpful to you.

@smarkusg

Try this

@kas1e

Unfortunatly no, as this still uses image files. I could not see a 'virtio-9p-pci' device available for powerpc machines in my installation (its not available for x64-Windows).

@derfs
Quote:2 errors there:Device drivers in DEVS: aren't started automatically, they are only loaded and started if something is using it.
For example a DOSDriver in DEVS:DOSDrivers for a partition using DEVICE=virtioscsi.device.
Maybe you should include the DOSDriver you are using for this method as an example.

The slb_v2 is running in U-Boot which doesn't know anything about AmigaOS assigns and something like "DEVS:virtioscsi.device" can't work, it has to be instead. Or "MODULE Kickstart/virtioscsi.device" if copied to the Kickstart directory.

@joerg

Thanks for the tip. So I integrated Virtioscsi as a Kickstart module in Kicklayout after adding it to Kickstart.

“MODULE Kickstart/virtioscsi.device”

The module loads correctly and AmigaOS 4.1 boots without any problems. But my connected virtual HD does not appear here either. Mounter and MediaToolBox do not display anything here either.

SySMoon also shows me that VirtioScsi is being used.

Integrated with:

“-drive file=/Volumes/Data/AmigaOs4.1BackUp/Test.img,format=raw,if=none,id=hd0 -device scsi-hd,drive=hd0,bus=scsi0.0”

I have no idea how this is supposed to work.

@joerg

well that part of the readme is very wrong! I will update it asap.

@all

The readme should say put the virtioscsi.device file in the SYS:Kickstart/ folder, add the entry to Kicklayout, and reboot. When you next run Media Toolbox, you will see the entry for virtioscsi.device. You will need to install the new disk, create a partition and format it - just like any other disk.

The 'Copy to DEVS:' entry should only be for those that want to test it via Mounter or a manual mount list.

*EDIT*

If you are using BBoot with the kickstart files zipped up, then you need to add virtioscsi.device to that zip file, and add the entry to Kicklayout in the zip file too.

@derfs

Perhaps I should have been a little more precise. Virtioscsi.device is already in my Kickstart.zip for BBoot and is configured as a module via Kicklayout.

@derfs
Unfortunately, it doesn't work for me.
I have “MODULE Kickstart/virtioscsi.device” set in boot (I had this setting when I checked earlier).
I created a new disk image.
Additionally, I checked “channel=0,scsi-id=0,lun=0” (I also checked this earlier).
Should anything other than “[virtioscsi] Loading Version: virtioscsi.device 1.3.1042 (23.02.2026)” appear in the debug kernel?
Someone else needs to check this because I've run out of ideas on my machine.
It would be best if someone could let me know if this driver works for them.

@smarkusg

Looks like there is a fundamental difference in how the amigaone and pegasos2 qemu machines deal with virtio pci devices.

@everyone hang fire for now, and I will get a new version out asap.

@derfs
I also checked on AmigaOne, but with bboot.
You didn't mention whether you use AmigaOne bboot or uboot.
I'll wait for the new version. If you need to check anything, let me know.

@smarkusg

new v1.5 in the upload queue on os4depot. I have updated the readme as there are slight differences between installation with bboot/non-bboot and amigaone/pegasos2 machines.

@derfs

Quote:

Perfect! With the new version of Os4Depot, it now works with the Qemu/machine Pegaso2.

That's cool, thanks. It's a shame we can't boot from this HD, but it's still very useful and the transfer rates are excellent.

@derfs
Quote:

Still it's cool, as you have no need for usb-fat-sticks anymore, right ? I.e. it's just the same like it was with usb-sticks, just no more size limitation like for emulated usb-sticks ?

@Maijestro
But you still can't operate in real time with it ? I mean, to be able to copy/delete files from os4 to it, and be able to see them at the same time on win32, and copy/delete files on win32 , and be able to see changes in realtime inside of qemu ?