Xen users - Aug 2009 - 3.4-testing : Kernel panic on bootup (mount: could not find filesystem /dev/root/)

Hi,

I installed XEN 3.4-testing version without much problems in CentOS 5.3
running on quadcore Intel Nahelam processors using the following
installation
steps (as in the README) :

<steps>
hg clone http://xenbits.xensource.com/xen-3.4-testing.hg`
cd xen-unstable.hg
make world
make install
make linux-2.6-xen-config CONFIGMODE=menuconfig
make linux-2.6-xen-build
make linux-2.6-xen-install
depmod 2.6.18.8-xen
mkinitrd -v -f --with=ahci --with=sd_mod --with=scsi_mod --allow-missing
initrd-2.6.18-xen.img 2.6.18.8-xen
cp initrd-2.6.18-xen.img /boot
</steps>

After the installation, I updated the grub with the following entry :

<grub.conf>
title  Xen 3.4.2
        root (hd0,0)
        kernel /xen.gz loglvl=all guest_loglvl=all vtd=1 iommu=1
        module /vmlinuz-2.6.18.8-xen root=LABEL=/ apic=debug maxcpus=8
        module /initrd-2.6.18-xen.img
<grub.conf>
But during the bootup, I see Kernel panic with the only error above that
being :

<error>
mount: could not find filesystem /dev/root/
setuproot: moving /dev failed: No such file or Directory
no fstub.sys, mounting internal defaults
setuproot: error mounting /proc:No such file or directory
</error>

Is it an error in partition ? or a Grub entry error ?
Or an installation error ?

Can someone help me ?

Thanks,
Madhu

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

Anyone ?
I searched the forums, but couldn''t find a solution to the problem am
facing.

-Madhu
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> bounces@lists.xensource.com] On Behalf Of Madhu Venugopal (vmadhu)
> Sent: Tuesday, August 25, 2009 3:43 PM
> To: Xen User-List
> Subject: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
could
> notfind filesystem /dev/root/)
> 
> Hi,
> 
> I installed XEN 3.4-testing version without much problems in CentOS
5.3
> running on quadcore Intel Nahelam processors using the following
> installation
> steps (as in the README) :
> 
> <steps>
> hg clone http://xenbits.xensource.com/xen-3.4-testing.hg`
> cd xen-unstable.hg
> make world
> make install
> make linux-2.6-xen-config CONFIGMODE=menuconfig
> make linux-2.6-xen-build
> make linux-2.6-xen-install
> depmod 2.6.18.8-xen
> mkinitrd -v -f --with=ahci --with=sd_mod --with=scsi_mod --allow-
> missing
> initrd-2.6.18-xen.img 2.6.18.8-xen
> cp initrd-2.6.18-xen.img /boot
> </steps>
> 
> After the installation, I updated the grub with the following entry :
> 
> <grub.conf>
> title  Xen 3.4.2
>         root (hd0,0)
>         kernel /xen.gz loglvl=all guest_loglvl=all vtd=1 iommu=1
>         module /vmlinuz-2.6.18.8-xen root=LABEL=/ apic=debug maxcpus=8
>         module /initrd-2.6.18-xen.img
> <grub.conf>
> But during the bootup, I see Kernel panic with the only error above
> that
> being :
> 
> <error>
> mount: could not find filesystem /dev/root/
> setuproot: moving /dev failed: No such file or Directory
> no fstub.sys, mounting internal defaults
> setuproot: error mounting /proc:No such file or directory
> </error>
> 
> Is it an error in partition ? or a Grub entry error ?
> Or an installation error ?
> 
> Can someone help me ?
> 
> Thanks,
> Madhu
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Look at your grub config.

Root=/LABEL=/ looks way wrong.

It should point to something in the /dev directory.

In my case my hard drive that has the / file system on it is /dev/sdc1

Look at your other grub configs for your other WORKING kernels and make the
root=/ section of your grub config the same as what those kernels read.


-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Madhu Venugopal
(vmadhu)
Sent: Wednesday, August 26, 2009 9:03 AM
To: Xen User-List
Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
couldnotfind filesystem /dev/root/)

Anyone ?
I searched the forums, but couldn''t find a solution to the problem am
facing.

-Madhu
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> bounces@lists.xensource.com] On Behalf Of Madhu Venugopal (vmadhu)
> Sent: Tuesday, August 25, 2009 3:43 PM
> To: Xen User-List
> Subject: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
could
> notfind filesystem /dev/root/)
> 
> Hi,
> 
> I installed XEN 3.4-testing version without much problems in CentOS
5.3
> running on quadcore Intel Nahelam processors using the following
> installation
> steps (as in the README) :
> 
> <steps>
> hg clone http://xenbits.xensource.com/xen-3.4-testing.hg`
> cd xen-unstable.hg
> make world
> make install
> make linux-2.6-xen-config CONFIGMODE=menuconfig
> make linux-2.6-xen-build
> make linux-2.6-xen-install
> depmod 2.6.18.8-xen
> mkinitrd -v -f --with=ahci --with=sd_mod --with=scsi_mod --allow-
> missing
> initrd-2.6.18-xen.img 2.6.18.8-xen
> cp initrd-2.6.18-xen.img /boot
> </steps>
> 
> After the installation, I updated the grub with the following entry :
> 
> <grub.conf>
> title  Xen 3.4.2
>         root (hd0,0)
>         kernel /xen.gz loglvl=all guest_loglvl=all vtd=1 iommu=1
>         module /vmlinuz-2.6.18.8-xen root=LABEL=/ apic=debug maxcpus=8
>         module /initrd-2.6.18-xen.img
> <grub.conf>
> But during the bootup, I see Kernel panic with the only error above
> that
> being :
> 
> <error>
> mount: could not find filesystem /dev/root/
> setuproot: moving /dev failed: No such file or Directory
> no fstub.sys, mounting internal defaults
> setuproot: error mounting /proc:No such file or directory
> </error>
> 
> Is it an error in partition ? or a Grub entry error ?
> Or an installation error ?
> 
> Can someone help me ?
> 
> Thanks,
> Madhu
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users




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

