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] boot Xen 4.0

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] boot Xen 4.0
From: ccmail111 <ccmail111@xxxxxxxxx>
Date: Tue, 18 May 2010 14:46:10 -0700 (PDT)
Cc: deshantm@xxxxxxxxx, yingbin wang <yingbin.wangyb@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 18 May 2010 14:47:11 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1274219171; bh=y5eHLtAqdGUJWorhMFrOmrU9uGoqXQxGdxQc3FqNtco=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=FLT7RwF/GFvCGQyty8iX1EVZ3euXhuBQVDTTU4ioCsg6pNgRM/OzCkxni0h4Nt9JwDM4vD1CzkBshXkbM0QJQo+s3MKwvkYn+7YaCDt+uZ13cXUTMU1f1MBJu5O5G4uQOxgxCVGBjHflVn9gkms+Htonrz2V95NqRSrjO7+ad84=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Iv6pFWbkPEQks/0aJg4eEQvux+8gE9Q+Cp4N45kd42hd+Z3G5BEGQA1EihAa/HtIa/TuZ9oK5KVv5Jl3/k25budlVmRlcCFdX7EZcC/FwH5Lt/yNKcjmrNrB+51VKl7BBBzSzTh5LuL1TFo5WqE4Kc3GNZm7vnuvsm8LM6y8Da8=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100518191129.GA17817@xxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Pasi,

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

title Xen 4.0 debug  XenLinux 2.6
        root (hd0,0)
       kernel /xen-4.0.0.gz console=com1, com1=115200,8n1 noreboot loglvl=all  vga=text-80x50,keep iommu=off apic=debug guest_loglvl=all
       module /vmlinuz-2.6.31.13  ro root=/dev/sda3 console=hvc0  earlyprintk=xen nomodeset initcall_debug debug loglevel=10
       module /initrd.img-2.6.31.13


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

      ACPI 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
     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/16550 driver, 4 ports, IRQ sharing enabled

Any thoughts ?

Thanks !
CM

--- On Tue, 5/18/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] boot Xen 4.0
To: "ccmail111" <ccmail111@xxxxxxxxx>
Cc: "yingbin wang" <yingbin.wangyb@xxxxxxxxx>, deshantm@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Tuesday, May 18, 2010, 3:11 PM

On Tue, May 18, 2010 at 12:08:36PM -0700, ccmail111 wrote:
>    Thanks for tip below.
>
>    1) I tried rebuild kernel with option below. I now build kernel with:
>
>    CONFIG_SYSFS_DEPRECATED=y
>    CONFIG_SYSFS_DEPRECATED_V2=y
>
>    But see problem below during boot up as below..
>
>    grub.conf:
>
>    title Xen 4.0 debug  XenLinux 2.6
>            root (hd0,0)
>           kernel /xen-4.0.0.gz console=com1, com1=115200,8n1 noreboot
>    loglvl=all  vga=text-80x50,keep iommu=off apic=debug guest_loglvl=all
>           module /vmlinuz-2.6.31.13  ro root=/dev/ram0 console=hvc0
>    earlyprintk=xen nomodeset initcall_debug debug loglevel=10

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


-- Pasi


