Re: Xen Dom U kernel

[kishore kumar <bodkekumar@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 5130 bytes --]

Thank you for your pointers.
Please find the answers for your questions.  May be there could be something
I am doing wrong here.

Where did you come up with the .config file? Did you use the same one as the
Dom0?
   NO. After I do git pull from konrad git repository and do make
menuconfig, I guess the .config file is generated. I am not using Dom 0
.config file.

1). Do you have the filesystem for you DomU compiled in?
     NO.  After My xen with pvops dom 0 is up and running, I just pulled the
dom U from konrad git and compiled.

2). Does you guest configuration file have an 'extra' and 'root'? Try
for right now to only have the root, and make sure it is minimal.

Below are the only options I have in my guest configuration file.  I doubt
if I have provided the right disk option here. Please help me here if I
provided the wrong disk option.
kernel = "/boot/vmlinuz-2.6.33"
ramdisk = "boot/initrd-2.6.33.img"
builder='linux'
memory=512
disk = ['phy:sda2,sda2,w']
root="/dev/volGroup01/Logvol00 ro"

I have CONFIG_BLK_DEV_INITRD=y set

Please let me know if something wrong I did here.

Thank You.






On Thu, Apr 22, 2010 at 6:36 PM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> On Thu, Apr 22, 2010 at 05:15:35PM -0700, kishore kumar wrote:
> > I am using RHEL5.
> >
> > and I have below too in my .config.
> >
> > CONFIG_SYSFS_DEPRECATED=y
> > CONFIG_SYSFS_DEPRECATED_V2=y
>
> Good. Where did you come up with the .config file? Did you use the same
> one as the Dom0?
>
> > My /etc/modprobe.conf has the following
> >
> > alias scsi_hostadapter ahci
> > alias eth2 ixgbe
> > alias eth3 ixgbe
> >
> > Do I need to add the below lines in /etc/modprobe.conf ??
>
> Those are when you migrate your Dom0 from 2.6.18 to 2.6.31. Let me
> make that specific in the Wiki.
> .. snip..
>
> > Could you please let me know what exactly needs to be done?  I could not
> get
> > much out of it?
>
> I can't tell you step-by-step what to do. What I can do is give pointers
> of where to look.
>
> 1). Do you have the filesystem for you DomU compiled in?
>
> 2). Can you edit mkinitrd so it doesn't use the 'setquiet' option. That
> will give you more debug data. Run mkinitrd to recreate the initrd
> image.
>
> 4). Does you guest configuration file have an 'extra' and 'root'? Try
> for right now to only have the root, and make sure it is minimal. So for
> example:
> root="/dev/VolGroup01/LogVol00 ro"
>
> 5). You do have CONFIG_BLK_DEV_INITRD=y set right?
>
> > Thank You.
> >
> > On Thu, Apr 22, 2010 at 2:47 PM, Konrad Rzeszutek Wilk <
> > konrad.wilk@oracle.com> wrote:
> >
> > > On Thu, Apr 22, 2010 at 02:35:04PM -0700, kishore kumar wrote:
> > > > OK.
> > > > what could be the reason for my domU creation is failing here?
> > >
> > > Hmm, Are you using a RHEL5/CentOS based userspace to build the initrd
> > > image?
> > >
> > > If you are please take a look at this:
> > > http://wiki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher
> > >
> > > >
> > > > Mounting proc filesystem
> > > > Mounting sysfs filesystem
> > > > Creating /dev
> > > > Creating initial device nodes
> > > > Setting up hotplug.
> > > > Creating block device nodes.
> > > > Scanning and configuring dmraid supported devices
> > > > Scanning logical volumes
> > > > Reading all physical volumes. This may take a while...
> > > > Found volume group "VolGroup01" using metadata type lvm2
> > > > lvm used greatest stack depth: 4912 bytes left
> > > > Activating logical volumes
> > > > 2 logical volume(s) in volume group "VolGroup01" now active
> > > > Trying to resume from /dev/VolGroup01/LogVol01
> > > > No suspend signature on swap, not resuming.
> > > > 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
>
> Uhh.
> > > > no fstab.sys, mounting internal defaults
>
> That is weird. The 'Creating root device' usually sets the /etc/fstab
> file
>
> > > > 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
> > > > Kernel panic - not syncing: Attempted to kill init!
> > > > Pid: 1, comm: init Not tainted 2.6.33 #3
> > > > Call Trace:
> > > > [<ffffffff810513fa>] panic+0xa5/0x171
> > > > [<ffffffff81006891>] ? xen_force_evtchn_callback+0xd/0xf
> > > > [<ffffffff8148ce94>] ? _raw_write_unlock_irq+0x30/0x3b
> > > > [<ffffffff8107ecb8>] ? trace_hardirqs_on_caller+0x110/0x134
> > > > [<ffffffff8107ece9>] ? trace_hardirqs_on+0xd/0xf
> > > > [<ffffffff8148ce9b>] ? _raw_write_unlock_irq+0x37/0x3b
> > > > [<ffffffff81054b0c>] do_exit+0x7c/0x6f5
> > > > [<ffffffff8107189f>] ? up_read+0x2b/0x2f
> > > > [<ffffffff81055221>] sys_exit_group+0x0/0x1b
> > > > [<ffffffff81055238>] sys_exit_group+0x17/0x1b
> > > > [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b
> > >
>

[-- Attachment #1.2: Type: text/html, Size: 6977 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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