bloody does not comes with vioscsi driver?

I remember that there was an omnios image with vioscsi included, I thought it was bloody but wasn't

I just copy the vioscsi driver to the ipxe booted machine, but how do I generate an omnios release that has the driver already installed?

It was added to bloody in January so I'd expect it to be in the latest media.

It doesn't look like it was added to the installer miniroot though, which is an issue!

I opened omniosorg/kayak #273 so it will be in the next bloody media.

If you'd like help building your own in the interim, I can help you with that.

You just need a VM running omnios bloody somewhere

The cloud images should have it, apparently that is why we didn't put it in the installer. We didn't think that people would be installing on this type of service by booting the .iso and going through the installation process, but rather just using one of the canned cloud images.

andyf I managed to copy the vioscsi to the ipxe booted instance, just the driver won't attach I'm debugging why

at least omnios boots now, before it stuck in pit

I'm testing in oci, seems the hypervisor is somewhaat custom

trying add_drv -i 'pci1af4,1004,p' vioscsi, returns paste.ec/paste/W3CVavnh#BfgHQKaQqJoT5+-0zYmjcwtFa9V+PkIuNw4aYCYXSCV

andyf I also tried the cloud images with kayak, maybe I did something wrong but I did not see the vioscsi driver there

I was using this to pxe boot patches.byteswizards.com/kayak/ipxe.txt

The cloud images aren't always appropriate. On vultr, for instance, not only does it want a raw image but it needs to be uncompressed, so you have to grab a raw image, uncompress it, put that somewhere, and then transfer it.

It's just so much quicker to point them at an iso

I'm trying to modload vioscsi but I'm getting this WARNING: mod_installdrv: no major number for vioscsi I already manually added vioscsi to /etc/name_to_major and to /etc/driver_aliases

andyf I understand now, the miniroot has the drivers, when you have time let me know how to generate the miniroot to test right away

andyf seems is like gmake install-tftp will build the miniroot

Something like this should do it - edit the data/miniroot.pkglist file and add driver/storage/vioscsi

then: pfexec gmake zfsdestroy all clean PKGURL="pkg.omnios.org/bloody/core"

You can be more selective, but that will build everything and place it in `/kayak_image`

andyf I'll try again because it failed SANITY CHECK FAILED

It should ay why - is it libpsl? That fix was merged a couple of days ago

*say

could be that I just run gmake install-tftp before instead passing PKGURL

andyf failed seems in the same step paste.ec/paste/P2bDqzZp#u79jl81lDoUDxZc7-5tleJNJmGrRjWxl1Rbl0d+WU9H

What was the command? Running `zfsdestroy all` should clear the old things out, and build all the pre-requisite binaries etc.

andyf kayak/bin/sanity expected python-3.10 I only had 3.11 in bloody that was the root cause of the failure

andyf ok, now sanity works but fails the check paste.ec/paste/LVeRl8ha#c0KqgmSH-hhoII+bJeopvhYmFadkT/hLCFgH/u2qoMb

command was pfexec gmake zfsdestroy all clean PKGURL="pkg.omnios.org/bloody/core"

andyf I just updated the kayak baseline file to match to what's is expecting

that worked, but maybe truss won't work?

Truss recently stopped being shipped with isaexec IIRC, so things might just not have caught up in bloody yet.

ok my miniroot created wrongly paste.ec/paste/LFglKt2P#01wcHmDaB3bf9ksEaHv7yATkza6vR950on8cPR7vnDs

well at least I learned how to pxe boot omnios and build a miniroot