Kvm/libvirt
it goes a good ways, but then cycles back. I set it to verbose and kmdb
and am at the kmdb prompt with the following traceback:
I set console=ttya, acpi = off, single user = on, verbose = on, and kmdb
= on and selected option 1 to go into single user mode.
Aside: it'd be nice if the console stuff was mirrored to ttya as a
default so that one could do everything without having the virtual
console up. RIght now, the menu is only available on the virtual console.
module /platform/i86pc/kernel/amd64/unix: text at [0xfffffffffb800000,
0xfffffffffb959b23] data at 0xfffffffffbc00000
module /kernel/amd64/genunix: text at [0xfffffffffb959b40,
0xfffffffffbbe5c07] data at 0xfffffffffbc9ea80
Loading kmdb...
module /kernel/misc/amd64/kmdbmod: text at [0xfffffffffbd0edc0,
0xfffffffffbdc7667] data at 0xfffffffffbdc7680
module /kernel/misc/amd64/ctf: text at [0xfffffffffbbe5c20,
0xfffffffffbbf03cf] data at 0xfffffffffbe00ae0
panic[cpu0]/thread=fffffffffbc38560: BAD TRAP: type=d (#gp General
protection) rp=fffffffffbc7abc0 addr=0
#gp General protection
pid=0, pc=0xfffffffffb861ccb, sp=0xfffffffffbc7acb0, eflags=0x10002
cr0: 80050011<pg,wp,et,pe> cr4: b8<pge,pae,pse,de>
cr2: 0cr3: 27000000cr8: 0
rdi: 9c5a203a rsi: e rdx: f00
rcx: c0011023 r8: fc r9: f61
rax: 8 rbx: fffffffffbc397a0 rbp: fffffffffbc7acb0
r10: fffffffffb856f10 r11: f r12: 8
r13: 1f r14: 8 r15: 0
fsb: 200000000 gsb: fffffffffbc397a0 ds: 0
es: 0 fs: 0 gs: 0
trp: d err: 0 rip: fffffffffb861ccb
cs: 30 rfl: 10002 rsp: fffffffffbc7acb0
ss: 38
Warning - stack not written to the dump buffer
fffffffffbc7aaa0 unix:real_mode_stop_cpu_stage2_end+b1f3 ()
fffffffffbc7abb0 unix:trap+a70 ()
fffffffffbc7abc0 unix:_cmntrap+e6 ()
fffffffffbc7acb0 unix:xrdmsr+b ()
fffffffffbc7ad70 unix:workaround_errata+3c0 ()
fffffffffbc7adb0 unix:mlsetup+59e ()
fffffffffbc7adc0 unix:_locore_start+8b ()
panic: entering debugger (no dump device, continue to reboot)
Welcome to kmdb
kmdb: unable to determine terminal type: assuming `vt100'
kmdb: dmod krtld failed to load: Error 2
[0]> $C
fffffffffbc82e00 kmdb_enter+0xb()
fffffffffbc82e30 debug_enter+0x59(fffffffffb93d3d8)
fffffffffbc82f10 panicsys+0x600(fffffffffb93baf8, fffffffffbc7a9b0,
fffffffffbc82f20, 1)
fffffffffbc7a9a0 vpanic+0x15c()
fffffffffbc7aa10 param_preset()
fffffffffbc7aaa0 0xfffffffffb84a56c()
fffffffffbc7abb0 trap+0xa70(fffffffffbc7abc0, 0, 0)
fffffffffbc7abc0 0xfffffffffb8001d6()
fffffffffbc7acb0 xrdmsr+0xb()
fffffffffbc7ad70 workaround_errata+0x3c0(fffffffffbc397a0)
fffffffffbc7adb0 mlsetup+0x59e(fffffffffbc7adc8)
fffffffffbc7adc0 _locore_start+0x8b()
On 3/9/2017 3:53 PM, Dan McDonald wrote:
On Mar 9, 2017, at 3:46 PM, Michael Rasmussen <m...@miras.org> wrote:
On Thu, 9 Mar 2017 11:18:17 -0500
Dan McDonald <dan...@omniti.com> wrote:
Just updated it in place to new bits that invoke "kbd -s" prior to the menu's
first display. The new checksums for http://kebe.com/~danmcd/webrevs/r151021-kayak.iso
are:
md5 (r151021-kayak.iso) = 971cc094a6dc89666f76bc453e2ab13a
sha1 (r151021-kayak.iso) = b72cb1dd08a09f5f9e491acc5aac8f25f852d000
sha256 (r151021-kayak.iso) =
4350d227b28f65746bb361686bde05202d536e5137db07dbfee3d9611756a622
Hi Dan,
Just tried this iso but disk discovery is weird. Can you explain this?
(see attached screenshot)
Is this on a Xen install? Prakash mentioned that there are "two paths, one
device" problems on Xen.
BTW, option #1 (based on diskinfo) works now, if you just want a whole-disk
install.
Dan
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss