Bug #7186

Hipster and 151a8 fail to install as Xen DomU

Added by Andreas Pflug about 1 year ago. Updated 5 months ago.

Status:NewStart date:2016-07-17
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Difficulty:Medium Tags:needs-triage

Description

I'm trying to install OI as DomU unter Xen 4.4.1 (Debian 8). If I configure a VIF at installation time vif=['bridge=lan'], the kernel will panic in xnf:

panic[cpu0]/thread=ffffff0003ea7c40: BAD TRAP: type=e (#pf Page fault) rp=ffffff0003ea7980 addr=40 occurred in module "xnf" due to a NULL pointer dereference

sched: #pf Page fault
Bad kernel fault at addr=0x40
pid=0, pc=0xfffffffff8071bc7, sp=0xffffff0003ea7a70, eflags=0x10206
cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 2660<vmxe,xmme,fxsr,mce,pae>
cr2: 40
rdi: 286 rsi: 0 rdx: 8
rcx: ffffff0149e6c058 r8: 0 r9: 0
rax: 150 rbx: 2 rbp: ffffff0003ea7ac0
r10: 0 r11: 0 r12: ffffff0149fed000
r13: 0 r14: 15 r15: 7
fsb: 0 gsb: fffffffffbc60020 ds: 4b
es: 4b fs: 0 gs: 1c3
trp: e err: 0 rip: fffffffff8071bc7
cs: e030 rfl: 10206 rsp: ffffff0003ea7a70
ss: e02b

Warning - stack not written to the dump buffer
ffffff0003ea7860 unix:die+df ()
ffffff0003ea7970 unix:trap+dd8 ()
ffffff0003ea7980 unix:_cmntrap+12b ()
ffffff0003ea7ac0 xnf:xnf_tx_clean_ring+c7 ()
ffffff0003ea7b30 xnf:tx_slots_get+95 ()
ffffff0003ea7b70 xnf:xnf_intr+15b ()
ffffff0003ea7be0 unix:av_dispatch_autovect+91 ()
ffffff0003ea7c20 unix:dispatch_hardint+36 ()
ffffff0003e05970 unix:switch_sp_and_call+13 ()
ffffff0003e059d0 unix:do_interrupt+fa ()
ffffff0003e05a80 unix:xen_callback_handler+373 ()
ffffff0003e05a90 unix:xen_callback+cb ()
ffffff0003e05ba0 unix:__hypercall2+a ()
ffffff0003e05bb0 unix:HYPERVISOR_block+10 ()
ffffff0003e05bc0 unix:mach_cpu_idle+1d ()
ffffff0003e05bf0 unix:cpu_idle+fe ()
ffffff0003e05c00 unix:cpu_idle_adaptive+13 ()
ffffff0003e05c20 unix:idle+a7 ()
ffffff0003e05c30 unix:thread_start+8 ()

Same happens with 151a8.

I tried the installation without network, works ok without panic; the VM will boot ok with networking enabled:
Then I tried to enable networking manually, but as soon as I assign an IP address (ifconfig xnf0 192.168.x.y) I get the same panic.

xnf_crash.0 - mdb crash dump infos (262 KB) Michal Nowak, 2017-03-21 07:33 PM

History

#1 Updated by Aurélien Larcher about 1 year ago

Given the nature of this issue, I would suggest that you post your bug report to and CC .
I will reference the corresponding illumos bug when it is opened.
Thank you.

#2 Updated by Alexander Pyhalov 7 months ago

  • Project changed from OpenIndiana Distribution to illumos gate

#4 Updated by Michal Nowak 5 months ago

I can reproduce this issue with custom OI ISO created from current packages according to this XML: http://buildzone.oi-build.r61.net/text_mode_x86.xml on openSUSE 42.2 with Xen 4.8 from this repo: https://build.opensuse.org/package/show/Virtualization/qemu.

The DilOS ISO mentioned above ends like this on first boot (installation went fine):

> sudo virsh console DilOSpv
Connected to domain DilOSpv
Escape character is ^]
v4.8.0_05-482 chgset ''
DilOS Version 1.3.7.168-9d-gcc6 64-bit
Copyright (c) 2011-2017, DilOS. All rights reserved.
DEBUG enabled
NOTICE: vdev_disk_open("/dev/dsk/c1t1d0s0"): fallback to DKIOCGMEDIAINFO

