10:59:16 Hello everyone! 11:00:21 Anyone manage to get OmniOS to communicate the necessary HPE iLO information as part of AMS please? 11:10:04 I'm here waiting for an answer. 11:15:17 I have an ip addr object in state disabled. What's the right incantation to enable it? I tried various forms of ipadm enable-addr and enable-if but to no avail 12:06:05 also, still can't get openbsd 7.4 to boot under bhyve on r46 12:58:58 aru - I've just tried it and it seems ok, so we should be able to work it out. 12:59:08 Did you set the `type` attribute in the zone config to `openbsd`? 12:59:17 Welcome to the OpenBSD/amd64 7.4 installation program. 12:59:17 (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? 13:00:25 huh 13:02:09 no, this is the zone config I used https://pastebin.com/UkEXBm2n . Is the type=openbsd thing documented somewhere? 13:02:44 Yes, in the man page for the brand - https://man.omnios.org/bhyve.7#type 13:04:23 Is your ipadm object possibly somehow temporarily disabled? If you try to enable it with the -t flag, does it work? 13:04:34 oh, thank you 13:05:21 I just installed by writing install74.img to a second disk and booting from that, then installing on the boot disk (sd0). 13:05:35 The only special thing was typing `set tty=com0` at the first prompt to switch to the serial console for the rest 13:06:15 it was probably the type thing, it completely ignored the attached iso and tried booting from network 13:06:55 If that doesn't work for any reason, the temporary second hard disk method definitely does. 13:07:30 if I try ipadm enable-if -t internal0 I either get "ipadm: Could not enable internal0 : Interface already exists" or "ipadm: Could not enable internal0 : Interface does not exist" depending if I ifconfig internal0 plumb/unplumb before running that 13:11:29 I generally wouldn't mix ipadm with ifconfig (unless this is for trying to unstick/debug things) 13:11:44 but if it was originally plumbed with ifconfig, does `ifconfig up` help? 13:13:08 hmm, no luck with type=openbsd https://pastebin.com/qN1WQ74B 13:13:37 Perhaps their .iso is not UEFI enabled? 13:13:54 but then it wouldn't work for you either? 13:14:12 I booted from the .img file written to a second hard disk 13:14:43 ah 13:14:44 Then, after I installed, I halted and deleted that temporary disk 13:14:49 right 13:16:29 let's try that 13:17:20 After creating the second disk (which was 'fast/hdd/test1' for me), I just did 13:17:20 dd if=/data/iso/install74.img of=/dev/zvol/dsk/fast/hdd/test1 bs=1M 13:27:59 now I get to openbsd's loader, but it just loops, this is all i get in the console https://pastebin.com/v5KTrCLw 13:28:28 Try the `set tty=com0` at that first boot> prompt, then return 13:30:13 It was `set tty com0`, but that did the trick, thank you 13:45:52 Great. For me, the installer offered to change the default console when it was near the end, and it all worked after that. 14:01:38 I ran into the tty=com0 thing the last time I tried openbsd 15:59:01 huh, can't brain today 16:16:10 I'm running out of ideas, I managed to get it installed, but I can't make it to boot from the disk it was installed to, it again goes straight to network booting no matter how I faff around with bootorder and things 16:25:51 oh, i see, what the heck 16:59:17 turns out when I selected whole disk automated partitioning during the installation, it picked up mbr partition table without setting up all the efi stuff 20:52:58 is there something extra that one needs to set to get vnc to work apart from the vnc attribute? Once i set it to on, the zone just halts almost imediatelly 20:55:09 oh, "device emulation initialization error: Operation not supported" 20:59:35 so that was a result of vga=on, which I put in there after I wasn't able to connect with realvnc, but that was just realvnc doing something silly