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-devel

Re: [Xen-devel] Xen 3.2 FC6 DomU Kernel Panic

To: "Mark Williamson" <mark.williamson@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.2 FC6 DomU Kernel Panic
From: "Girish V" <girish.xen@xxxxxxxxx>
Date: Tue, 8 Apr 2008 09:24:19 -0400
Cc: weiming <zephyr.zhao@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 08 Apr 2008 06:25:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=X8zFKaO8pc1AeKRaPqJiu5qSzRmfvLI8L/Osz38L5qk=; b=IdJ26ROXXQmMwEOKXkHg7dh5zowNqgkUUelY6Qn+/GbYXiNTZaw0z4eBR4oisrrv3LTTqniZAAQAqITFf7YyWmtGUdJX4Ye78CpxWx0Ga7POqx1/G4Od23s+qJpZQqfTlSOmnEU/Q53ukIPh32UgdVr4CMF4N5csrx8wqyf1suI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=uDPYFCyQ5Y6OSzIsZoy1bcHx1yNGmQ7x2yVg5vecw8y2uN3dKi+PpMnZf8EP0GmTI+KYLEqwPeXN+BJZ9AzJaklwpQ6tqHW8aHsjzdi0Ei60dSwRomk1uSCUpMowc57/1AVI8r3FFdoh+xS+Jh3QDo1LsTywecBJ4UYmHA7cvSs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200804062046.53929.mark.williamson@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <2122f0920803202010meba23d9w2f2a12528f471945@xxxxxxxxxxxxxx> <200804062046.53929.mark.williamson@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thank you for the reply. I was out of town for the weekend and could not reply earlier.

I have tried using a ramdisk - with builtin ide drivers, preloading xenblk and xennet modules - all the suggestions from xen mailing lists - but still no change.

Thanks,
Girish


On Sun, Apr 6, 2008 at 3:46 PM, Mark Williamson <mark.williamson@xxxxxxxxxxxx> wrote:
> 5) With this I tried to bring up the domU using the following configuration
> file. From what I understand, I can use the dom0 kernel itself for domU.
>
> ---------------------------------------------------------------------------
>-------------------------------------
>
> kernel = "/boot/vmlinuz-2.6.18.8-xen"
> memory = 256
> name = "fc6"
> vif = [ 'bridge=xenbr0' ]
> disk = [ 'file:/second/fc6_domudisk,sda1,w' ]
> root = "/dev/sda1 ro"
> ---------------------------------------------------------------------------
>-------------------------------------

You should use an initrd, since most modern distributions require one in order
to boot.  Add the line:

ramdisk = "/boot/initrd-3.2-xen.img"

to use the initrd from your host system (this should work, since as I
understand it you are using FC6 for both host and guest, am I right?)

I think I'd suggest you try that first and see if that changes the result.  If
you still have problems, post an update!

Hope that helps,

Cheers,
Mark

>
> But the boot fails with a kernel panic. The boot messages are listed below.
>
> ---------------------------------------------------------------------------
>--------------------------------------
>
> 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)) #1 SMP Mon Mar 17 20:26:25 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 4232.073 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.118 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: 255340k/270336k available (2056k kernel code, 6800k reserved, 716k
> data, 196k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
> Ok. calibrate_delay_direct() failed to get a good estimate for
> loops_per_jiffy. Probably due to long platform interrupts. Consider using
> "lpj=" boot option. 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
> 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(1423925502.304: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.
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as
> ext2
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 196k freed
> Kernel panic - not syncing: Attempted to kill init!
> ---------------------------------------------------------------------------
>--------------------------------------
>
> It would be great if someone could help me out.
>
> Thanks,
> Girish



--
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>