From mboxrd@z Thu Jan 1 00:00:00 1970 From: ccmail111 Subject: Re: boot Xen 4.0 Date: Tue, 18 May 2010 14:46:10 -0700 (PDT) Message-ID: <140776.68428.qm@web34205.mail.mud.yahoo.com> References: <20100518191129.GA17817@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0227184179==" Return-path: In-Reply-To: <20100518191129.GA17817@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?iso-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: deshantm@gmail.com, yingbin wang , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0227184179== Content-Type: multipart/alternative; boundary="0-1445321312-1274219170=:68428" --0-1445321312-1274219170=:68428 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi Pasi, I'm sorry for typo below grub.conf is: title Xen 4.0 debug=A0 XenLinux 2.6 =A0=A0=A0=A0=A0=A0=A0 root (hd0,0) =A0=A0=A0=A0=A0=A0 kernel /xen-4.0.0.gz console=3Dcom1, com1=3D115200,8n1 n= oreboot loglvl=3Dall=A0 vga=3Dtext-80x50,keep iommu=3Doff apic=3Ddebug gues= t_loglvl=3Dall =A0=A0=A0=A0=A0=A0 module /vmlinuz-2.6.31.13=A0 ro root=3D/dev/sda3 console= =3Dhvc0=A0 earlyprintk=3Dxen nomodeset initcall_debug debug loglevel=3D10 =A0=A0=A0=A0=A0=A0 module /initrd.img-2.6.31.13 on another PC during boot up I see another problem - it is stuck at error: =A0=A0=A0=A0=A0 ACPI Error (dsField-0140): [CAPD] Namespace lookup failure,= AE_ALREADY_EXISTS. =A0=A0=A0=A0=A0 ACPI Error (psparse-0537): Method parse/execution failed [\= _SB_.PCI0._OSCI] (Node ffff8800b4c12500), AE_ALREADY_EXISTS =A0=A0=A0=A0 aer 0000:00:01.0: pcie02: AER service couldn't init device: _O= SC failed =A0 <...clip..errors...> =A0(XEN)=A0 irq.c:=A0 1182:d0 Cannot bind IRQ 0 to guest. Will not share wi= th others. =A0=A0=A0 <..clip..> =A0=A0=A0=A0 [drm] Initialized drm 1.1.0 20060810 =A0=A0=A0=A0 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled Any thoughts ? Thanks ! CM --- On Tue, 5/18/10, Pasi K=E4rkk=E4inen wrote: From: Pasi K=E4rkk=E4inen Subject: Re: [Xen-devel] boot Xen 4.0 To: "ccmail111" Cc: "yingbin wang" , deshantm@gmail.com, xen-deve= l@lists.xensource.com Date: Tuesday, May 18, 2010, 3:11 PM On Tue, May 18, 2010 at 12:08:36PM -0700, ccmail111 wrote: >=A0 =A0 Thanks for tip below. >=20 >=A0 =A0 1) I tried rebuild kernel with option below. I now build kernel wi= th: >=20 >=A0 =A0 CONFIG_SYSFS_DEPRECATED=3Dy >=A0 =A0 CONFIG_SYSFS_DEPRECATED_V2=3Dy >=20 >=A0 =A0 But see problem below during boot up as below.. >=20 >=A0 =A0 grub.conf: >=20 >=A0 =A0 title Xen 4.0 debug=A0 XenLinux 2.6 >=A0 =A0 =A0 =A0 =A0 =A0 root (hd0,0) >=A0 =A0 =A0 =A0 =A0=A0=A0kernel /xen-4.0.0.gz console=3Dcom1, com1=3D11520= 0,8n1 noreboot >=A0 =A0 loglvl=3Dall=A0 vga=3Dtext-80x50,keep iommu=3Doff apic=3Ddebug gue= st_loglvl=3Dall >=A0 =A0 =A0 =A0 =A0=A0=A0module /vmlinuz-2.6.31.13=A0 ro root=3D/dev/ram0 = console=3Dhvc0 >=A0 =A0 earlyprintk=3Dxen nomodeset initcall_debug debug loglevel=3D10 your root=3D parameter is wrong. You need to have the actual root partition path there. -- Pasi >=A0 =A0 =A0 =A0 =A0=A0=A0module /initrd.img-2.6.31.13 >=20 >=A0 =A0 2) Is there a reference (working) ramdisk/initrd for Xen4.0 with b= usybox >=A0 =A0 or such ? I created ramdisk as: >=20 >=A0 =A0 # mkinitrd -v -f --builtin=3Dehci-hcd --builtin=3Dohci-hcd --built= in=3Duhci-hcd >=A0 =A0 --builtin=3Dahci --builtin=3Daacraid --builtin=3Daacraid --builtin= =3Dsd_mod >=A0 =A0 --builtin=3Dscsi_mod /boot/initrd.img-2.6.31.13 2.6.31.13 >=20 >=A0 =A0 Using this (since there is no busybox or such): >=20 >=A0 =A0 Trying to resume from /dev/sdb2 >=A0 =A0 Unable to access resume device (/dev/sdb2) >=A0 =A0 Creating root device. >=A0 =A0 usb 5-1: new full speed USB device using uhci_hcd and address 2 >=A0 =A0 Mounting root filesystem. >=A0 =A0 VFS: Can't find ext3 filesystem on dev ram0. >=A0 =A0 mount: error mounting /dev/root on /sysroot as ext3: Invalid argum= ent >=A0 =A0 Setting up other filesystems. >=A0 =A0 Setting up new root fs >=A0 =A0 setuproot: moving /dev failed: No such file or directory >=A0 =A0 no fstab.sys, mounting internal defaults >=A0 =A0 setuproot: error mounting /proc: No such file or directory >=A0 =A0 setuproot: error mounting /sys: No such file or directory >=A0 =A0 Switching to new root and running init. >=A0 =A0 unmounting old /dev >=A0 =A0 unmounting old /proc >=A0 =A0 unmounting old /sys >=A0 =A0 switchroot: mount failed: No such file or directory >=A0 =A0 Kernel panic - not syncing: Attempted to kill init! >=A0 =A0 Pid: 1, comm: init Not tainted 2.6.31.13 #8 >=A0 =A0 Call Trace: >=A0 =A0=A0=A0[] panic+0xb7/0x172 >=A0 =A0=A0=A0[] ? do_exit+0x37c/0x6de >=A0 =A0=A0=A0[] ? xen_restore_fl_direct_end+0x0/0x1 >=A0 =A0=A0=A0[] ? lock_release+0x197/0x1b8 >=A0 =A0=A0=A0[] ? trace_hardirqs_on+0x20/0x36 >=A0 =A0=A0=A0[] ? _write_unlock_irq+0x46/0x61 >=A0 =A0=A0=A0[] do_exit+0x8d/0x6de >=A0 =A0=A0=A0[] sys_exit_group+0x0/0x42 >=A0 =A0=A0=A0[] ? trace_hardirqs_on_thunk+0x3a/0x3f >=A0 =A0=A0=A0[] sys_exit_group+0x2a/0x42 >=A0 =A0=A0=A0[] system_call_fastpath+0x16/0x1b >=20 >=A0 =A0 Any suggestions ? >=20 >=A0 =A0 Thanks ! >=20 >=A0 =A0 CM >=20 >=A0 =A0 --- On Sat, 5/15/10, yingbin wang wrote= : >=20 >=A0 =A0 =A0 From: yingbin wang >=A0 =A0 =A0 Subject: Re: [Xen-devel] boot Xen 4.0 >=A0 =A0 =A0 To: "ccmail111" >=A0 =A0 =A0 Cc: "Pasi K=E4rkk=E4inen" , deshantm@gmail.com, >=A0 =A0 =A0 xen-devel@lists.xensource.com >=A0 =A0 =A0 Date: Saturday, May 15, 2010, 12:34 PM >=20 >=A0 =A0 =A0 I met similar problems and solved it. >=20 >=A0 =A0 =A0 if your grub.conf is OK, you can try to edit a option of=A0 yo= ur .config. >=A0 =A0 =A0 CONFIG_SYSFS_DEPRECATED_V2=3Dy >=20 >=A0 =A0 =A0 2010/5/14 ccmail111 >=A0 =A0 =A0 > >=A0 =A0 =A0 > Thanks Pasi/Todd, >=A0 =A0 =A0 > >=A0 =A0 =A0 > I did: >=A0 =A0 =A0 > # mkinitrd -v -f --builtin=3Dehci-hcd --builtin=3Dohci-hcd >=A0 =A0 =A0 --builtin=3Duhci-hcd --builtin=3Dahci --builtin=3Daacraid --bu= iltin=3Daacraid >=A0 =A0 =A0 --builtin=3Dsd_mod --builtin=3Dscsi_mod /boot/initrd.img-2.6.3= 1.13 2.6.31.13 >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > Now >=A0 =A0 =A0 > I see during boot: kernel panic: >=A0 =A0 =A0 > >=A0 =A0 =A0 > Mounting root filesystem. >=A0 =A0 =A0 > mount: could not find filesystem '/dev/root' >=A0 =A0 =A0 > setting up other filesystems >=A0 =A0 =A0 > setting up new root fs >=A0 =A0 =A0 > setuproot: moving /dev failed No such file or directory >=A0 =A0 =A0 > setuproot: error mounting /proc: No such file or directory >=A0 =A0 =A0 > setuproot: error mounting /sys: No such file or directory >=A0 =A0 =A0 > switchroot: mount failed: No such file or directory >=A0 =A0 =A0 >=A0=A0=A0kernel panic - not syncing : Attempted to kill init = ! >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > --- On Thu, 5/13/10, Pasi K=E4rkk=E4inen wrot= e: >=A0 =A0 =A0 > >=A0 =A0 =A0 > From: Pasi K=E4rkk=E4inen >=A0 =A0 =A0 > Subject: Re: [Xen-devel] initrd Xen 4.0 >=A0 =A0 =A0 > To: "ccmail111" >=A0 =A0 =A0 > Cc: deshantm@gmail.com, xen-devel@lists.xensource.com >=A0 =A0 =A0 > Date: Thursday, May 13, 2010, 4:27 PM >=A0 =A0 =A0 > >=A0 =A0 =A0 > On Thu, May 13, 2010 at 01:08:36PM -0700, ccmail111 wrote: >=A0 =A0 =A0 > >=A0 =A0 The #5 of README is not clear in details. >=A0 =A0 =A0 > >=A0 =A0 which directory to run depmod and mkinitrd from ? >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 > It doesn't matter. >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 I see: >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 # depmod xen-4.0.0 >=A0 =A0 =A0 > >=A0 =A0 WARNING: Couldn't find symtab and strtab in module = xen-4.0.0 >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 > Wrong. You need to run depmod for the *kernel*, not for xen. >=A0 =A0 =A0 > >=A0 =A0 =A0 > So like this: >=A0 =A0 =A0 > depmod -a 2.6.32.12 >=A0 =A0 =A0 > >=A0 =A0 =A0 > Or whatever is your kernel version. >=A0 =A0 =A0 > >=A0 =A0 =A0 > -- Pasi >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 # ls -l >=A0 =A0 =A0 > >=A0 =A0 total 1356 >=A0 =A0 =A0 > >=A0 =A0 -rw-r--r-- 1 root root 1380620 May 13 13:05 xen-4.0= .0 >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 Any suggestions ? >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 --- On Wed, 5/12/10, Todd Deshane wrote: >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 From: Todd Deshane >=A0 =A0 =A0 > >=A0 =A0 =A0 Subject: Re: [Xen-devel] initrd Xen 4.0 >=A0 =A0 =A0 > >=A0 =A0 =A0 To: "ccmail111" >=A0 =A0 =A0 > >=A0 =A0 =A0 Cc: xen-devel@lists.xensource.com >=A0 =A0 =A0 > >=A0 =A0 =A0 Date: Wednesday, May 12, 2010, 9:46 PM >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 Hi, >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 See inline. >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 On Wed, May 12, 2010 at 12:25 PM, ccmail111 >=A0 =A0 =A0 <[1]ccmail111@yahoo.com> >=A0 =A0 =A0 > >=A0 =A0 =A0 wrote: >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > Hi, >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > I downloaded Xen 4.0 and did: >=A0 =A0 =A0 > >=A0 =A0 =A0 > make install >=A0 =A0 =A0 > >=A0 =A0 =A0 > I donot see initrd (ramdisk) being created at= all. >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > Any suggestions ? >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 Step 5 of the README >=A0 =A0 =A0 > >=A0 =A0 =A0 =A0=A0=A0Depending on your config, you may need= to use 'mkinitrd' to >=A0 =A0 =A0 create >=A0 =A0 =A0 > >=A0 =A0 =A0 =A0=A0=A0an initial ram disk, just like a nativ= e system e.g. >=A0 =A0 =A0 > >=A0 =A0 =A0 =A0 =A0 # depmod 2.6.18-xen >=A0 =A0 =A0 > >=A0 =A0 =A0 =A0 =A0 # mkinitrd -v -f --with=3Daacraid --wit= h=3Dsd_mod >=A0 =A0 =A0 --with=3Dscsi_mod >=A0 =A0 =A0 > >=A0 =A0 =A0 initrd-2.6.18-xen.img 2.6.18-xen >=A0 =A0 =A0 > >=A0 =A0 =A0 =A0=A0=A0Other systems may requires the use of = 'mkinitramfs' to >=A0 =A0 =A0 create the >=A0 =A0 =A0 > >=A0 =A0 =A0 =A0=A0=A0ram disk. >=A0 =A0 =A0 > >=A0 =A0 =A0 =A0 =A0 # depmod 2.6.18-xen >=A0 =A0 =A0 > >=A0 =A0 =A0 =A0 =A0 # mkinitramfs -o initrd-2.6.18-xen.img = 2.6.18-xen >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 You may need to change the kernel version based= on what you >=A0 =A0 =A0 built. >=A0 =A0 =A0 > >=A0 =A0 =A0 Also some distros use different commands to bui= ld initrd files. >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 I actually forgot about this step for a second = too. >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 Thanks, >=A0 =A0 =A0 > >=A0 =A0 =A0 Todd >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 =A0 -- >=A0 =A0 =A0 > >=A0 =A0 =A0 Todd Deshane >=A0 =A0 =A0 > >=A0 =A0 =A0 [2][1]http://todddeshane.net >=A0 =A0 =A0 > >=A0 =A0 =A0 [3][2]http://runningxen.com >=A0 =A0 =A0 > > >=A0 =A0 =A0 > > References >=A0 =A0 =A0 > > >=A0 =A0 =A0 > >=A0 =A0 Visible links >=A0 =A0 =A0 > >=A0 =A0 1. file:///mc/compose?to=3Dccmail111@yahoo.com >=A0 =A0 =A0 > >=A0 =A0 2. [3]http://todddeshane.net/ >=A0 =A0 =A0 > >=A0 =A0 3. [4]http://runningxen.com/ >=A0 =A0 =A0 > >=A0 =A0 =A0 > > _______________________________________________ >=A0 =A0 =A0 > > Xen-devel mailing list >=A0 =A0 =A0 > > Xen-devel@lists.xensource.com >=A0 =A0 =A0 > > [5]http://lists.xensource.com/xen-devel >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > >=A0 =A0 =A0 > _______________________________________________ >=A0 =A0 =A0 > Xen-devel mailing list >=A0 =A0 =A0 > Xen-devel@lists.xensource.com >=A0 =A0 =A0 > [6]http://lists.xensource.com/xen-devel >=A0 =A0 =A0 > >=20 > References >=20 >=A0 =A0 Visible links >=A0 =A0 1. http://todddeshane.net/ >=A0 =A0 2. http://runningxen.com/ >=A0 =A0 3. http://todddeshane.net/ >=A0 =A0 4. http://runningxen.com/ >=A0 =A0 5. http://lists.xensource.com/xen-devel >=A0 =A0 6. http://lists.xensource.com/xen-devel =0A=0A=0A --0-1445321312-1274219170=:68428 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
=0A=0A --0-1445321312-1274219170=:68428-- --===============0227184179== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0227184179==--
Hi Pasi,