Hi Robbie,

Thanks for your response.
I tried all forms... but none of them worked :-(

The Only other Grub config I have is as follows and the XEN Grub config
follows this approach.

<grub>
title CentOS (2.6.18-128.el5PAE)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-128.el5PAE ro root=LABEL=/1 rhgb quiet
        initrd /initrd-2.6.18-128.el5PAE.img
<grub>

As I mentioned, I tried the physical /dev locations as well, but that 
didn''t help... But never tried "/". I can give that a shot
today.

Any other suggestions (or) possible problems ?

FYI, the GRUB config that I posted worked fine on another system with
Similar installation for 1 of my colleagues.

-Madhu
> -----Original Message-----
> From: Robbie Garrett [mailto:rgarrett@hostourweb.com]
> Sent: Wednesday, August 26, 2009 6:11 AM
> To: Madhu Venugopal (vmadhu); ''Xen User-List''
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> Look at your grub config.
> 
> Root=/LABEL=/ looks way wrong.
> 
> It should point to something in the /dev directory.
> 
> In my case my hard drive that has the / file system on it is /dev/sdc1
> 
> Look at your other grub configs for your other WORKING kernels and
make
> the
> root=/ section of your grub config the same as what those kernels
read.
> 
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Madhu
> Venugopal
> (vmadhu)
> Sent: Wednesday, August 26, 2009 9:03 AM
> To: Xen User-List
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> Anyone ?
> I searched the forums, but couldn''t find a solution to the problem
am
> facing.
> 
> -Madhu
> 
> > -----Original Message-----
> > From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> > bounces@lists.xensource.com] On Behalf Of Madhu Venugopal (vmadhu)
> > Sent: Tuesday, August 25, 2009 3:43 PM
> > To: Xen User-List
> > Subject: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> could
> > notfind filesystem /dev/root/)
> >
> > Hi,
> >
> > I installed XEN 3.4-testing version without much problems in CentOS
> 5.3
> > running on quadcore Intel Nahelam processors using the following
> > installation
> > steps (as in the README) :
> >
> > <steps>
> > hg clone http://xenbits.xensource.com/xen-3.4-testing.hg`
> > cd xen-unstable.hg
> > make world
> > make install
> > make linux-2.6-xen-config CONFIGMODE=menuconfig
> > make linux-2.6-xen-build
> > make linux-2.6-xen-install
> > depmod 2.6.18.8-xen
> > mkinitrd -v -f --with=ahci --with=sd_mod --with=scsi_mod --allow-
> > missing
> > initrd-2.6.18-xen.img 2.6.18.8-xen
> > cp initrd-2.6.18-xen.img /boot
> > </steps>
> >
> > After the installation, I updated the grub with the following entry
:
> >
> > <grub.conf>
> > title  Xen 3.4.2
> >         root (hd0,0)
> >         kernel /xen.gz loglvl=all guest_loglvl=all vtd=1 iommu=1
> >         module /vmlinuz-2.6.18.8-xen root=LABEL=/ apic=debug
> maxcpus=8
> >         module /initrd-2.6.18-xen.img
> > <grub.conf>
> > But during the bootup, I see Kernel panic with the only error above
> > that
> > being :
> >
> > <error>
> > mount: could not find filesystem /dev/root/
> > setuproot: moving /dev failed: No such file or Directory
> > no fstub.sys, mounting internal defaults
> > setuproot: error mounting /proc:No such file or directory
> > </error>
> >
> > Is it an error in partition ? or a Grub entry error ?
> > Or an installation error ?
> >
> > Can someone help me ?
> >
> > Thanks,
> > Madhu
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 

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

Hi,

I started everything from scratch...

1. Installed CentOS 5.3
2. Installed XEN 3.4-testing as per README

The same problem during the reboot. I copied the Grub entry from the
Native CentOS5.3 installation.

This time am seeing an error additional error :

"Volume group : "VolGroup00" not Found"

Searching the forums, I understand that this is a Logical Volume and
There are a few problems with Logical Volumes. But none of the
workarounds
Seems to work.

I get a feeling that the "mkinitrd" is not doing its job completely.
(or) what am I missing ?

Can someone help me please ?

