09:28:51 <jimklimov> Cheers, can the illumos "loader" (as seen in OI for example) be used to boot FreeBSD from ZFS? I suppose it should not have any trouble booting OmniOS, FWIW?
09:30:19 <jimklimov> For context: migrating some NUT CI VMs from FossHost to DigitalOcean, and an OI cloud image is something I could use as a "custom template" there - so if I can just zfs send/recv the existing VMs' rootfs'es into the image that started out as an OI VM, that would simplify a lot :)
10:03:18 <otis> the loader is imported from freebsd, actually.
10:03:36 <otis> tsoome would answer your question with 100% certainity.
10:52:37 <tsoome> jimklimov chainload should work -- assuming the disk layout is done in supported way. direct load may, but it has never been the goal there, so it is not tested in any way.
11:16:54 <tsoome> jimklimov for chainload, you want to point to [p]mbr or loader.efi from freebsd.
14:56:48 <jimklimov> yupee, OI from cloud image which was sucking in the zfs send/recv pool contents from fosshost actually booted, usable console, network and all!
14:57:30 <jimklimov> DigitalOcean web-console does suck by disconnection during VM reboot, so early messages and sometimes loader menu are lost :\
14:58:30 <jimklimov> hm, `init 6` seems to have got stuck after `syncing file systems... done` - I think it did not reboot actually
14:59:10 <jimklimov> FWIW, also says "WARNING: Fast reboot is not supported on this platform due to presence of boot-time modules" - can this be related to not rebooting a line later?
15:07:15 <jimklimov> Also, is https://github.com/illumos/metadata-agent packaged for OI? :)
15:09:39 <jimklimov> Hm, after a few minutes, a "rebooting..." line appeared
15:09:39 <jimklimov> And that dying uptime's console is still up...
15:09:57 <jimklimov> So at least 15 min since `init 6`
15:16:15 <ptribble> You may be hitting https://www.illumos.org/issues/14526
15:16:16 <fenix> → BUG 14526: illumos guest hangs on reboot under QEMU 6.0.0 (New)
15:17:56 <jimklimov> you're the quickest shot in the West! :)
15:18:33 <jimklimov> at least by symptoms - looks like it
15:21:43 <ptribble> I've seen exactly that behaviour on Digital Ocean a few times :-(
15:21:46 <jimklimov> did anyone come up with some solution or workaround? it would be cumbersome to have to go to the hosting UI to power-cycle the VM whenever we want a reboot (more so if it were unintentional - some kernel dump, zfs deadman, etc.)
15:22:28 <jimklimov> for intentional cases, maybe might add some late-shutdown restapi call to "powercycle me!" in the same style NUT drivers tell the UPS to cut the juice
15:22:57 <jimklimov> just need some way to enable running userland-provided logic after svc.startd has killed everyone
15:29:25 <jimklimov> Are there watchdogs on DO for tighter integration (like that metadata-agent)? Can that take care of eventual unattended reboots?
16:02:10 <jimklimov> Does current illumos (OI, OO) include some qemu guest software that could 1) probe if the QEMU host provides a virtual watchdog device, and 2) actually use one? I remember there was bmc-watchdog, but was it only for certain physical hardware?.. :)
16:03:59 <jimklimov> at least there was nothing evident in `prtconf`...
16:15:14 <jimklimov> eh, guess I'll leave it trying to reboot after an OS update now; waiting for DNS to refresh before productizing this VM anyway...
16:15:14 <jimklimov> if "rebooting..." appeared after 10-15 mins, who knows what another hour can bring? :)
17:00:29 <gitomat> [illumos-gate] 5583 support QLogic 16Gb FC-HBA -- Hans Rosenfeld <hans.rosenfeld⊙nc>
21:18:26 <jimklimov> The world is safe: I came back from a walk, and that VM booted after all, 3h:10m ago
21:19:12 <jimklimov> So it was roughly hanging for 2 hours, but did reboot. Not AWOL indefinitely. Better than nothing =D