I'm sorry for typo below grub= .conf is:

title Xen 4.0 debug  XenLinux 2.6
  &nbs= p;     root (hd0,0)
     &n= bsp; kernel /xen-4.0.0.gz console=3Dcom1, com1=3D115200,8n1 noreboot loglvl= =3Dall  vga=3Dtext-80x50,keep iommu=3Doff apic=3Ddebug guest_loglvl=3D= all
       module /vmlinuz-2.6.31.13 = ro root=3D/dev/sda3 console=3Dhvc0  earlyprintk=3Dxen nomodeset initc= all_debug debug loglevel=3D10
       modul= e /initrd.img-2.6.31.13


on another PC during boot up I see anoth= er problem - it is stuck at error:

      AC= PI Error (dsField-0140): [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS= .
      ACPI Error (psparse-0537): Method parse= /execution failed [\_SB_.PCI0._OSCI] (Node ffff8800b4c12500), AE_ALREADY_EXISTS
 &nb= sp;   aer 0000:00:01.0: pcie02: AER service couldn't init device:= _OSC failed

  <...clip..errors...>
 (XEN)  = irq.c:  1182:d0 Cannot bind IRQ 0 to guest. Will not share with others= .
    <..clip..>
     [drm] = Initialized drm 1.1.0 20060810
     Serial: 8250/165= 50 driver, 4 ports, IRQ sharing enabled

Any thoughts ?

Thanks= !
CM

--- On Tue, 5/18/10, Pasi K=E4rkk=E4inen <pasik@ik= i.fi> wrote:

From: Pasi K=E4rkk= =E4inen <pasik@iki.fi>
Subject: Re: [Xen-devel] boot Xen 4.0
To= : "ccmail111" <ccmail111@yahoo.com>
Cc: "yingbin wang" <yingbin= .wangyb@gmail.com>, deshantm@gmail.com, xen-devel@lists.xensource.com
Date: Tuesday, May 18, 2010, 3:11 PM
<= br>
On Tue, May 18, 2010 at 12:08:36PM -0700, ccmai= l111 wrote:
>    Thanks for tip below.
>
>&nbs= p;   1) I tried rebuild kernel with option below. I now build kernel w= ith:
>
>    CONFIG_SYSFS_DEPRECATED=3Dy
> = ;   CONFIG_SYSFS_DEPRECATED_V2=3Dy
>
>    But s= ee problem below during boot up as below..
>
>    gr= ub.conf:
>
>    title Xen 4.0 debug  XenLinux 2= .6
>            root (hd0,0)
>&nb= sp;          kernel /xen-4.0.0.gz console=3Dc= om1, com1=3D115200,8n1 noreboot
>    loglvl=3Dall  vga= =3Dtext-80x50,keep iommu=3Doff apic=3Ddebug guest_loglvl=3Dall
> = ;          module /vmlinuz-2.6.31.13  ro root=3D/dev/ram0 console=3Dhvc0
>    earlyprintk=3Dxen nom= odeset initcall_debug debug loglevel=3D10

