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-pvops dom0 booting issue

To: kishore kumar <bodkekumar@xxxxxxxxx>
Subject: Re: [Xen-devel] xen-pvops dom0 booting issue
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 29 Mar 2010 20:28:34 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 29 Mar 2010 11:14:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9f975f341003251637i3ef2cb89y776fcf61c1baf25a@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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <9f975f341003251637i3ef2cb89y776fcf61c1baf25a@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Thu, Mar 25, 2010 at 04:37:11PM -0700, kishore kumar wrote:
>    Hi,
> 
>    my grub.conf is as below
> 
>    kernel       /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all
>    sync_console console_to_ring com1=115200,8n1 console=vga,com1 lapic=debug
>    apic_verbosity=debug apic=debug iommu=1 msi=1
>    module       /vmlinuz-2.6.32.10 ro root=/dev/VolGroup00/LogVol01
>    console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10
>    module       /initrd-2.6.32.10.img
> 
>    I tried changing the root=/dev/VolGroup00/LogVol00 as well.
> 
>    ================================
>    1.  df -h gives me
> 
>    ===================================
> 
>    Filesystem Size Used Avail Use% Mounted on
> 
>    /dev/mapper/VolGroup00-LogVol00
> 
>    221G 11G 199G 6% /
> 
>    /dev/sda1 99M 34M 61M 36% /boot
> 
>    tmpfs 1.8G 0 1.8G 0% /dev/shm
> 
>    ===================================
>    2.  pvscan gives me
>    ===================================
>    PV /dev/sda2 VG VolGroup00 lvm2 [232.78 GB / 0 free]
> 
>    Total: 1 [232.78 GB] / in use: 1 [232.78 GB] / in no VG: 0 [0 ]
> 
>    ===================================
> 
>    3.  cat /etc/fstab gives mes
> 
>    ===================================
> 
>    /dev/VolGroup00/LogVol00 / ext3 defaults 1 1
> 
>    LABEL=/boot /boot ext3 defaults 1 2
> 
>    tmpfs /dev/shm tmpfs defaults 0 0
> 
>    devpts /dev/pts devpts gid=5,mode=620 0 0
> 
>    sysfs /sys sysfs defaults 0 0
> 
>    proc /proc proc defaults 0 0
> 
>    /dev/VolGroup00/LogVol01 swap swap defaults 0 0
> 
>    ===================================
> 
>    I get below message while booting
> 

Please paste the full boot messages.

>From this log we can't see if /dev/sda was detected or not. 
Is the disk driver included in the initrd image? 

When you generate the initrd image, run "mkinitrd -v" so 
you get verbose output of which drivers are included.

(rhel/centos/fedora mkinitrd reads the drivers needed from /etc/modprobe.conf)

-- Pasi

>    ===================================
> 
>    Reading all physical volumes.  This may take a while...
>    Activating logical volumes
>      Volume group "VolGroup00" not found
>    Trying to resume from /dev/VolGroup00/LogVol01
>    Unable to access resume device (/dev/VolGroup00/LogVol01)
>    Creating root device.
>    Mounting root filesystem.
>    mount: could not find filesystem '/dev/root'
>    Setting up other filesystems.
>    Setting up new root fs
>    setuproot: moving /dev failed: No such file or directory
>    no fstab.sys, mounting internal defaults
>    setuproot: error mounting /proc: No such file or directory
>    setuproot: error mounting /sys: No such file or directory
>    Switching to new root and running init.
>    unmounting old /dev
>    unmounting old /proc
>    unmounting old /sys
>    switchroot: mount failed: No such file or directory
>    init used greatest stack depth: 4088 bytes left
>    Kernel panic - not syncing: Attempted to kill init!
>    Pid: 1, comm: init Not tainted 2.6.32.10 #1
>    Call Trace:
>     [<ffffffff8105b743>] panic+0xa5/0x167
>     [<ffffffff8100ed91>] ? xen_force_evtchn_callback+0xd/0xf
>     [<ffffffff8105f2af>] ? do_exit+0x38a/0x701
>     [<ffffffff8100f44f>] ? xen_restore_fl_direct_end+0x0/0x1
>     [<ffffffff8108f81f>] ? lock_release+0x179/0x184
>     [<ffffffff8108ca21>] ? trace_hardirqs_on+0xd/0xf
>     [<ffffffff8147e77f>] ? _write_unlock_irq+0x37/0x3c
>     [<ffffffff8105efa3>] do_exit+0x7e/0x701
>     [<ffffffff8100f462>] ? check_events+0x12/0x20
>     [<ffffffff8105f6c2>] sys_exit_group+0x0/0x1b
>     [<ffffffff8105f6d9>] sys_exit_group+0x17/0x1b
>     [<ffffffff81012d72>] system_call_fastpath+0x16/0x1b
> 
>    Can you let me know what should be the grub.conf??

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


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

<Prev in Thread] Current Thread [Next in Thread>