00:54:58 <Smithx10> Anyone try running Propolis on SmartOS ?
03:28:11 <papertigers> I have run it on omnios, it that helps :)
13:06:52 <ktk> what is the syntax for pointing to a bootrom? can't find a specific example in the wiki
13:07:15 <ktk> doc says I can say uefi or bios but I need to point to a binary as well
13:27:26 <neuroserve> is it expected, that lx-images from https://github.com/omniosorg/lx-images are usable on omnios, smartos and triton alike?
13:30:52 <neuroserve> or is it a bug, if there's no sshd running inside a booted lx-image?
13:31:50 <ktk> about my bootrom question, I see /usr/share/bhyve/uefi-csm-rom.bin
13:32:01 <ktk> are they taken default when I set uefi?
13:32:08 <ktk> (there is bios too there)
15:19:30 <bahamat> neuroserve: If you're getting the image from images.smartos.org, then it's a bug if sshd is not running.
15:21:45 <neuroserve> bahamat : I wasn't sure, if on bare smartos or omnios it could be intended to have sshd off after an image has been started
15:22:36 <bahamat> It's more about who you got the image from than which hypervisor it's running on.
15:22:56 <bahamat> The images we produce are intended to be used in a cloud setting by non-operators, so it will always have sshd running.
15:23:28 <bahamat> That's the *only* intended access method for new instances.
15:23:33 <neuroserve> I had hoped, that it would be the same for all hypervisors/users
15:23:43 <bahamat> Tenants can, of course, set up anything else the want after create.
15:24:15 <bahamat> Well OmniOS may have a different intent with their images. I can't vouch for what ought to be running in an image you obtain from OmniOS.
15:24:40 <bahamat> It may be their intent that you create then zlogin to set up whatever. That's something that you'd have to ask them.
15:25:02 <bahamat> But if you got the image from images.smartos.org and the image does not attempt to run sshd by default, then that's a bug in the image creation process.
15:25:26 <andyf> I don't know either, but I think the omnios 'void' images have almost nothing running by default, on purpose. That may be true of some of the others there.
15:26:02 <bahamat> They're produced from docker images these days, so they're *very* light.
15:28:25 <neuroserve> I was actually testing the latest void image and was wondering how the intended customization process works there - and found out that tmux doesn't work in the current image :-)
15:29:11 <bahamat> That's something we'd have to look into :-)
15:29:20 <bahamat> But if you can ssh into it, that's the minimum viable image.
15:43:43 <neuroserve> what's the latest void image from images.smartos.org, btw?
17:27:16 <bahamat> f9d127e8-9c81-11eb-916e-471b372b0c3f  void  20210413  P      linux  2021-04-13T17:59:22Z