-Madhu
> -----Original Message-----
> From: Robbie Garrett [mailto:rgarrett@hostourweb.com]
> Sent: Wednesday, August 26, 2009 6:11 AM
> To: Madhu Venugopal (vmadhu); ''Xen User-List''
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> Look at your grub config.
> 
> Root=/LABEL=/ looks way wrong.
> 
> It should point to something in the /dev directory.
> 
> In my case my hard drive that has the / file system on it is /dev/sdc1
> 
> Look at your other grub configs for your other WORKING kernels and
make
> the
> root=/ section of your grub config the same as what those kernels
read.
> 
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Madhu
> Venugopal
> (vmadhu)
> Sent: Wednesday, August 26, 2009 9:03 AM
> To: Xen User-List
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> Anyone ?
> I searched the forums, but couldn''t find a solution to the problem
am
> facing.
> 
> -Madhu
> 
> > -----Original Message-----
> > From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> > bounces@lists.xensource.com] On Behalf Of Madhu Venugopal (vmadhu)
> > Sent: Tuesday, August 25, 2009 3:43 PM
> > To: Xen User-List
> > Subject: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> could
> > notfind filesystem /dev/root/)
> >
> > Hi,
> >
> > I installed XEN 3.4-testing version without much problems in CentOS
> 5.3
> > running on quadcore Intel Nahelam processors using the following
> > installation
> > steps (as in the README) :
> >
> > <steps>
> > hg clone http://xenbits.xensource.com/xen-3.4-testing.hg`
> > cd xen-unstable.hg
> > make world
> > make install
> > make linux-2.6-xen-config CONFIGMODE=menuconfig
> > make linux-2.6-xen-build
> > make linux-2.6-xen-install
> > depmod 2.6.18.8-xen
> > mkinitrd -v -f --with=ahci --with=sd_mod --with=scsi_mod --allow-
> > missing
> > initrd-2.6.18-xen.img 2.6.18.8-xen
> > cp initrd-2.6.18-xen.img /boot
> > </steps>
> >
> > After the installation, I updated the grub with the following entry
:
> >
> > <grub.conf>
> > title  Xen 3.4.2
> >         root (hd0,0)
> >         kernel /xen.gz loglvl=all guest_loglvl=all vtd=1 iommu=1
> >         module /vmlinuz-2.6.18.8-xen root=LABEL=/ apic=debug
> maxcpus=8
> >         module /initrd-2.6.18-xen.img
> > <grub.conf>
> > But during the bootup, I see Kernel panic with the only error above
> > that
> > being :
> >
> > <error>
> > mount: could not find filesystem /dev/root/
> > setuproot: moving /dev failed: No such file or Directory
> > no fstub.sys, mounting internal defaults
> > setuproot: error mounting /proc:No such file or directory
> > </error>
> >
> > Is it an error in partition ? or a Grub entry error ?
> > Or an installation error ?
> >
> > Can someone help me ?
> >
> > Thanks,
> > Madhu
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 

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

Try the same results with 3.4.1 and not 3.4-testing.

Lots of people use centos with no issues.

Below is my grub config for debian 5.0

title           Xen 3.4.1 / Debian GNU/Linux, kernel 2.6.18.8-xen
root            (hd2,0)
kernel          /boot/xen-3.4.1.gz
module          /boot/vmlinuz-2.6.18.8-xen root=/dev/sdc1 ro console=tty0
max_loop=64 #for some reason this lines raps. It should be just after
console=tty on the same line.
module          /boot/initrd.img-2.6.18.8-xen

-----Original Message-----
From: Madhu Venugopal (vmadhu) [mailto:vmadhu@cisco.com] 
Sent: Wednesday, August 26, 2009 3:57 PM
To: Robbie Garrett; Xen User-List
Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
couldnotfind filesystem /dev/root/)

Hi,

I started everything from scratch...

1. Installed CentOS 5.3
2. Installed XEN 3.4-testing as per README

The same problem during the reboot. I copied the Grub entry from the
Native CentOS5.3 installation.

This time am seeing an error additional error :

"Volume group : "VolGroup00" not Found"

Searching the forums, I understand that this is a Logical Volume and
There are a few problems with Logical Volumes. But none of the
workarounds
Seems to work.

I get a feeling that the "mkinitrd" is not doing its job completely.
(or) what am I missing ?

Can someone help me please ?

-Madhu
> -----Original Message-----
> From: Robbie Garrett [mailto:rgarrett@hostourweb.com]
> Sent: Wednesday, August 26, 2009 6:11 AM
> To: Madhu Venugopal (vmadhu); ''Xen User-List''
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> Look at your grub config.
> 
> Root=/LABEL=/ looks way wrong.
> 
> It should point to something in the /dev directory.
> 
> In my case my hard drive that has the / file system on it is /dev/sdc1
> 
> Look at your other grub configs for your other WORKING kernels and
make
> the
> root=/ section of your grub config the same as what those kernels
read.
> 
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Madhu
> Venugopal
> (vmadhu)
> Sent: Wednesday, August 26, 2009 9:03 AM
> To: Xen User-List
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> Anyone ?
> I searched the forums, but couldn''t find a solution to the problem
am
> facing.
> 
> -Madhu
> 
> > -----Original Message-----
> > From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> > bounces@lists.xensource.com] On Behalf Of Madhu Venugopal (vmadhu)
> > Sent: Tuesday, August 25, 2009 3:43 PM
> > To: Xen User-List
> > Subject: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> could
> > notfind filesystem /dev/root/)
> >
> > Hi,
> >
> > I installed XEN 3.4-testing version without much problems in CentOS
> 5.3
> > running on quadcore Intel Nahelam processors using the following
> > installation
> > steps (as in the README) :
> >
> > <steps>
> > hg clone http://xenbits.xensource.com/xen-3.4-testing.hg`
> > cd xen-unstable.hg
> > make world
> > make install
> > make linux-2.6-xen-config CONFIGMODE=menuconfig
> > make linux-2.6-xen-build
> > make linux-2.6-xen-install
> > depmod 2.6.18.8-xen
> > mkinitrd -v -f --with=ahci --with=sd_mod --with=scsi_mod --allow-
> > missing
> > initrd-2.6.18-xen.img 2.6.18.8-xen
> > cp initrd-2.6.18-xen.img /boot
> > </steps>
> >
> > After the installation, I updated the grub with the following entry
:
> >
> > <grub.conf>
> > title  Xen 3.4.2
> >         root (hd0,0)
> >         kernel /xen.gz loglvl=all guest_loglvl=all vtd=1 iommu=1
> >         module /vmlinuz-2.6.18.8-xen root=LABEL=/ apic=debug
> maxcpus=8
> >         module /initrd-2.6.18-xen.img
> > <grub.conf>
> > But during the bootup, I see Kernel panic with the only error above
> > that
> > being :
> >
> > <error>
> > mount: could not find filesystem /dev/root/
> > setuproot: moving /dev failed: No such file or Directory
> > no fstub.sys, mounting internal defaults
> > setuproot: error mounting /proc:No such file or directory
> > </error>
> >
> > Is it an error in partition ? or a Grub entry error ?
> > Or an installation error ?
> >
> > Can someone help me ?
> >
> > Thanks,
> > Madhu
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 




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

