marino, there's people talking about omnios here: illumos.topicbox.com/groups/omnios-discuss I'm not sure if you know about it. I'm new myself so can't answer your question exactly.

if you do get the usable prompt on bootloader (press esc before it boots and land on OK prompt), enter: show efi-version -- if it does show the version number, you have UEFI boot; next check output from: framebuffer get -- if it does not show framebuffer address then you have no usable console for kernel, we only can do memory mapped framebuffer console as we do not have other drivers. No console means that you would need install image

which will set up network and allows remote access without user action on console.

i have a bhyve vm running in a zone(created with zadm), but dhcpd doesn't work. additionally, I need to run pppoe on the one interface. I'm guessing it doesn't work because the auto created vnic is not in bridge mode? How does one setup a VM in bhyve to allow dhcpd to work on the subnet?

it does not work how exactly?

it's an openbsd vm running dhcpd. the physical devices on the network don't get an ip address.

does this vm see dhcp requests ?

like, with tcpdump, tshark - do they list dhcp traffic?

Is the allowed-address property set in the zone configuration? That completely messes with dhcp.

I see this in tcpdump paste.debian.net/1377327 the network config is like so paste.debian.net/1377328

I have the allowed address set to the VMs IP address.

ok, solution was to remove the allowed-address property. thanks ptribble

tsoome: efi-version = 2.80 and "framebuffer get" returns lots of information (EDID resolutions, address, etc)

tsoome: something interesting - I went ahead an installed the latest smartos. This box has two nvme drives and I installed smartos on the 1T one. The installation was straightforward, but even though I made the zpool bootable, the nvme boot entry doesn't show in bios so I can't boot into it.

I had the idea of using omnios menu option "boot to hard disk" to see if I could at least access it. It said "disk not found" but then proceeded to successfully go to the install menu

i don't know if that would have happened without the previous smart os install. maybe.

either way I'm trying to figure out how to either get this recognized by the bios or get the grub menu of the other drive to be able to boot the 1T smartos image

my next step was to try to install omnios in a smartos zone

marino I havent seen *BIOS* system able to boot from nvme. UEFI, sure, but not BIOS.

it's UEFI. i'm old

;)

Once I get smartos set up how I want it, I'm going to try installing omni in a zone

I'm pretty sure the glitch I found would result in a native install though

the first pass with smartos I didn't know to set the bootable zone to work with UEFI so it's not recognized, but now the install option is off the table, so I probably need to install something else on the 1TB drive and then reinstall smartos

smartos is a bit picky about left over old pools. you better wipe like 1GB at the end and at the beginning of the disk, that should do.

I've got it all sorted. there

is a factor reset command. I recreated the pool to support UEFI and now it's recognized and bootable with the usb key

yes, factory reset should do it too.

marino: congrats!