Re: [Xen-users] Kernel Panic on DomU kernel which was custom compiled for Suse

[Sanjay Upadhyay <glowfriend@xxxxxxxxx>]

Hi Mustafa,
The Partition is being correctly specified. The Correct partition where Suse is installed is /dev/hda1. 
I have copied the /lib/modules/2.6.10-xenU folder from the Host machine to the Guest Machine too.

tried recompiling many times with as correctly everything possible.

thanks

On 11/22/05, Mustafa Abbasi <lordverminard@xxxxxxxxx> wrote:

On 11/22/05, Sanjay Upadhyay < glowfriend@xxxxxxxxx> wrote:

Hi folks,
Quickly,  what am i trying.

I have DomO machine on debian Sarge.
I have been able to run a DomU machine and install a basic Debian Sarge.
Now, I wanted to do a cross, run a Suse on DomU.
I installed Suse (very basic Install of 9.3 personall edition) on a
different partition.
I compiled the xen kernel from source.. and followed this post as it says..
http://lists.xensource.com/archives/html/xen-users/2005-09/msg00563.html
I included reiserfs to be compiled in the kernel.

Now I started the booting of DomU kernel I built, with a basic configuration

====Config====
kernel = "/boot/vmlinuz-2.6.10-xenU"
memory = 128
name = "suse"
vif = ['bridge=xen-br0']
disk = ['phy:/dev/hda1,hda1,r','phy:/dev/hda8,hda8,w']
ip=" 192.168.0.151"
netmask=" 255.255.255.0"
gateway="192.168.0.10"
hostname="tarooza"
root="/dev/hda1 ro"
extra="2"


=====Error=====
age 30, max trans age 30
ReiserFS: hda1: checking transaction log (hda1)
ReiserFS: hda1: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 144k freed
Warning: unable to open an initial console.
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
c025d5ba
*pde = ma 00000000 pa 55555000
[<c025d781>] vc_allocate+0xa1/0x1b0
[<c0467000>] reiserfs_xattr_register_handlers+0x90/0xf0
[<c0260d78>] con_open+0x48/0xc0
[<c0250a3d>] tty_open+0x22d/0x2b0
[<c0467000>] reiserfs_xattr_register_handlers+0x90/0xf0
[<c0467000>] reiserfs_xattr_register_handlers+0x90/0xf0
[<c0250810>] tty_open+0x0/0x2b0
[<c0159eee>] chrdev_open+0xae/0x150
[<c015095a>] dentry_open+0x12a/0x1d0
[<c0150828>] filp_open+0x68/0x70
[<c0150a3e>] get_unused_fd+0x3e/0xd0
[<c0150b69>] sys_open+0x49/0x90
[<c0109350>] syscall_call+0x7/0xb
Oops: 0000 [#1]
Modules linked in:
CPU:    0
EIP:    0061:[<c025d5ba>]    Not tainted VLI
EFLAGS: 00010246   (2.6.10-xenU )
EIP is at visual_init+0x5a/0x180
eax: 00000000   ebx: c05fbe00   ecx: 00000000   edx: c05fbe00
esi: 00000000   edi: 00000001   ebp: 00000000   esp: c0023e98
ds: 007b   es: 007b   ss: 0069
Process init (pid: 1, threadinfo=c0022000 task=c00799e0)
Stack: 00000000 000000d0 c05fbe00 00000000 c025d781 00000000 00000001 00000000
      c05e1dc0 00000000 00000000 c0467000 00400000 c0260d78 00000000 ffffffed
      c05fed80 00000001 c0250a3d c0467000 c05fed80 c0023ef4 00008102 c0467000
Call Trace:
[<c025d781>] vc_allocate+0xa1/0x1b0
[<c0467000>] reiserfs_xattr_register_handlers+0x90/0xf0
[<c0260d78>] con_open+0x48/0xc0
[<c0250a3d>] tty_open+0x22d/0x2b0
[<c0467000>] reiserfs_xattr_register_handlers+0x90/0xf0
[<c0467000>] reiserfs_xattr_register_handlers+0x90/0xf0
[<c0250810>] tty_open+0x0/0x2b0
[<c0159eee>] chrdev_open+0xae/0x150
[<c015095a>] dentry_open+0x12a/0x1d0
[<c0150828>] filp_open+0x68/0x70
[<c0150a3e>] get_unused_fd+0x3e/0xd0
[<c0150b69>] sys_open+0x49/0x90
[<c0109350>] syscall_call+0x7/0xb
Code: 40 8a 49 c0 a1 2c 8a 49 c0 89 42 28 8b 14 b5 80 9b 49 c0 85 d2
74 0a 8b 04 b5 40 8a 49 c0 89 50 28 8b 14 b5 40 8a 49 c0 8b 42 28 <8b>
18 85 db 74 1d 89 1c 24 e8 48 0b ed ff 85 c0 0f 84 e7 00 00
<0>Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 1 seconds..

not sure about thus case but kernel panic is normalt caused by the root partition being specified in correctly. maybe other cases as well but check if you are specidying the root correctly

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users