NOTICE: vdev_disk_open("/dev/dsk/c1t1d0s0"): fallback to DKIOCGMEDIAINFO

Configuring devices.
dcpc: unable to resolve dependency, cannot load module 'drv/cpc'
NOTICE: vdev_disk_open("/dev/dsk/c1t1d0s0"): fallback to DKIOCGMEDIAINFO

NOTICE: vdev_disk_open("/dev/dsk/c1t1d0s0"): fallback to DKIOCGMEDIAINFO

...

NOTICE: vdev_disk_open("/dev/dsk/c1t1d0s0"): fallback to DKIOCGMEDIAINFO

panic[cpu1]/thread=ffffff0004b63c40: assertion failed: tidp->next == INVALID_TX_ID, file: ../../common/xen/io/xnf.c, line: 1268

ffffff0004b63a60 genunix:process_type+1900ad ()
ffffff0004b63ad0 xnf:xnf_tx_clean_ring+120 ()
ffffff0004b63b40 xnf:tx_slots_get+e0 ()
ffffff0004b63b80 xnf:xnf_intr+139 ()
ffffff0004b63be0 unix:av_dispatch_autovect+81 ()
ffffff0004b63c20 unix:dispatch_hardint+36 ()
ffffff0004b12950 unix:switch_sp_and_call+13 ()
ffffff0004b129b0 unix:do_interrupt+146 ()
ffffff0004b12a70 unix:xen_callback_handler+42e ()
ffffff0004b12a80 unix:xen_callback+18f ()
ffffff0004b12b90 unix:__hypercall2+a ()
ffffff0004b12ba0 unix:HYPERVISOR_block+10 ()
ffffff0004b12bb0 unix:mach_cpu_idle+1d ()
ffffff0004b12bf0 unix:cpu_idle+d1 ()
ffffff0004b12c00 unix:cpu_idle_adaptive+13 ()
ffffff0004b12c20 unix:idle+a2 ()
ffffff0004b12c30 unix:thread_start+8 ()

dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel + curproc
dumping:  0:34 100% done
100% done: 80825 pages dumped, dump succeeded
rebooting...

Any directions what might be done next?

#5 Updated by Igor Kozhukhov 5 months ago

Michal Nowak wrote:

I can reproduce this issue with custom OI ISO created from current packages according to this XML: http://buildzone.oi-build.r61.net/text_mode_x86.xml on openSUSE 42.2 with Xen 4.8 from this repo: https://build.opensuse.org/package/show/Virtualization/qemu.

The DilOS ISO mentioned above ends like this on first boot (installation went fine):

[...]

Any directions what might be done next?

well, i need a time for debug dilos on new xen.
i'm using dilos pv guests under dilos-xen-3.4-dom0
it is old one, but still working
probably need updates for new xen under dilos side, but i'm not ready for it yet.
based on log - missed one module
dcpc: unable to resolve dependency, cannot load module 'drv/cpc'
i can take a look why i missed it on installed system.
i have plans update dilos to new xen, but i have no estimates when i can start to do it - need port build dependencies to new system first - i'm working on it. you can ping me on #dilos IRC (FreeNode)

#6 Updated by Michal Nowak 5 months ago

Thanks Igor.

Attaching mdb crash dump infos per https://wiki.illumos.org/display/illumos/How+To+Report+Problems. Hopefully it's of some use (it's aligned to 80 characters as I got it via serial line).

Also available in: Atom