your root=3D parameter is = wrong.
You need to have the actual root partition path there.

-- Pasi


>           modul= e /initrd.img-2.6.31.13
>
>    2) Is there a referen= ce (working) ramdisk/initrd for Xen4.0 with busybox
>    or= such ? I created ramdisk as:
>
>    # mkinitrd -v -= f --builtin=3Dehci-hcd --builtin=3Dohci-hcd --builtin=3Duhci-hcd
>&nb= sp;   --builtin=3Dahci --builtin=3Daacraid --builtin=3Daacraid --built= in=3Dsd_mod
>    --builtin=3Dscsi_mod /boot/initrd.img-2.6.= 31.13 2.6.31.13
>
>    Using this (since there is no= busybox or such):
>
>    Trying to resume from /dev= /sdb2
>    Unable to access resume device (/dev/sdb2)
&g= t;    Creating root device.
>    usb 5-1: new full speed USB dev= ice using uhci_hcd and address 2
>    Mounting root filesys= tem.
>    VFS: Can't find ext3 filesystem on dev ram0.
&= gt;    mount: error mounting /dev/root on /sysroot as ext3: Inval= id argument
>    Setting up other filesystems.
> = ;   Setting up new root fs
>    setuproot: moving /dev= failed: No such file or directory
>    no fstab.sys, mount= ing internal defaults
>    setuproot: error mounting /proc:= No such file or directory
>    setuproot: error mounting /= sys: No such file or directory
>    Switching to new root a= nd running init.
>    unmounting old /dev
>  &nb= sp; unmounting old /proc
>    unmounting old /sys
>&n= bsp;   switchroot: mount failed: No such file or directory
>    Kernel panic - not syncing: Attempted to ki= ll init!
>    Pid: 1, comm: init Not tainted 2.6.31.13 #8>    Call Trace:
>     [<ffffff= ff8106bbeb>] panic+0xb7/0x172
>     [<fffff= fff8106fe04>] ? do_exit+0x37c/0x6de
>     [<= ;ffffffff8100fa6f>] ? xen_restore_fl_direct_end+0x0/0x1
>  &n= bsp;  [<ffffffff810a1c6b>] ? lock_release+0x197/0x1b8
&g= t;     [<ffffffff8109ef6e>] ? trace_hardirqs_on+0= x20/0x36
>     [<ffffffff815436be>] ? _writ= e_unlock_irq+0x46/0x61
>     [<ffffffff8106fb1= 5>] do_exit+0x8d/0x6de
>     [<ffffffff8107= 021e>] sys_exit_group+0x0/0x42
>     [<ffff= ffff8154265c>] ? trace_hardirqs_on_thunk+0x3a/0x3f
>     [<ffffffff81070248>] sys_exit_group+0x2a/0x42
&= gt;     [<ffffffff81015332>] system_call_fastpath= +0x16/0x1b
>
>    Any suggestions ?
>
>=     Thanks !
>
>    CM
>
>&nb= sp;   --- On Sat, 5/15/10, yingbin wang <yin= gbin.wangyb@gmail.com> wrote:
>
>      F= rom: yingbin wang <yingbin.wangyb@gmail.com= >
>      Subject: Re: [Xen-devel] boot Xen 4.0
&= gt;      To: "ccmail111" <ccmail111@yahoo.co= m>
>      Cc: "Pasi K=E4rkk=E4inen" <pas= ik@iki.fi>, deshantm@gmail.com,
>    =   xen-devel@lists.xensource.com>      Date: Saturday, May 15, 2010, 12:34 PM
> <= br>>      I met similar problems and solved it.
> <= br>>      if your grub.conf is OK, you can try to edit a = option of  your .config.
>      CONFIG_SYSFS_DEPR= ECATED_V2=3Dy
>
>      2010/5/14 ccmail111 <= ccmail111@yahoo.com>
>      >>      > Thanks Pasi/Todd,
>    &nbs= p; >
>      > I did:
>      &= gt; # mkinitrd -v -f --builtin=3Dehci-hcd --builtin=3Dohci-hcd
> = ;     --builtin=3Duhci-hcd --builtin=3Dahci --builtin=3Daacraid -= -builtin=3Daacraid
>      --builtin=3Dsd_mod --builtin= =3Dscsi_mod /boot/initrd.img-2.6.31.13 2.6.31.13
>     = ; >
>      >
>      > No= w
>      > I see during boot: kernel panic:
>=       >
>      > Mounting root fi= lesystem.
>      > mount: could not find filesystem= '/dev/root'
>      > setting up other filesystems<= br>>      > setting up new root fs
>   = ;   > setuproot: moving /dev failed No such file or directory
&g= t;      > setuproot: error mounting /proc: No such file o= r directory
>      > setuproot: error mounting /sys:= No such file or directory
>      > switchroot: mou= nt failed: No such file or directory
>      > =   kernel panic - not syncing : Attempted to kill init !
>&n= bsp;     >
>      >
>  &nbs= p;   >
>      >
>     = > --- On Thu, 5/13/10, Pasi K=E4rkk=E4inen <pasik@iki.fi> wrot= e:
>      >
>      > From: = Pasi K=E4rkk=E4inen <pasik@iki.fi>
>      >= ; Subject: Re: [Xen-devel] initrd Xen 4.0
>      > = To: "ccmail111" <ccmail111@yahoo.com><= br>>      > Cc: deshantm@gmail.com, xen-devel@lists.xensource.com
>&nbs= p;     > Date: Thursday, May 13, 2010, 4:27 PM
>  &= nbsp;   >
>      > On Thu, May 13, 2010 at = 01:08:36PM -0700, ccmail111 wrote:
>      > >&nb= sp;   The #5 of README is not clear in details.
>    &= nbsp; > >    which directory to run depmod and mkinitrd fro= m ?
>      > >
>      ><= br>>      > It doesn't matter.
>    &n= bsp; >
>      > >    I see:
>=       > >
>      > >   = # depmod xen-4.0.0
>      > >    WARN= ING: Couldn't find symtab and strtab in module xen-4.0.0
>  &nbs= p;   > >
>      >
>    &= nbsp; > Wrong. You need to run depmod for the *kernel*, not for xen.
= >      >
>      > So like this= :
>      > depmod -a 2.6.32.12
>   =   >
>      > Or whatever is your kernel ve= rsion.
>      >
>      > --= Pasi
>      >
>      > >= ;    # ls -l
>      > >    t= otal 1356
>      > >    -rw-r--r-- 1 r= oot root 1380620 May 13 13:05 xen-4.0.0
>      > >
>      > >    Any suggestio= ns ?
>      > >
>      >= >    --- On Wed, 5/12/10, Todd Deshane <deshant= m@gmail.com> wrote:
>      > >
>&nb= sp;     > >      From: Todd Deshane <deshantm@gmail.com>
>      > >&nbs= p;     Subject: Re: [Xen-devel] initrd Xen 4.0
>  &nbs= p;   > >      To: "ccmail111" <cc= mail111@yahoo.com>
>      > >   = ;   Cc: xen-devel@lists.xe= nsource.com
>      > >      D= ate: Wednesday, May 12, 2010, 9:46 PM
>      > >=
>      > >      Hi,
> = ;     > >
>      > >   = ;   See inline.
>      > >
>  &n= bsp;   > >      On Wed, May 12, 2010 at 12:25 PM,= ccmail111
>      <[1]ccmail111@yahoo.= com>
>      > >      wrote= :
>      > >      >
>&nb= sp;     > >      > Hi,
>  &nbs= p;   > >      >
>      &g= t; >      > I downloaded Xen 4.0 and did:
>  =     > >      > make install
> =     > >      > I donot see initrd (ramdi= sk) being created at all.
>      > >   = ;   >
>      > >      >= ; Any suggestions ?
>      > >    &nbs= p; >
>      > >
>      &= gt; >      Step 5 of the README
>    &nbs= p; > >         Depending on your config= , you may need to use 'mkinitrd' to
>      create
&= gt;      > >         an = initial ram disk, just like a native system e.g.
>     = ; > >          # depmod 2.6.18-xen
>      > >       = ;   # mkinitrd -v -f --with=3Daacraid --with=3Dsd_mod
>  &n= bsp;   --with=3Dscsi_mod
>      > >  &= nbsp;   initrd-2.6.18-xen.img 2.6.18-xen
>      &= gt; >         Other systems may requires t= he use of 'mkinitramfs' to
>      create the
>&n= bsp;     > >         ram disk= .
>      > >          #= depmod 2.6.18-xen
>      > >     = ;     # mkinitramfs -o initrd-2.6.18-xen.img 2.6.18-xen
>&n= bsp;     > >
>      > >  &n= bsp;   You may need to change the kernel version based on what you
= >      built.
>      > >      Also some distros use different commands to build= initrd files.
>      > >
>    &= nbsp; > >      I actually forgot about this step for a= second too.
>      > >
>    &nb= sp; > >      Thanks,
>      > = >      Todd
>      > >
>=       > >      --
>    =   > >      Todd Deshane
>    &nbs= p; > >      [2][1]http://todddeshane.net
>      >= ; >      [3][2]http://runningxen.com
>      > >=
>      > > References
>    &nbs= p; > >
>      > >    Visible links=
>      > >    1. file:///mc/compose?t= o=3Dccmail111@yahoo.com
>      > &= gt;    2. [3]http://todddeshane.net/
>      > >  &= nbsp; 3. [4]http://run= ningxen.com/
>      >
>    &nbs= p; > > _______________________________________________
>  =     > > Xen-devel mailing list
>      = > > Xen-devel@lists.xensource.com
>      > > [5]http://lists.xensource.com/xen-devel
>  &= nbsp;   >
>      >
>    &nb= sp; >
>      > _________________________________= ______________
>      > Xen-devel mailing list
&= gt;      > Xen-devel@lis= ts.xensource.com
>      > [6]http://lists.xensource.com= /xen-devel
>      >
>
> References=
>
>    Visible links
>    1. http://todddeshane.net/=
>    2. http://runningxen.com/
>    3. http://todddeshane.net/
>    4. http://runningxen.com/=
>    5. http://lists.xensource.com/xen-devel
>  &nb= sp; 6. h= ttp://lists.xensource.com/xen-devel