WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Kernel Panic on trying to boot domU

To: "Girish V" <girish.xen@xxxxxxxxx>
Subject: Re: [Xen-users] Kernel Panic on trying to boot domU
From: weiming <zephyr.zhao@xxxxxxxxx>
Date: Tue, 25 Mar 2008 10:29:25 -0400
Cc: Igor Chubin <igor@xxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 25 Mar 2008 07:30:20 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=AdQjS8BpMrcam1Hm/KoT2kcLuMAVVUMHWTyo8ZwgbNk=; b=S/9/jA1M+YPin9xxKeV71svvn81phuVJcAzRKwA2ixOim9jdbO6vyKr+cc0HbMmFPfZ1HzOBkZYTg0WsAIiwq0rSlHQqMrbk/3dJYkmWb77gjkZo59JrP4F2oIOrJQEXcD7qFJxjuUiif9pIP2dYgeuvBa4W4WGeRk+8BkPo0J4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=jPKKCSjVTH0rCVgkuLkfWOThMRoRpKPWvk7OZGhQVrOkE9wy6HlZmc2S223onV3WHAN5cRSAzP7rmoSMC3+0XP8W7XTh8RN5S4BBgs8FflayZ/QfbAcTD9pGClvnZPi0yhkTfpenk3Fxb5BTX05di8A13nh7W7reY1rxl06I1RM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <2122f0920803250635w6cd9498ua27c314af5641cca@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <2122f0920803191943w18e546cemdc711b4d2ec2e860@xxxxxxxxxxxxxx> <20080322180910.GC24600@xxxxxxx> <2122f0920803222130i1a0c3bfbv3021d76be1889611@xxxxxxxxxxxxxx> <20080323101732.GB24038@xxxxxxx> <2122f0920803250635w6cd9498ua27c314af5641cca@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
seems that the driver for your hard driver controllers was not included in the image file.

On Tue, Mar 25, 2008 at 9:35 AM, Girish V <girish.xen@xxxxxxxxx> wrote:
The bootup message after using the ramdisk is shown below.
Thanks
Girish
--------------------------------------------------------------------------------------------------------

[root@localhost second]# xm create -c file-config-rh9_diskimg
Using config file "./file-config-rh9_diskimg".
Started domain fc6_new
                      Linux version 2.6.18.8-xen (root@xxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-13)) #2 SMP Thu Mar 20 17:40:00 EDT 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
0MB HIGHMEM available.
264MB LOWMEM available.
ACPI in unprivileged domain disabled
Allocating PCI resources starting at 20000000 (gap: 10800000:ef800000)
Detected 3202.737 MHz processor.
Built 1 zonelists.  Total pages: 67584
Kernel command line: root=/dev/sda1 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Xen reported: 3200.114 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Software IO TLB disabled
vmalloc area: d1000000-f51fe000, maxmem 2d7fe000
Memory: 251788k/270336k available (2056k kernel code, 10352k reserved, 712k data, 196k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 6447.39 BogoMIPS (lpj=32236972)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 3552k freed
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen <tigran@xxxxxxxxxxx>
audit: initializing netlink socket (disabled)
audit(1206452738.073:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
Failed to obtain physical IRQ 6
floppy0: Unable to grab DMA2 for the floppy driver
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
xen-vbd: registered block device major 8
blkfront: sda1: barriers enabled
XENBUS: Device with no driver: device/console/0
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
Freeing unused kernel memory: 196k freed
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
Fusion MPT base driver 3.04.01
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SPI Host driver 3.04.01
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Kernel panic - not syncing: Attempted to kill init!
 


--------------------------------------------------------------------------------------------------------

On Sun, Mar 23, 2008 at 6:17 AM, Igor Chubin <igor@xxxxxxx> wrote:
On So, Mär 23, 2008 at 12:30:11 -0400, Girish V wrote:
> Hi Igor.
> Thanks for the suggestion. I did try using a ramdisk - and the bootup of the
> domU goes a little bit furter, but init still crashes with the same message
> as before.
> Any idea what I should do further?


What the last printed lines now?

> Thanks,
> Girish
>
> On Sat, Mar 22, 2008 at 2:09 PM, Igor Chubin <igor@xxxxxxx> wrote:
>
> > On Mi, Mär 19, 2008 at 10:43:25 -0400, Girish V wrote:
> > > Hello,
> >
> > Hello Girish,
> >
> > ...
> >
> >
> > Try to specify ramdisk here:
> >
> > (check path in my example)
> >
> > >
> > >
> > ----------------------------------------------------------------------------------------------------------------
> > >
> > > kernel = "/boot/vmlinuz-2.6.18.8-xen"
> > ramdisk = "/boot/initrd.img-2.6.18.8-xen"
> > > memory = 256
> > > name = "fc6"
> > > vif = [ 'bridge=xenbr0' ]
> > > disk = [ 'file:/second/fc6_domudisk,sda1,w' ]
> > > root = "/dev/sda1 ro"
> > >
> > ----------------------------------------------------------------------------------------------------------------
> > >
> > --
> > WBR, i.m.chubin
> >
> >

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

--
WBR, i.m.chubin



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

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