Hi Robbie,


I had this exact same problem, tried for 5-10 hours to fix but never got
Xen Dom working with LVM.

Try installing Centos on a standard partition rather than the default
LVM scheme, it fixed it for me. You can still use LVM partitions for
your VMs with this setup.


Rob

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Robbie
Garrett
Sent: 27 August 2009 13:24
To: ''Madhu Venugopal (vmadhu)''; ''Xen
User-List''
Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup
(mount:couldnotfind filesystem /dev/root/)

Try the same results with 3.4.1 and not 3.4-testing.

Lots of people use centos with no issues.

Below is my grub config for debian 5.0

title           Xen 3.4.1 / Debian GNU/Linux, kernel 2.6.18.8-xen
root            (hd2,0)
kernel          /boot/xen-3.4.1.gz
module          /boot/vmlinuz-2.6.18.8-xen root=/dev/sdc1 ro
console=tty0
max_loop=64 #for some reason this lines raps. It should be just after
console=tty on the same line.
module          /boot/initrd.img-2.6.18.8-xen

-----Original Message-----
From: Madhu Venugopal (vmadhu) [mailto:vmadhu@cisco.com] 
Sent: Wednesday, August 26, 2009 3:57 PM
To: Robbie Garrett; Xen User-List
Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
couldnotfind filesystem /dev/root/)

Hi,

I started everything from scratch...

1. Installed CentOS 5.3
2. Installed XEN 3.4-testing as per README

The same problem during the reboot. I copied the Grub entry from the
Native CentOS5.3 installation.

This time am seeing an error additional error :

"Volume group : "VolGroup00" not Found"

Searching the forums, I understand that this is a Logical Volume and
There are a few problems with Logical Volumes. But none of the
workarounds
Seems to work.

I get a feeling that the "mkinitrd" is not doing its job completely.
(or) what am I missing ?

Can someone help me please ?

-Madhu
> -----Original Message-----
> From: Robbie Garrett [mailto:rgarrett@hostourweb.com]
> Sent: Wednesday, August 26, 2009 6:11 AM
> To: Madhu Venugopal (vmadhu); ''Xen User-List''
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> Look at your grub config.
> 
> Root=/LABEL=/ looks way wrong.
> 
> It should point to something in the /dev directory.
> 
> In my case my hard drive that has the / file system on it is /dev/sdc1
> 
> Look at your other grub configs for your other WORKING kernels and
make
> the
> root=/ section of your grub config the same as what those kernels
read.
> 
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Madhu
> Venugopal
> (vmadhu)
> Sent: Wednesday, August 26, 2009 9:03 AM
> To: Xen User-List
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> Anyone ?
> I searched the forums, but couldn''t find a solution to the problem
am
> facing.
> 
> -Madhu
> 
> > -----Original Message-----
> > From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> > bounces@lists.xensource.com] On Behalf Of Madhu Venugopal (vmadhu)
> > Sent: Tuesday, August 25, 2009 3:43 PM
> > To: Xen User-List
> > Subject: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> could
> > notfind filesystem /dev/root/)
> >
> > Hi,
> >
> > I installed XEN 3.4-testing version without much problems in CentOS
> 5.3
> > running on quadcore Intel Nahelam processors using the following
> > installation
> > steps (as in the README) :
> >
> > <steps>
> > hg clone http://xenbits.xensource.com/xen-3.4-testing.hg`
> > cd xen-unstable.hg
> > make world
> > make install
> > make linux-2.6-xen-config CONFIGMODE=menuconfig
> > make linux-2.6-xen-build
> > make linux-2.6-xen-install
> > depmod 2.6.18.8-xen
> > mkinitrd -v -f --with=ahci --with=sd_mod --with=scsi_mod --allow-
> > missing
> > initrd-2.6.18-xen.img 2.6.18.8-xen
> > cp initrd-2.6.18-xen.img /boot
> > </steps>
> >
> > After the installation, I updated the grub with the following entry
:
> >
> > <grub.conf>
> > title  Xen 3.4.2
> >         root (hd0,0)
> >         kernel /xen.gz loglvl=all guest_loglvl=all vtd=1 iommu=1
> >         module /vmlinuz-2.6.18.8-xen root=LABEL=/ apic=debug
> maxcpus=8
> >         module /initrd-2.6.18-xen.img
> > <grub.conf>
> > But during the bootup, I see Kernel panic with the only error above
> > that
> > being :
> >
> > <error>
> > mount: could not find filesystem /dev/root/
> > setuproot: moving /dev failed: No such file or Directory
> > no fstub.sys, mounting internal defaults
> > setuproot: error mounting /proc:No such file or directory
> > </error>
> >
> > Is it an error in partition ? or a Grub entry error ?
> > Or an installation error ?
> >
> > Can someone help me ?
> >
> > Thanks,
> > Madhu
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 




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

