* [Xen-users] kernel panic in domU
@ 2011-09-20 21:27 jinho hwang
2011-09-21 1:32 ` Jeremy Fitzhardinge
0 siblings, 1 reply; 4+ messages in thread
From: jinho hwang @ 2011-09-20 21:27 UTC (permalink / raw)
To: xen-devel, xen-users
[-- Attachment #1.1: Type: text/plain, Size: 4285 bytes --]
Hi All,
I'm using xen 4.0.1, kernel 2.6.32.45 for DomU, kernel 2.6.32.46 for Dom0. I
also use pygrub to boot the domU kernel in the xen. I tried all the things I
know for making this work, but unfortunately it does not work at this
moment.
The kernel shows panic message and then escapes. The following is thetrace..
it tells me that the hypercall_page might trigger the xen_panic_event and
then kernel got it to make itself panic.
-----------------------------------------------------------------------------
cs:eip: 0061:c04023a7 hypercall_page+0x3a7
flags: 00001286 i s nz p
ss:esp: 0069:dfc1ff14
eax: 00000000 ebx: 00000002 ecx: dfc1ff18 edx: 00000000
esi: 00000000 edi: 00000000 ebp: dfc1ff28
ds: 007b es: 007b fs: 00d8 gs: 0000
Code (instr addr c04023a7)
cc cc cc cc cc cc cc cc cc cc cc cc cc cc b8 1d 00 00 00 cd 82 <c3> cc cc cc
cc cc cc cc cc cc cc
Stack:
c04036f2 00000003 c086ecc8 00000000 00000000 dfc1ff44 c06f7e45 c092b99c
c0874c24 dfc22cc0 c087379c dfc22cc0 dfc1ff54 c06f7e89 ffffffff 00000000
dfc1ff70 c06f3e55 c07da467 c092b99c dfc1ff7c dfc22cc0 c087379c dfc1ffa4
c043eba9 c07da8ae c0406fab c040b33b dfc10000 00000000 00000001 dfc1ff90
Call Trace:
[<c04023a7>] hypercall_page+0x3a7 <--
[<c04036f2>] xen_panic_event+0x1d
[<c06f7e45>] notifier_call_chain+0x26
[<c06f7e89>] atomic_notifier_call_chain+0xf
[<c06f3e55>] panic+0x59
[<c043eba9>] do_exit+0x5c
[<c0406fab>] xen_restore_fl_direct_reloc+0x4
[<c040b33b>] do_softirq+0xd5
[<c043f1f1>] sys_exit+0x13
[<c0409389>] syscall_call+0x7
-----------------------------------------------------------------------------
I also include some logs from console.
-------------------------------------------------------------------------------
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
nf_conntrack version 0.5.0 (7992 buckets, 31968 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
Bridge firewalling registered
Using IPI No-Shortcut mode
registered taskstats version 1
XENBUS: Device with no driver: device/vbd/51714
XENBUS: Device with no driver: device/vbd/51713
XENBUS: Device with no driver: device/console/0
Magic number: 1:252:3141
Freeing unused kernel memory: 464k freed
Write protecting the kernel text: 3048k
Write protecting the kernel read-only data: 1464k
Loading, please wait...
<30>udev[493]: starting version 167
Begin: Loading essential drivers ... JINHO: 1. xlblk_init called
JINHO: 2. xlblk_init called
JINHO: 3. xlblk_init called
blkfront: xvda2: barriers enabled (tag)
Setting capacity to 8388608
blkfront: xvda1: barriers enabled (tag)
Setting capacity to 2097152
xvda1: detected capacity change from 0 to 1073741824
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Running /scripts/local-premount ... done.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with writeback data mode.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
run-init: /sbin/init: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: run-init Not tainted 2.6.32.45 #1
Call Trace:
[<c06f3efc>] ? printk+0xf/0x13
[<c06f3e35>] panic+0x39/0xf1
[<c043eba9>] do_exit+0x5c/0x5cf
[<c0406fab>] ? xen_restore_fl_direct_end+0x0/0x1
[<c040b33b>] ? do_softirq+0xd5/0xde
[<c043f1f1>] complete_and_exit+0x0/0x17
[<c0409389>] syscall_call+0x7/0xb
------------------------------------------------------------------
Please help me to solve this problem. I have spent one week with this
problem.
Thank you,
Jinho
--
Jinho Hwang
PhD Student
Department of Computer Science
The George Washington University
Washington, DC 20052
hwang.jinho@gmail.com (email)
276.336.0971 (Cell)
202.994.4875 (fax)
070.8285.6546 (myLg070)
[-- Attachment #1.2: Type: text/html, Size: 4889 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xen-users] kernel panic in domU
2011-09-20 21:27 [Xen-users] kernel panic in domU jinho hwang
@ 2011-09-21 1:32 ` Jeremy Fitzhardinge
2011-09-21 2:18 ` jinho hwang
0 siblings, 1 reply; 4+ messages in thread
From: Jeremy Fitzhardinge @ 2011-09-21 1:32 UTC (permalink / raw)
To: jinho hwang; +Cc: xen-devel, xen-users
On 09/20/2011 02:27 PM, jinho hwang wrote:
>
> Hi All,
>
> I'm using xen 4.0.1, kernel 2.6.32.45 for DomU, kernel 2.6.32.46 for
> Dom0. I also use pygrub to boot the domU kernel in the xen. I tried
> all the things I know for making this work, but unfortunately it does
> not work at this moment.
> The kernel shows panic message and then escapes. The following is
> thetrace.. it tells me that the hypercall_page might trigger the
> xen_panic_event and then kernel got it to make itself panic.
>
> -----------------------------------------------------------------------------
> cs:eip: 0061:c04023a7 hypercall_page+0x3a7
> flags: 00001286 i s nz p
> ss:esp: 0069:dfc1ff14
> eax: 00000000 ebx: 00000002 ecx: dfc1ff18 edx: 00000000
> esi: 00000000 edi: 00000000 ebp: dfc1ff28
> ds: 007b es: 007b fs: 00d8 gs: 0000
> Code (instr addr c04023a7)
> cc cc cc cc cc cc cc cc cc cc cc cc cc cc b8 1d 00 00 00 cd 82 <c3> cc
> cc cc cc cc cc cc cc cc cc
>
>
> Stack:
> c04036f2 00000003 c086ecc8 00000000 00000000 dfc1ff44 c06f7e45 c092b99c
> c0874c24 dfc22cc0 c087379c dfc22cc0 dfc1ff54 c06f7e89 ffffffff 00000000
> dfc1ff70 c06f3e55 c07da467 c092b99c dfc1ff7c dfc22cc0 c087379c dfc1ffa4
> c043eba9 c07da8ae c0406fab c040b33b dfc10000 00000000 00000001 dfc1ff90
>
> Call Trace:
> [<c04023a7>] hypercall_page+0x3a7 <--
> [<c04036f2>] xen_panic_event+0x1d
> [<c06f7e45>] notifier_call_chain+0x26
> [<c06f7e89>] atomic_notifier_call_chain+0xf
> [<c06f3e55>] panic+0x59
> [<c043eba9>] do_exit+0x5c
> [<c0406fab>] xen_restore_fl_direct_reloc+0x4
> [<c040b33b>] do_softirq+0xd5
> [<c043f1f1>] sys_exit+0x13
> [<c0409389>] syscall_call+0x7
> -----------------------------------------------------------------------------
>
> I also include some logs from console.
>
> -------------------------------------------------------------------------------
> cpuidle: using governor ladder
> cpuidle: using governor menu
> usbcore: registered new interface driver hiddev
> usbcore: registered new interface driver usbhid
> usbhid: v2.6:USB HID core driver
> nf_conntrack version 0.5.0 (7992 buckets, 31968 max)
> CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
> nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
> sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
> ip_tables: (C) 2000-2006 Netfilter Core Team
> TCP cubic registered
> Initializing XFRM netlink socket
> NET: Registered protocol family 17
> Bridge firewalling registered
> Using IPI No-Shortcut mode
> registered taskstats version 1
> XENBUS: Device with no driver: device/vbd/51714
> XENBUS: Device with no driver: device/vbd/51713
> XENBUS: Device with no driver: device/console/0
> Magic number: 1:252:3141
> Freeing unused kernel memory: 464k freed
> Write protecting the kernel text: 3048k
> Write protecting the kernel read-only data: 1464k
> Loading, please wait...
> <30>udev[493]: starting version 167
> Begin: Loading essential drivers ... JINHO: 1. xlblk_init called
> JINHO: 2. xlblk_init called
> JINHO: 3. xlblk_init called
> blkfront: xvda2: barriers enabled (tag)
> Setting capacity to 8388608
> blkfront: xvda1: barriers enabled (tag)
> Setting capacity to 2097152
> xvda1: detected capacity change from 0 to 1073741824
> done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top
> ... done.
> Begin: Running /scripts/local-premount ... done.
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: mounted filesystem with writeback data mode.
> Begin: Running /scripts/local-bottom ... done.
> done.
> Begin: Running /scripts/init-bottom ... done.
> run-init: /sbin/init: No such file or directory
> Kernel panic - not syncing: Attempted to kill init!
> Pid: 1, comm: run-init Not tainted 2.6.32.45 #1
> Call Trace:
> [<c06f3efc>] ? printk+0xf/0x13
> [<c06f3e35>] panic+0x39/0xf1
> [<c043eba9>] do_exit+0x5c/0x5cf
> [<c0406fab>] ? xen_restore_fl_direct_end+0x0/0x1
> [<c040b33b>] ? do_softirq+0xd5/0xde
> [<c043f1f1>] complete_and_exit+0x0/0x17
> [<c0409389>] syscall_call+0x7/0xb
> ------------------------------------------------------------------
>
> Please help me to solve this problem. I have spent one week with this
> problem.
It looks like there's something wrong with your filesystem
configuration: it is missing an /sbin/init. When this fails to start,
the kernel panics as it has no way to start up the usermode environment
without it.
J
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [Xen-users] kernel panic in domU
2011-09-21 1:32 ` Jeremy Fitzhardinge
@ 2011-09-21 2:18 ` jinho hwang
2011-09-21 9:07 ` Ian Campbell
0 siblings, 1 reply; 4+ messages in thread
From: jinho hwang @ 2011-09-21 2:18 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: xen-devel, xen-users
[-- Attachment #1.1: Type: text/plain, Size: 5358 bytes --]
Thanks for replay. This is my fstab. Do I have to do something else for
mounting?
proc /proc proc defaults 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
/dev/xvda1 none swap sw 0 0
/dev/xvda2 / ext3 noatime,nodiratime,errors=remount-ro 0 1
Jinho
On Tue, Sep 20, 2011 at 9:32 PM, Jeremy Fitzhardinge <jeremy@goop.org>wrote:
> On 09/20/2011 02:27 PM, jinho hwang wrote:
> >
> > Hi All,
> >
> > I'm using xen 4.0.1, kernel 2.6.32.45 for DomU, kernel 2.6.32.46 for
> > Dom0. I also use pygrub to boot the domU kernel in the xen. I tried
> > all the things I know for making this work, but unfortunately it does
> > not work at this moment.
> > The kernel shows panic message and then escapes. The following is
> > thetrace.. it tells me that the hypercall_page might trigger the
> > xen_panic_event and then kernel got it to make itself panic.
> >
> >
> -----------------------------------------------------------------------------
> > cs:eip: 0061:c04023a7 hypercall_page+0x3a7
> > flags: 00001286 i s nz p
> > ss:esp: 0069:dfc1ff14
> > eax: 00000000 ebx: 00000002 ecx: dfc1ff18 edx: 00000000
> > esi: 00000000 edi: 00000000 ebp: dfc1ff28
> > ds: 007b es: 007b fs: 00d8 gs: 0000
> > Code (instr addr c04023a7)
> > cc cc cc cc cc cc cc cc cc cc cc cc cc cc b8 1d 00 00 00 cd 82 <c3> cc
> > cc cc cc cc cc cc cc cc cc
> >
> >
> > Stack:
> > c04036f2 00000003 c086ecc8 00000000 00000000 dfc1ff44 c06f7e45 c092b99c
> > c0874c24 dfc22cc0 c087379c dfc22cc0 dfc1ff54 c06f7e89 ffffffff 00000000
> > dfc1ff70 c06f3e55 c07da467 c092b99c dfc1ff7c dfc22cc0 c087379c dfc1ffa4
> > c043eba9 c07da8ae c0406fab c040b33b dfc10000 00000000 00000001 dfc1ff90
> >
> > Call Trace:
> > [<c04023a7>] hypercall_page+0x3a7 <--
> > [<c04036f2>] xen_panic_event+0x1d
> > [<c06f7e45>] notifier_call_chain+0x26
> > [<c06f7e89>] atomic_notifier_call_chain+0xf
> > [<c06f3e55>] panic+0x59
> > [<c043eba9>] do_exit+0x5c
> > [<c0406fab>] xen_restore_fl_direct_reloc+0x4
> > [<c040b33b>] do_softirq+0xd5
> > [<c043f1f1>] sys_exit+0x13
> > [<c0409389>] syscall_call+0x7
> >
> -----------------------------------------------------------------------------
> >
> > I also include some logs from console.
> >
> >
> -------------------------------------------------------------------------------
> > cpuidle: using governor ladder
> > cpuidle: using governor menu
> > usbcore: registered new interface driver hiddev
> > usbcore: registered new interface driver usbhid
> > usbhid: v2.6:USB HID core driver
> > nf_conntrack version 0.5.0 (7992 buckets, 31968 max)
> > CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
> > nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option
> or
> > sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
> > ip_tables: (C) 2000-2006 Netfilter Core Team
> > TCP cubic registered
> > Initializing XFRM netlink socket
> > NET: Registered protocol family 17
> > Bridge firewalling registered
> > Using IPI No-Shortcut mode
> > registered taskstats version 1
> > XENBUS: Device with no driver: device/vbd/51714
> > XENBUS: Device with no driver: device/vbd/51713
> > XENBUS: Device with no driver: device/console/0
> > Magic number: 1:252:3141
> > Freeing unused kernel memory: 464k freed
> > Write protecting the kernel text: 3048k
> > Write protecting the kernel read-only data: 1464k
> > Loading, please wait...
> > <30>udev[493]: starting version 167
> > Begin: Loading essential drivers ... JINHO: 1. xlblk_init called
> > JINHO: 2. xlblk_init called
> > JINHO: 3. xlblk_init called
> > blkfront: xvda2: barriers enabled (tag)
> > Setting capacity to 8388608
> > blkfront: xvda1: barriers enabled (tag)
> > Setting capacity to 2097152
> > xvda1: detected capacity change from 0 to 1073741824
> > done.
> > Begin: Running /scripts/init-premount ... done.
> > Begin: Mounting root file system ... Begin: Running /scripts/local-top
> > ... done.
> > Begin: Running /scripts/local-premount ... done.
> > kjournald starting. Commit interval 5 seconds
> > EXT3-fs: mounted filesystem with writeback data mode.
> > Begin: Running /scripts/local-bottom ... done.
> > done.
> > Begin: Running /scripts/init-bottom ... done.
> > run-init: /sbin/init: No such file or directory
> > Kernel panic - not syncing: Attempted to kill init!
> > Pid: 1, comm: run-init Not tainted 2.6.32.45 #1
> > Call Trace:
> > [<c06f3efc>] ? printk+0xf/0x13
> > [<c06f3e35>] panic+0x39/0xf1
> > [<c043eba9>] do_exit+0x5c/0x5cf
> > [<c0406fab>] ? xen_restore_fl_direct_end+0x0/0x1
> > [<c040b33b>] ? do_softirq+0xd5/0xde
> > [<c043f1f1>] complete_and_exit+0x0/0x17
> > [<c0409389>] syscall_call+0x7/0xb
> > ------------------------------------------------------------------
> >
> > Please help me to solve this problem. I have spent one week with this
> > problem.
>
> It looks like there's something wrong with your filesystem
> configuration: it is missing an /sbin/init. When this fails to start,
> the kernel panics as it has no way to start up the usermode environment
> without it.
>
> J
>
--
Jinho Hwang
PhD Student
Department of Computer Science
The George Washington University
Washington, DC 20052
hwang.jinho@gmail.com (email)
276.336.0971 (Cell)
202.994.4875 (fax)
070.8285.6546 (myLg070)
[-- Attachment #1.2: Type: text/html, Size: 6645 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xen-users] kernel panic in domU
2011-09-21 2:18 ` jinho hwang
@ 2011-09-21 9:07 ` Ian Campbell
0 siblings, 0 replies; 4+ messages in thread
From: Ian Campbell @ 2011-09-21 9:07 UTC (permalink / raw)
To: jinho hwang
Cc: Jeremy Fitzhardinge, xen-devel@lists.xensource.com,
xen-users@lists.xensource.com
Please don't top-post. See http://wiki.xen.org/xenwiki/ReportingBugs for
other list-etiquette pointers.
On Wed, 2011-09-21 at 03:18 +0100, jinho hwang wrote:
> Thanks for replay. This is my fstab. Do I have to do something else
> for mounting?
Do you have the necessary filesystem for xvda2 either builtin or modular
and loaded in your initramfs?
Are you sure /sbin/init exists in that filesystem? Please mount it in
dom0 and check.
Do you have the necessary personalty to run the binary? For example a 64
bit kernel with a 32 bit userspace will need CONFIG_IA32_EMULATION.
While you have the filesystem mounted in dom0 can you run "file
$MNT/sbin/init" to confirm what sort of binary it is.
Does using init=/bin/sh work for you?
Failing all that perhaps you can use whatever (distro-specific)
mechanism that is provided to allow you to break into a shell in the
initramfs and check out what it is doing, which modules it is loading
etc etc. You appear to be using Debian so I think "break=init" on the
kernel command line will cause you to drop to a shell just before
launching /sbin/init.
If none of this helps please post your guest config file and your kernel
config.
Ian.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-09-21 9:07 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-20 21:27 [Xen-users] kernel panic in domU jinho hwang
2011-09-21 1:32 ` Jeremy Fitzhardinge
2011-09-21 2:18 ` jinho hwang
2011-09-21 9:07 ` Ian Campbell
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.