>           module /initrd.img-2.6.31.13
>
>    2) Is there a reference (working) ramdisk/initrd for Xen4.0 with busybox
>    or such ? I created ramdisk as:
>
>    # mkinitrd -v -f --builtin=ehci-hcd --builtin=ohci-hcd --builtin=uhci-hcd
>    --builtin=ahci --builtin=aacraid --builtin=aacraid --builtin=sd_mod
>    --builtin=scsi_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)
>    Creating root device.
>    usb 5-1: new full speed USB device using uhci_hcd and address 2
>    Mounting root filesystem.
>    VFS: Can't find ext3 filesystem on dev ram0.
>    mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
>    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.31.13 #8
>    Call Trace:
>     [<ffffffff8106bbeb>] panic+0xb7/0x172
>     [<ffffffff8106fe04>] ? do_exit+0x37c/0x6de
>     [<ffffffff8100fa6f>] ? xen_restore_fl_direct_end+0x0/0x1
>     [<ffffffff810a1c6b>] ? lock_release+0x197/0x1b8
>     [<ffffffff8109ef6e>] ? trace_hardirqs_on+0x20/0x36
>     [<ffffffff815436be>] ? _write_unlock_irq+0x46/0x61
>     [<ffffffff8106fb15>] do_exit+0x8d/0x6de
>     [<ffffffff8107021e>] sys_exit_group+0x0/0x42
>     [<ffffffff8154265c>] ? trace_hardirqs_on_thunk+0x3a/0x3f
>     [<ffffffff81070248>] sys_exit_group+0x2a/0x42
>     [<ffffffff81015332>] system_call_fastpath+0x16/0x1b
>
>    Any suggestions ?
>
>    Thanks !
>
>    CM
>
>    --- On Sat, 5/15/10, yingbin wang <yingbin.wangyb@xxxxxxxxx> wrote:
>
>      From: yingbin wang <yingbin.wangyb@xxxxxxxxx>
>      Subject: Re: [Xen-devel] boot Xen 4.0
>      To: "ccmail111" <ccmail111@xxxxxxxxx>
>      Cc: "Pasi Kärkkäinen" <pasik@xxxxxx>, deshantm@xxxxxxxxx,
>      xen-devel@xxxxxxxxxxxxxxxxxxx
>      Date: Saturday, May 15, 2010, 12:34 PM
>
>      I met similar problems and solved it.
>
>      if your grub.conf is OK, you can try to edit a option of  your .config.
>      CONFIG_SYSFS_DEPRECATED_V2=y
>
>      2010/5/14 ccmail111 <ccmail111@xxxxxxxxx>
>      >
>      > Thanks Pasi/Todd,
>      >
>      > I did:
>      > # mkinitrd -v -f --builtin=ehci-hcd --builtin=ohci-hcd
>      --builtin=uhci-hcd --builtin=ahci --builtin=aacraid --builtin=aacraid
>      --builtin=sd_mod --builtin=scsi_mod /boot/initrd.img-2.6.31.13 2.6.31.13
>      >
>      >
>      > Now
>      > I see during boot: kernel panic:
>      >
>      > 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
>      > setuproot: error mounting /proc: No such file or directory
>      > setuproot: error mounting /sys: No such file or directory
>      > switchroot: mount failed: No such file or directory
>      >   kernel panic - not syncing : Attempted to kill init !
>      >
>      >
>      >
>      >
>      > --- On Thu, 5/13/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>      >
>      > From: Pasi Kärkkäinen <pasik@xxxxxx>
>      > Subject: Re: [Xen-devel] initrd Xen 4.0
>      > To: "ccmail111" <ccmail111@xxxxxxxxx>
>      > Cc: deshantm@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
>      > Date: Thursday, May 13, 2010, 4:27 PM
>      >
>      > On Thu, May 13, 2010 at 01:08:36PM -0700, ccmail111 wrote:
>      > >    The #5 of README is not clear in details.
>      > >    which directory to run depmod and mkinitrd from ?
>      > >
>      >
>      > It doesn't matter.
>      >
>      > >    I see:
>      > >
>      > >    # depmod xen-4.0.0
>      > >    WARNING: Couldn't find symtab and strtab in module xen-4.0.0
>      > >
>      >
>      > 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 version.
>      >
>      > -- Pasi
>      >
>      > >    # ls -l
>      > >    total 1356
>      > >    -rw-r--r-- 1 root root 1380620 May 13 13:05 xen-4.0.0
>      > >
>      > >    Any suggestions ?
>      > >
>      > >    --- On Wed, 5/12/10, Todd Deshane <deshantm@xxxxxxxxx> wrote:
>      > >
>      > >      From: Todd Deshane <deshantm@xxxxxxxxx>
>      > >      Subject: Re: [Xen-devel] initrd Xen 4.0
>      > >      To: "ccmail111" <ccmail111@xxxxxxxxx>
>      > >      Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>      > >      Date: Wednesday, May 12, 2010, 9:46 PM
>      > >
>      > >      Hi,
>      > >
>      > >      See inline.
>      > >
>      > >      On Wed, May 12, 2010 at 12:25 PM, ccmail111
>      <[1]ccmail111@xxxxxxxxx>
>      > >      wrote:
>      > >      >
>      > >      > Hi,
>      > >      >
>      > >      > I downloaded Xen 4.0 and did:
>      > >      > make install
>      > >      > I donot see initrd (ramdisk) being created at all.
>      > >      >
>      > >      > Any suggestions ?
>      > >      >
>      > >
>      > >      Step 5 of the README
>      > >         Depending on your config, you may need to use 'mkinitrd' to
>      create
>      > >         an initial ram disk, just like a native system e.g.
>      > >          # depmod 2.6.18-xen
>      > >          # mkinitrd -v -f --with=aacraid --with=sd_mod
>      --with=scsi_mod
>      > >      initrd-2.6.18-xen.img 2.6.18-xen
>      > >         Other systems may requires the use of 'mkinitramfs' to
>      create the
>      > >         ram disk.
>      > >          # depmod 2.6.18-xen
>      > >          # mkinitramfs -o initrd-2.6.18-xen.img 2.6.18-xen
>      > >
>      > >      You may need to change the kernel version based on what you
>      built.
>      > >      Also some distros use different commands to build initrd files.
>      > >
>      > >      I actually forgot about this step for a second too.
>      > >
>      > >      Thanks,
>      > >      Todd
>      > >
>      > >      --
>      > >      Todd Deshane
>      > >      [2][1]http://todddeshane.net
>      > >      [3][2]http://runningxen.com
>      > >
>      > > References
>      > >
>      > >    Visible links
>      > >    1. file:///mc/compose?to=ccmail111@xxxxxxxxx
>      > >    2. [3]http://todddeshane.net/
>      > >    3. [4]http://runningxen.com/
>      >
>      > > _______________________________________________
>      > > Xen-devel mailing list
>      > > Xen-devel@xxxxxxxxxxxxxxxxxxx
>      > > [5]http://lists.xensource.com/xen-devel
>      >
>      >
>      >
>      > _______________________________________________
>      > Xen-devel mailing list
>      > Xen-devel@xxxxxxxxxxxxxxxxxxx
>      > [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
>    6. 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>