The SAQ Group

Registered Office: 18 Chapel Street, Petersfield, Hampshire GU32 3DZ
SAQ is the trading name of SEMTEC Limited. Registered in England & Wales
Company Number: 06481952

http://www.saqnet.co.uk AS29219

SAQ Group Delivers high quality, honestly priced communication and I.T. services
to UK Business.

Broadband : Domains : Email : Hosting : CoLo : Servers : Racks : Transit :
Backups : Managed Networks : Remote Support.

ISPA Member


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

On Thu, Aug 27, 2009 at 2:56 AM, Madhu Venugopal
(vmadhu)<vmadhu@cisco.com> wrote:
> Hi,
>
> I started everything from scratch...
>
> 1. Installed CentOS 5.3
> 2. Installed XEN 3.4-testing as per README
>
> The same problem during the reboot. I copied the Grub entry from the
> Native CentOS5.3 installation.
On your original setup, I noticed you''re using
"root=LABEL=/1" on the
original grub stanza and "root=LABEL=/" on Xen stanza. Are they
supposed to refer to the same root? This could be one of things
causing you problems.
>
> This time am seeing an error additional error :
>
> "Volume group : "VolGroup00" not Found"
>
> Searching the forums, I understand that this is a Logical Volume and
> There are a few problems with Logical Volumes. But none of the
> workarounds
> Seems to work.
>
> I get a feeling that the "mkinitrd" is not doing its job
completely.
> (or) what am I missing ?
My guess is the kernel config you use is missing some essential
modules needed to boot correctly. Here''s some of the things you can
try :

- Install RHEL''s Xen. This should be pretty straightforward,
you''d end
up with Xen 3.1+ and a working grub.conf stanza for Xen with RHEL''s
kernel-xen
- Install Xen package from gitco (http://www.gitco.de/repo/). You can
get Xen 3.4.1 (currently in testing) but still using RHEL''s kernel-xen
- If that works, you can simply compile another xen kernel as you
like, using either 2.6.18 or later pv_ops kernel. If using 2.6.18, you
can use RHEL''s kernel-xen config as a base.

-- 
Fajar

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

Hi Rob,

I started everything from scratch ... this time with Physical partitions
(without the LVM).

But the result is the same... Kernel panic !

I think am missing some driver as others suggested. But not sure what am
Missing :-(. How can I figure it out ?

-Madhu
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> bounces@lists.xensource.com] On Behalf Of Robert Dunkley
> Sent: Thursday, August 27, 2009 5:37 AM
> To: Robbie Garrett; Madhu Venugopal (vmadhu); Xen User-List
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on
> bootup(mount:couldnotfind filesystem /dev/root/)
> 
> Hi Robbie,
> 
> 
> I had this exact same problem, tried for 5-10 hours to fix but never
> got
> Xen Dom working with LVM.
> 
> Try installing Centos on a standard partition rather than the default
> LVM scheme, it fixed it for me. You can still use LVM partitions for
> your VMs with this setup.
> 
> 
> Rob
> 
> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Robbie
> Garrett
> Sent: 27 August 2009 13:24
> To: ''Madhu Venugopal (vmadhu)''; ''Xen
User-List''
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup
> (mount:couldnotfind filesystem /dev/root/)
> 
> Try the same results with 3.4.1 and not 3.4-testing.
> 
> Lots of people use centos with no issues.
> 
> Below is my grub config for debian 5.0
> 
> title           Xen 3.4.1 / Debian GNU/Linux, kernel 2.6.18.8-xen
> root            (hd2,0)
> kernel          /boot/xen-3.4.1.gz
> module          /boot/vmlinuz-2.6.18.8-xen root=/dev/sdc1 ro
> console=tty0
> max_loop=64 #for some reason this lines raps. It should be just after
> console=tty on the same line.
> module          /boot/initrd.img-2.6.18.8-xen
> 
> -----Original Message-----
> From: Madhu Venugopal (vmadhu) [mailto:vmadhu@cisco.com]
> Sent: Wednesday, August 26, 2009 3:57 PM
> To: Robbie Garrett; Xen User-List
> Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> Hi,
> 
> I started everything from scratch...
> 
> 1. Installed CentOS 5.3
> 2. Installed XEN 3.4-testing as per README
> 
> The same problem during the reboot. I copied the Grub entry from the
> Native CentOS5.3 installation.
> 
> This time am seeing an error additional error :
> 
> "Volume group : "VolGroup00" not Found"
> 
> Searching the forums, I understand that this is a Logical Volume and
> There are a few problems with Logical Volumes. But none of the
> workarounds
> Seems to work.
> 
> I get a feeling that the "mkinitrd" is not doing its job
completely.
> (or) what am I missing ?
> 
> Can someone help me please ?
> 
> -Madhu
> 
> > -----Original Message-----
> > From: Robbie Garrett [mailto:rgarrett@hostourweb.com]
> > Sent: Wednesday, August 26, 2009 6:11 AM
> > To: Madhu Venugopal (vmadhu); ''Xen User-List''
> > Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup
(mount:
> > couldnotfind filesystem /dev/root/)
> >
> > Look at your grub config.
> >
> > Root=/LABEL=/ looks way wrong.
> >
> > It should point to something in the /dev directory.
> >
> > In my case my hard drive that has the / file system on it is
> /dev/sdc1
> >
> > Look at your other grub configs for your other WORKING kernels and
> make
> > the
> > root=/ section of your grub config the same as what those kernels
> read.
> >
> >
> > -----Original Message-----
> > From: xen-users-bounces@lists.xensource.com
> > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Madhu
> > Venugopal
> > (vmadhu)
> > Sent: Wednesday, August 26, 2009 9:03 AM
> > To: Xen User-List
> > Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup
(mount:
> > couldnotfind filesystem /dev/root/)
> >
> > Anyone ?
> > I searched the forums, but couldn''t find a solution to the
problem
am
> > facing.
> >
> > -Madhu
> >
> > > -----Original Message-----
> > > From: xen-users-bounces@lists.xensource.com [mailto:xen-users-
> > > bounces@lists.xensource.com] On Behalf Of Madhu Venugopal
(vmadhu)
> > > Sent: Tuesday, August 25, 2009 3:43 PM
> > > To: Xen User-List
> > > Subject: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> > could
> > > notfind filesystem /dev/root/)
> > >
> > > Hi,
> > >
> > > I installed XEN 3.4-testing version without much problems in
CentOS
> > 5.3
> > > running on quadcore Intel Nahelam processors using the following
> > > installation
> > > steps (as in the README) :
> > >
> > > <steps>
> > > hg clone http://xenbits.xensource.com/xen-3.4-testing.hg`
> > > cd xen-unstable.hg
> > > make world
> > > make install
> > > make linux-2.6-xen-config CONFIGMODE=menuconfig
> > > make linux-2.6-xen-build
> > > make linux-2.6-xen-install
> > > depmod 2.6.18.8-xen
> > > mkinitrd -v -f --with=ahci --with=sd_mod --with=scsi_mod --allow-
> > > missing
> > > initrd-2.6.18-xen.img 2.6.18.8-xen
> > > cp initrd-2.6.18-xen.img /boot
> > > </steps>
> > >
> > > After the installation, I updated the grub with the following
entry
> :
> > >
> > > <grub.conf>
> > > title  Xen 3.4.2
> > >         root (hd0,0)
> > >         kernel /xen.gz loglvl=all guest_loglvl=all vtd=1 iommu=1
> > >         module /vmlinuz-2.6.18.8-xen root=LABEL=/ apic=debug
> > maxcpus=8
> > >         module /initrd-2.6.18-xen.img
> > > <grub.conf>
> > > But during the bootup, I see Kernel panic with the only error
above
> > > that
> > > being :
> > >
> > > <error>
> > > mount: could not find filesystem /dev/root/
> > > setuproot: moving /dev failed: No such file or Directory
> > > no fstub.sys, mounting internal defaults
> > > setuproot: error mounting /proc:No such file or directory
> > > </error>
> > >
> > > Is it an error in partition ? or a Grub entry error ?
> > > Or an installation error ?
> > >
> > > Can someone help me ?
> > >
> > > Thanks,
> > > Madhu
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
> >
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> The SAQ Group
> 
> Registered Office: 18 Chapel Street, Petersfield, Hampshire GU32 3DZ
> SAQ is the trading name of SEMTEC Limited. Registered in England &
> Wales
> Company Number: 06481952
> 
> http://www.saqnet.co.uk AS29219
> 
> SAQ Group Delivers high quality, honestly priced communication and
I.T.
> services to UK Business.
> 
> Broadband : Domains : Email : Hosting : CoLo : Servers : Racks :
> Transit : Backups : Managed Networks : Remote Support.
> 
> ISPA Member
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Fajar

