[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen Dom U kernel


  • To: Pasi Kärkkäinen <pasik@xxxxxx>
  • From: kishore kumar <bodkekumar@xxxxxxxxx>
  • Date: Thu, 22 Apr 2010 14:35:04 -0700
  • Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • Delivery-date: Thu, 22 Apr 2010 14:36:08 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xZqFqPp49iuaxli5XQ0s9FprCG0rKutRcZY3MOkxgYZFkAEfQJXkycgyYmGEJU3IMt 7gq5wkbO6sboT4SNZqsHpuTWUOWHtsct1MzYNSTeSl1I4f+0fj900p4Wvjwlfx7ePjKH fw7Sa+lJl3Drt17CZoKhZyEQ/ZxdjVVYCru5I=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

OK. 
what could be the reason for my domU creation is failing here? 
 
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
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
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
 
Thank You.
On Thu, Apr 22, 2010 at 1:48 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Thu, Apr 22, 2010 at 01:39:57PM -0700, kishore kumar wrote:
>    I did below steps
>    make menuconfig
>    make
>    make modules_install install
>    /sbin/depmod -a 2.6.33
>    /sbin/mkinitrd --with xen-blkfront --with xen-netfront
>    /boot/initrd-xenu.img    2.6.33
>

You had these .config options set:
CONFIG_XEN_BLKDEV_FRONTEND=y
CONFIG_XEN_NETDEV_FRONTEND=y

That means the drivers are built *into* the kernel statically,
and they're *not* built as modules.

So you don't need to use "--with xen-blkfront --with xen-netfront" for mkinitrd.

-- Pasi

>    still the same problem.
>
>    On Thu, Apr 22, 2010 at 1:25 PM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote:
>
>      On Thu, Apr 22, 2010 at 01:08:54PM -0700, kishore kumar wrote:
>      >    I tried
>      >    mkinitrd --with xen-blkfront --with xen-netfront
>      /boot/initrd-xenu.img
>      >     2.6.33
>      >    It complaints No module xen-blkfront found for kernel 2.6.33,
>      aborting.
>      >
>      >    I dont see xen-blkfront.ko in my /lib/modules/2.633/drivers/block .
>       Am I
>      >    looking at the right place?
>      >
>
>      Have you done "depmod -a <kernelversion>" before running mkinitrd ?
>
>      -- Pasi
>
>      >    Thank You.
>      >
>      >    On Thu, Apr 22, 2010 at 12:53 PM, Pasi Kärkkäinen
>      <[1][2]pasik@xxxxxx> wrote:
>      >
>      >      On Thu, Apr 22, 2010 at 11:31:25AM -0700, kishore kumar wrote:
>      >      >    I am trying create ramdisk image for my domU image from
>      Konrad git
>      >      >    repository.
>      >      >
>      >      >    mkinitrd --with xenblk --with xennet /boot/initrd-xenu.img
>       2.6.33
>      >      >    I get No module xenblk found for kernel 2.6.33, aborting.
>      >      >    Can you please let me know what could be the problem??
>      >      >
>      >      >    I have CONFIG_XEN_BLKDEV_FRONTEND=y
>      >      >    CONFIG_XEN_NETDEV_FRONTEND=y in my .config as well.
>      >      >
>      >
>      >      Xen modules in upstream [2][3]kernel.org (pvops) kernels are not
>      called
>      >      xennet or xenblk.
>      >      They're called xen-blkfront and xen-netfront in pvops kernels.
>      >
>      >      You can easily verify be checking under
>      /lib/modules/<kernelversion>/
>      >
>      >      -- Pasi
>      >      >    Thank You.
>      >      >    On Tue, Apr 20, 2010 at 6:45 PM, Konrad Rzeszutek Wilk
>      >      >    <[1][3][4]konrad.wilk@xxxxxxxxxx> wrote:
>      >      >
>      >      >      On Tue, Apr 20, 2010 at 05:09:29PM -0700, kishore kumar
>      wrote:
>      >      >      > I did git pull and did
>      >      >      > make
>      >      >      > make modules_install install.
>      >      >      >   Is this the problem with xen blkdevices not loaded?
>       Can you
>      >      let me
>      >      >      know
>      >      >
>      >      >      So now you are hitting another problem. This looks
>      >      >      to be this one:
>      >      >
>      >
>      [2][4][5]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html
>      >      >
>      >      >      Please follow the whole thread and select the right config
>      >      options.
>      >      >
>      >      > References
>      >      >
>      >      >    Visible links
>      >      >    1. mailto:[5][6]konrad.wilk@xxxxxxxxxx
>      >      >    2.
>      >
>       [6][7]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html
>      >
>      > References
>      >
>      >    Visible links
>      >    1. mailto:[8]pasik@xxxxxx
>      >    2. [9]http://kernel.org/
>      >    3. mailto:[10]konrad.wilk@xxxxxxxxxx
>      >    4.
>      [11]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html
>      >    5. mailto:[12]konrad.wilk@xxxxxxxxxx
>      >    6.
>      [13]http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html
>
> References
>
>    Visible links
>    1. mailto:pasik@xxxxxx
>    2. mailto:pasik@xxxxxx
>    3. http://kernel.org/
>    4. mailto:konrad.wilk@xxxxxxxxxx
>    5. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html
>    6. mailto:konrad.wilk@xxxxxxxxxx
>    7. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html
>    8. mailto:pasik@xxxxxx
>    9. http://kernel.org/
>   10. mailto:konrad.wilk@xxxxxxxxxx
>   11. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html
>   12. mailto:konrad.wilk@xxxxxxxxxx
>   13. http://lists.xensource.com/archives/html/xen-devel/2010-04/msg00897.html

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.