I use it this way, and it's why I created the extension. My solution for a .iso image is to use the qremaster script to load the extension earlier in the boot process. Basically, the vm-scsi extension is placed in /opt/tce within a cpio archive, which is the designated path for extensions that must be loaded early in the boot process.

Alternatively, you can use an IDE drive in your virtual machine which removes the need for the vm-scsi extension.

vi /mnt/sda1/boot/extlinux/extlinux.confIt did not work the first time, the 2 vm-scsi files (the .tcz and the .tcz.md5.txt) expanded in the root ('/') and were not loaded. I could manually load those with tce-load.I retried making sure the path would be /opt/tce but it did not work either (I did not even find the files!).

But somehow it is not automatically loaded. I still need to manually load it.

I tried adding lst=/opt/tce/onboot.lst in APPEND of extlinuxconf without success.

Maybe I need to modify onboot.lst that is in the tinycore.gz instead ? In which case I would need to rebuild it, maybe with the help of a remastering script?

There's gotta be an easier way..

-Beetle

PS: yes, I'm trying to boot from sda and have persistence there. I don't have IDE available in the vSphere I use. If all else fails I might try to have an iso that is resident in the vSphere server for the vm to have it available permanently. Currently, the iso is virtually loaded in the CDROM tray manually on the client side: it is unloaded as soon as the client disconnects, and somehow it always disconnects overnight. As of now, I no longer need to iso since the vm-scsi is available in the vm. It is just not automatically loaded and I don't know how to use a startup script in that scenario since my data & scripts (on sda) are not yet available at boot time.