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: "pradeep singh rautela" <rautelap@xxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.2 FC6 DomU Kernel Panic
From: "Girish V" <girish.xen@xxxxxxxxx>
Date: Fri, 21 Mar 2008 16:32:36 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 21 Mar 2008 13:33:01 -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=nX8zzp4LpaoosSgbmMmbZKNeIOYWwkZuUegNq5T6nTQ=; b=QdEmpGxkFET+2bDbvnQq3ZyKHQHCGXjybkpDwgIz7Acv5COjva7iXJg/INXNtS8jLWbD23CxsB1XD4j3yI/MC5XPwl4/E6jJ68xn8B/eGuKwwCJlmucvYY5arF83zyd7H09wHy2dleCxmW7yQwRe9OJNc2r8zCpZxDBBs/bgN1A=
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=R7YrE+qrIrRqiivcNEyMvem7vSXBJsVNQP+hhL72PuJGCtrSoVGizMNUPwucIiFwS1SJagY52zw+xl9lkmvmvYywH592b4u0KJ6n4qv7Ie/Wapu18qPED+FHkvHZr9KC5YQgJmBRWomG0MrxRwyNfTmW4KI3QkJVoFiyN9Tp1FA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <6bc632150803202259q19e08983pfb546acf055db6fc@xxxxxxxxxxxxxx>
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> <6bc632150803202259q19e08983pfb546acf055db6fc@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I tried compiling Xen 3.1.3 and tried to boot a domU using the same image (Of course, I replaced the xen 3.2 modules with the xen 3.1.3 modules in lib/modules of the image). I did not compile separate dom0 and domU kernels, but used the same unified kernel for both dom0 and domU and this works.

But, as I mentioned in my previous email, the same procedure does not work on Xen 3.2. The dom0 boots but the domU kernel panics and crashes.

It would be great if someone who has compiled Xen 32 and booted a guest dom helped me out with instructions.

Thanks,
Girish


On Fri, Mar 21, 2008 at 1:59 AM, pradeep singh rautela <rautelap@xxxxxxxxx> wrote:
May be you need to recompiled the domainU PV kernel with ext3/ext2
modules statically built into the kernel. Also IDE/SATA driver it
seems.

HTH

thanks,
             --Pradeep

On 21/03/2008, Girish V <girish.xen@xxxxxxxxx> wrote:
> Hello,
> I am trying to boot a FC6 domU on Xen 3.2 (compiled on a FC6 system).
>
> After compiling Xen 3.2 successfully on FC6 and making the ramdisk, I
> modified the conf.grub as shown below. With this, I was able to boot xen.
>
> ------------------------------
> ---------------------------------------------------------------------------------
>
>
> # grub.conf generated by anaconda
>  #
>  # Note that you do not have to rerun grub after making changes to this file
>  # NOTICE:  You do not have a /boot partition.  This means that
>  #          all kernel and initrd paths are relative to /, eg.
>  #          root (hd0,0)
>  #          kernel /boot/vmlinuz-version ro root=/dev/sda1
>  #          initrd /boot/initrd-version.img
>  #boot=/dev/sda
>  default=0
>  timeout=5
>  splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>  hiddenmenu
>  title Xen 3.2 (2.6.18.8-xen)
>        root (hd0,0)
>        kernel /boot/xen.gz dom0_mem=1024M console=vga
>        module /boot/vmlinuz-2.6.18.8-xen ro root=LABEL=/1 console=tty0
>        module /boot/initrd-3.2-xen.img
>  title Fedora Core (2.6.18-1.2798.fc6)
>        root (hd0,0)
>        kernel /boot/vmlinuz-2.6.18-1.2798.fc6 ro root=LABEL=/1 rhgb quiet
>        initrd /boot/initrd-2.6.18-1.2798.fc6.img
> ---------------------------------------------------------------------------------------------------------------
>
>
> Then, I created a domU image as in the uer manual for v3.0.
>
> 1) I created a blank discimage fc6_domudisk and monted in in /mnt
> 2) I copied /{root, dev,var,etc,usr,bin,sbin,lib} to /mnt
> 3) I makde the {home, proc, sys, tmp} directories inside /mnt
>  4) I modified the mnt/etc/fstab as follows
> ----------------------------------------------------------------------------------------------------------------
>
>
> /dev/sda1                /                       ext3    defaults        1 1
>  devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
>  tmpfs                   /dev/shm                tmpfs   defaults        0 0
>  proc                    /proc                   proc    defaults        0 0
>  sysfs                   /sys                    sysfs   defaults        0 0
> ---------------------------------------------------------------------------------------------------------------
>
> 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"
> ----------------------------------------------------------------------------------------------------------------
>
> 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
> _______________________________________________
>  Xen-devel mailing list
>  Xen-devel@xxxxxxxxxxxxxxxxxxx
>  http://lists.xensource.com/xen-devel
>
>


--
Pradeep Singh Rautela
http://eagain.wordpress.com
http://emptydomain.googlepages.com

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