> (vmadhu)<vmadhu@cisco.com> wrote:
> > Hi,
> >
> > I started everything from scratch...
> >
> > 1. Installed CentOS 5.3
> > 2. Installed XEN 3.4-testing as per README
> >
> > The same problem during the reboot. I copied the Grub entry from the
> > Native CentOS5.3 installation.
> 
> On your original setup, I noticed you''re using
"root=LABEL=/1" on the
> original grub stanza and "root=LABEL=/" on Xen stanza. Are they
> supposed to refer to the same root? This could be one of things
> causing you problems.
That is the earliest attempt and that setup is gone. I don''t want to 
debug this now... Maybe later (once the issue at hand is resolved).
> 
> >
> > This time am seeing an error additional error :
> >
> > "Volume group : "VolGroup00" not Found"
> >
> > Searching the forums, I understand that this is a Logical Volume and
> > There are a few problems with Logical Volumes. But none of the
> > workarounds
> > Seems to work.
> >
> > I get a feeling that the "mkinitrd" is not doing its job
completely.
> > (or) what am I missing ?
> 
> My guess is the kernel config you use is missing some essential
> modules needed to boot correctly. Here''s some of the things you
can
> try :
Okay. How would I find what modules are missing ?
I don''t see any such error in the bootup logs. Any other suggestions ?
> 
> - Install RHEL''s Xen. This should be pretty straightforward,
you''d end
> up with Xen 3.1+ and a working grub.conf stanza for Xen with
RHEL''s
> kernel-xen
> - Install Xen package from gitco (http://www.gitco.de/repo/). You can
> get Xen 3.4.1 (currently in testing) but still using RHEL''s
kernel-xen
> - If that works, you can simply compile another xen kernel as you
> like, using either 2.6.18 or later pv_ops kernel. If using 2.6.18, you
> can use RHEL''s kernel-xen config as a base.
I didn''t want to take this approach. We have standardized on the
approach
to take with the existing XEN installations and kernel to use. It is
confusing
that am the only one seeing this issue while it works just fine on other
Machines. This makes it clear that it is machine specific and am missing
Some drivers for them. But am clueless on what is that am missing and
how
To include them in initrd. Any suggestions ?

Thanks,
Madhu

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

Just before the error message, I see the following messages during the
bootup
Sequence :

<log>
scanning and configuring dmraid supported devices
creating root device
Mounting root filesystem
Mount: could not find filesystem ''/dev/root''
<log>

Does that mean it is something to do with the dmraid modules ?

Thanks,
Madhu
> -----Original Message-----
> From: Fajar A. Nugraha [mailto:fajar@fajar.net]
> Sent: Thursday, August 27, 2009 5:52 AM
> To: Madhu Venugopal (vmadhu)
> Cc: Xen User-List
> Subject: Re: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> On Thu, Aug 27, 2009 at 2:56 AM, Madhu Venugopal
> (vmadhu)<vmadhu@cisco.com> wrote:
> > Hi,
> >
> > I started everything from scratch...
> >
> > 1. Installed CentOS 5.3
> > 2. Installed XEN 3.4-testing as per README
> >
> > The same problem during the reboot. I copied the Grub entry from the
> > Native CentOS5.3 installation.
> 
> On your original setup, I noticed you''re using
"root=LABEL=/1" on the
> original grub stanza and "root=LABEL=/" on Xen stanza. Are they
> supposed to refer to the same root? This could be one of things
> causing you problems.
> 
> >
> > This time am seeing an error additional error :
> >
> > "Volume group : "VolGroup00" not Found"
> >
> > Searching the forums, I understand that this is a Logical Volume and
> > There are a few problems with Logical Volumes. But none of the
> > workarounds
> > Seems to work.
> >
> > I get a feeling that the "mkinitrd" is not doing its job
completely.
> > (or) what am I missing ?
> 
> My guess is the kernel config you use is missing some essential
> modules needed to boot correctly. Here''s some of the things you
can
> try :
> 
> - Install RHEL''s Xen. This should be pretty straightforward,
you''d end
> up with Xen 3.1+ and a working grub.conf stanza for Xen with
RHEL''s
> kernel-xen
> - Install Xen package from gitco (http://www.gitco.de/repo/). You can
> get Xen 3.4.1 (currently in testing) but still using RHEL''s
kernel-xen
> - If that works, you can simply compile another xen kernel as you
> like, using either 2.6.18 or later pv_ops kernel. If using 2.6.18, you
> can use RHEL''s kernel-xen config as a base.
> 
> --
> Fajar
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Fri, Aug 28, 2009 at 11:44 AM, Madhu Venugopal
(vmadhu)<vmadhu@cisco.com> wrote:
>> > I get a feeling that the "mkinitrd" is not doing its job
completely.
>> > (or) what am I missing ?
>>
>> My guess is the kernel config you use is missing some essential
>> modules needed to boot correctly. Here''s some of the things
you can
>> try :
>
> Okay. How would I find what modules are missing ?
> I don''t see any such error in the bootup logs. Any other
suggestions ?
Start with the boot log. It usually shows you what block devices are
detected, etc.
The basic ones for domU (2.6.18 kernel) are xenblk (domU block device)
and ext3 (or whatever file system you use). For dom0 kernel, it''s
easier to see the output of "lsmod" from your working installation.
>
>>
>> - Install RHEL''s Xen. This should be pretty straightforward,
you''d end
>> up with Xen 3.1+ and a working grub.conf stanza for Xen with
RHEL''s
>> kernel-xen
>> - Install Xen package from gitco (http://www.gitco.de/repo/). You can
>> get Xen 3.4.1 (currently in testing) but still using RHEL''s
kernel-xen
>> - If that works, you can simply compile another xen kernel as you
>> like, using either 2.6.18 or later pv_ops kernel. If using 2.6.18, you
>> can use RHEL''s kernel-xen config as a base.
>
> I didn''t want to take this approach. We have standardized on the
> approach
> to take with the existing XEN installations and kernel to use.
Standard is fine, if it works. What I''m saying is if you want to find
out what''s wrong (is it Xen userland? kernel version? kernel config?)
the steps above can help.
> It is
> confusing
> that am the only one seeing this issue while it works just fine on other
> Machines. This makes it clear that it is machine specific and am missing
> Some drivers for them. But am clueless on what is that am missing and
> how
> To include them in initrd. Any suggestions ?
For starters, copy RHEL''s kernel-xen config to the kernel from xen.org
(like
http://bits.xensource.com/oss-xen/release/3.4.0/linux-2.6.18-xen-3.4.0.tar.gz).
That should provide similar set of modules.

Then try running mkinitrd WITHOUT --allow-missing. It should show you
what modules it thinks you should have but currently missing.

-- 
Fajar

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

> >
> > Okay. How would I find what modules are missing ?
> > I don''t see any such error in the bootup logs. Any other
suggestions
> ?
> 
> Start with the boot log. It usually shows you what block devices are
> detected, etc.
> The basic ones for domU (2.6.18 kernel) are xenblk (domU block device)
> and ext3 (or whatever file system you use). For dom0 kernel, it''s
> easier to see the output of "lsmod" from your working
installation.
I tried lsmod on the Base CentOS 5.3 installation and saw these :

<lsmod>
dm_raid45              66509  0 
dm_message              6977  1 dm_raid45
dm_region_hash         15681  1 dm_raid45
dm_log                 14529  3 dm_mirror,dm_raid45,dm_region_hash
dm_mod                 62201  4 dm_mirror,dm_multipath,dm_raid45,dm_log
dm_mem_cache            9537  1 dm_raid45
ata_piix               23621  0 
libata                156933  1 ata_piix
cciss                  63813  3 
sd_mod                 25153  0 
scsi_mod              141589  6 scsi_dh,sr_mod,sg,libata,cciss,sd_mod
ext3                  124233  1 
jbd                    56937  1 ext3
<lsmod>

I could not see the dm_raid45, dm_region_hash in the
/lib/modules/2.6.18.8-xen/kernel
Directory. Hence I copied these from /lib/modules/2.6.18-128.el5PAE/.

After this I ran mkinitrd again. I still see the kernel panic, Also I
see a few error
message during bootup : "dm-raid45: disagrees about version of
symbol..."...

Looks like I cant just copy over the modules...

I will try your other suggestions...

-Madhu
> 
> >
> >>
> >> - Install RHEL''s Xen. This should be pretty
straightforward, you''d
> end
> >> up with Xen 3.1+ and a working grub.conf stanza for Xen with
RHEL''s
> >> kernel-xen
> >> - Install Xen package from gitco (http://www.gitco.de/repo/). You
> can
> >> get Xen 3.4.1 (currently in testing) but still using
RHEL''s kernel-
> xen
> >> - If that works, you can simply compile another xen kernel as you
> >> like, using either 2.6.18 or later pv_ops kernel. If using 2.6.18,
> you
> >> can use RHEL''s kernel-xen config as a base.
> >
> > I didn''t want to take this approach. We have standardized on
the
> > approach
> > to take with the existing XEN installations and kernel to use.
> 
> Standard is fine, if it works. What I''m saying is if you want to
find
> out what''s wrong (is it Xen userland? kernel version? kernel
config?)
> the steps above can help.
> 
> > It is
> > confusing
> > that am the only one seeing this issue while it works just fine on
> other
> > Machines. This makes it clear that it is machine specific and am
> missing
> > Some drivers for them. But am clueless on what is that am missing
and
> > how
> > To include them in initrd. Any suggestions ?
> 
> For starters, copy RHEL''s kernel-xen config to the kernel from
xen.org
> (like
http://bits.xensource.com/oss-xen/release/3.4.0/linux-2.6.18-xen-
> 3.4.0.tar.gz).
> That should provide similar set of modules.
> 
> Then try running mkinitrd WITHOUT --allow-missing. It should show you
> what modules it thinks you should have but currently missing.
> 
> --
> Fajar
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I want to upgrade my virt-manager to virt-manager-0.8.0-1.fc11.noarch.rpm. while
doing this manually a lot of dependency problem occurs.
[root@HPCNL-SR-2 ~]# uname -ra
Linux HPCNL-SR-2 2.6.30-rc6-tip #1 SMP Tue Aug 25 12:26:16 PKST 2009 i686 i686
i386 GNU/Linux
 with these specs whenever i do yum install virt-manager i get 
virt-manager-0.7.0-5.fc11.i586

which doesn''t work. Please guide how to repair virt-manager

Regards
Fasiha



      See the Web's breaking stories, chosen by people like you. Check
out Yahoo! Buzz. http://in.buzz.yahoo.com/

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

Hi Fajar, all,

Without much luck with CentOS, I tried Fedora 11.

This time, I could get Xen3.4.1 up and running with Fedora 11.
I don''t know the problem involved in CentOS. Maybe someone
from the CentOS developer community should look into this.
The only difference I see between my setup and others is the
need for cciss RAID controller (HP smart array).

Am now facing issues with the guest VM Configuration file.
Will start a new email thread on that.

Thanks,
-Madhu
> -----Original Message-----
> From: Fajar A. Nugraha [mailto:fajar@fajar.net]
> Sent: Thursday, August 27, 2009 5:52 AM
> To: Madhu Venugopal (vmadhu)
> Cc: Xen User-List
> Subject: Re: [Xen-users] 3.4-testing : Kernel panic on bootup (mount:
> couldnotfind filesystem /dev/root/)
> 
> On Thu, Aug 27, 2009 at 2:56 AM, Madhu Venugopal
> (vmadhu)<vmadhu@cisco.com> wrote:
> > Hi,
> >
> > I started everything from scratch...
> >
> > 1. Installed CentOS 5.3
> > 2. Installed XEN 3.4-testing as per README
> >
> > The same problem during the reboot. I copied the Grub entry from the
> > Native CentOS5.3 installation.
> 
> On your original setup, I noticed you''re using
"root=LABEL=/1" on the
> original grub stanza and "root=LABEL=/" on Xen stanza. Are they
> supposed to refer to the same root? This could be one of things
> causing you problems.
> 
> >
> > This time am seeing an error additional error :
> >
> > "Volume group : "VolGroup00" not Found"
> >
> > Searching the forums, I understand that this is a Logical Volume and
> > There are a few problems with Logical Volumes. But none of the
> > workarounds
> > Seems to work.
> >
> > I get a feeling that the "mkinitrd" is not doing its job
completely.
> > (or) what am I missing ?
> 
> My guess is the kernel config you use is missing some essential
> modules needed to boot correctly. Here''s some of the things you
can
> try :
> 
> - Install RHEL''s Xen. This should be pretty straightforward,
you''d end
> up with Xen 3.1+ and a working grub.conf stanza for Xen with
RHEL''s
> kernel-xen
> - Install Xen package from gitco (http://www.gitco.de/repo/). You can
> get Xen 3.4.1 (currently in testing) but still using RHEL''s
kernel-xen
> - If that works, you can simply compile another xen kernel as you
> like, using either 2.6.18 or later pv_ops kernel. If using 2.6.18, you
> can use RHEL''s kernel-xen config as a base.
> 
> --
> Fajar
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users