Illumos boot

[Matt Churchyard]

> Hi,

>> ..............
> /pci at 0,0/pci8086,2821 at 4/disk at 0,0 (sd1) online
> NOTICE: vioif0: Got MAC address from host: e4:94:1:0:ff:ff
> pseudo-device: tun0
> tun0 is /pseudo/tun at 0
> pseudo-device: lx_systrace0
> lx_systrace0 is /pseudo/lx_systrace at 0
> 
> panic[cpu0]/thread=ffffff0002566c40: BAD TRAP: type=d (#gp General 
> protection) rp=ffffff00025664c0 addr=20
> 
> sched: #gp General protection
> addr=0x20
> pid=0, pc=0xfffffffff80d375a, sp=0xffffff00025665b0, eflags=0x10282
> cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 
> 406b8<osxsav,xmme,fxsr,pge,pae,pse,de>
> cr2: fed3b5accr3: 1dc00000cr8: c
> 
>        rdi: 7f1a90ffffff00c3 rsi: ffffff00c33321f8 rdx: ffffff00c37f5828
>        rcx: ffffff00c3868603  r8: ffffff00ca7aa600  r9:             2ba6
>        rax:                0 rbx: ffffff00c30d0ef0 rbp: ffffff00025665c0
>        r10: fffffffffb8554c4 r11:                1 r12:               1f
>        r13: ffffff00c319f880 r14:               10 r15:               20
>        fsb:                0 gsb: fffffffffbc326a0  ds:               4b
>         es:               4b  fs:                0  gs:              1c3
>        trp:                d err:                0 rip: fffffffff80d375a
>         cs:               30 rfl:            10282 rsp: ffffff00025665b0
>         ss:               38
> 
> This is the log of the bhyve options used (apart from 1 cpu, 1G ram)
> 
> Oct 13 14:22:43:  [bhyve devices: -s 0,hostbridge -s 31,lpc -s 
> 4:0,ahci-hd,/data/vm/smartos/disk0.img -s 7:0,virtio-net,tap1] Oct 13 
> 14:22:43:  [bhyve console: -l com1,/dev/nmdm1A -l com2,/dev/nmdm2A] 
> Oct 13 14:22:43:  [bhyve options: -Hw -l 
> bootrom,/data/vm/.config/BHYVE_UEFI_CSM.fd]
> Oct 13 14:22:43:  [bhyve iso device: -s 
> 3:0,ahci-cd,/data/vm/.iso/smartos-latest.iso]

> Ouch, even with the additional verbosity, the output isn't very insightful.  All I can glean is that you are reasonably far along in the boot > process.  You could try to run with KMDB (-k boot option) and do some disassembly around that program counter to see if any specific module is > implicated.

> Alternately, I'd omit the network device and see how far that gets you.

It does appear that I can get as far as a login console without the virtio-net device

Matt