Virtio SCSI driver for AmigaOS4.1FE on QEMU

@derfs
Quote:
No problem – here’s the description

I tested this on Qemu-10 peg2 U3 with bboot and VirtualSCSIDevice v53.8
Just to be sure, I’ve now also checked Qemu-9 A1 U3 with -bios u-boot-amigaone.bin (not bboot)
The system disk is not located on VirtualSCSIDevice.
Test 1:
Create qemu-img create test.img 100M.
Attach it to -device virtio-scsi-pci.
After the system has booted, open the ‘Media Toolbox’
VirtualSCSIDevice 1.8 - works correctly.
VirtualSCSIDevice 53.8 - does not work
dubmp:

Test 2:
Use the pre-configured test.img (initialised with ‘Install...’, must contain a partition, does not need to be formatted)
VirtualSCSIDevice 1.8 – works correctly.
VirtualSCSIDevice 53.8 – works correctly.

I do not have the VirtualSCSIDevice version (virtioscsi.device.debug) – it is not included in the lha package.

As a side note, but is this confusing 53.8 naming are good thing for our 3d party stuff ? Isn't 1.8 ,etc are better ? I mean, why we need this 53.x there , like its component of the OS ?:)

@smarkusg

Thanks

It looks like there is a partition RDB entry for SFS on the test.img file, or at least thats what this bit of the log says.

Was this a new image file or was it previously setup as SFS in media toolbox?
- If it was setup in media toolbox, what blocksize did you use? was the partition the complete image file?
What version of SFS are you using?
Is it crashing as soon as Media Toolbox loads, or can you select any options (virtioscsi.device, 'Install', ...) ?

I cant currently replicate the crash, so this extra information will help lots.

I have also added a debug version to the latest lha file in https://github.com/derfsss/VirtualSCSI ... 3.8/VirtualSCSIDevice.lha

@kas1e

No real reason other than I was under a false impression that this needed to be a certain version number to work with mounter, so thats why only this driver has a v53 version number.

@derfs
Qemu-9 A1 U3 – this is a clean system. Nothing from ES was installed on it. I haven’t installed anything on this system apart from Virtio9PFS-beta, VirtualSCSIDevice 53.8 and system updates to U3. The network isn’t even configured.
The system disk HD.img, which I use with bus=ide.0, has an SFS file system
Command line:

I’ll show you this visually – it’ll be easier to see if you don’t have access right now and can’t check it properly.
Here’s the full TEST1 run, as you might be interested in one more error
I create an image: qemu-img create test.img 100M
I run QEMU from my command line as specified.
After the system boots, I launch ‘Media Toolbox’ – the first crash occurs
screen - > https://ibb.co/8nDxBzrz
I select in ‘Media Toolbox’ -> ‘virtioscsi.device’ – the second crash occurs. The ‘Media Toolbox’ programme stops responding.
screen -> https://ibb.co/qY2tTH9P

The problem also occurs if I remove the entry in SYS:Kickstart/diskboot.config ‘virtioscsi.device 8 3’

@derfs
Replying post #60 in previous page.
In QEMU the MV64361 and Articia are both emulated and don't emulate any of the floating buffer or transparency mentioned in the explanation so if that comes from an AI it's BS. It looks more likely something else is wrong. Maybe it just does not look for memory BARs at the right address as the PCI memory windows might be at different addresses on the two machines but if it found the config registers and the IO BAR it should also be able to look up the memory BAR. Maybe AmigaOS does not map these by default and BBoot or the A1 firmware did not do that either so maybe something needs to do that? Can you compare "info pci" and "info mtree" output on the two machines to see if the BAR needed is mapped and where? I think I've asked those outputs before but did not see an answer.