From: ccmail111 <ccmail111@yahoo.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: deshantm@gmail.com, yingbin wang <yingbin.wangyb@gmail.com>,
xen-devel@lists.xensource.com
Subject: Re: boot Xen 4.0
Date: Fri, 4 Jun 2010 13:30:06 -0700 (PDT) [thread overview]
Message-ID: <549893.93295.qm@web34204.mail.mud.yahoo.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 16895 bytes --]
Hi Pasi,
Here is output of serial console where I see Xen4.0 stuck during boot up:
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen kernel: 64-bit, lsb, compat32
(XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2768000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 00000000b4000000->00000000b8000000 (725348 pages to be all
ocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff81000000->ffffffff82768000
(XEN) Init. ramdisk: ffffffff82768000->ffffffff82c1ec00
(XEN) Phys-Mach map: ffffffff82c1f000->ffffffff831c7b20
(XEN) Start info: ffffffff831c8000->ffffffff831c84b4
(XEN) Page tables: ffffffff831c9000->ffffffff831e6000
(XEN) Boot stack: ffffffff831e6000->ffffffff831e7000
(XEN) TOTAL: ffffffff80000000->ffffffff83400000
(XEN) ENTRY ADDRESS: ffffffff81a63200
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen
)
(XEN) Freed 156kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.32.13 (gcc version 4.1.2 20080704 (Red Hat
4.1.2-44)) #2 SMP Thu May 20 17:22:39 PDT 2010
Command line: ro root=/dev/sda2 console=hvc0 earlyprintk=xen nomodeset debug log
level=10
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
released 0 pages of unused memory
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000000095800 (usable)
Xen: 0000000000095800 - 0000000000100000 (reserved)
Xen: 0000000000100000 - 00000000b5164000 (usable)
Xen: 00000000bf7a5800 - 00000000c0000000 (reserved)
Xen: 00000000f0000000 - 00000000f8000000 (reserved)
Xen: 00000000fec00000 - 00000000fed40000 (reserved)
Xen: 00000000fed45000 - 0000000100000000 (reserved)
bootconsole [xenboot0] enabled
DMI 2.6 present.
last_pfn = 0xb5164 max_arch_pfn = 0x400000000
x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106
initial memory mapped : 0 - 20000000
init_memory_mapping: 0000000000000000-00000000b5164000
0000000000 - 00b5164000 page 4k
kernel direct mapping tables up to b5164000 @ 100000-6ad000
RAMDISK: 02768000 - 02c1ec00
ACPI: RSDP 00000000000e9010 00024 (v02 HP
ACPI: XSDT 00000000bf7b88e8 0006C (v01 HPQOEM SLIC-WKS 20091208 00000000)
ACPI: FACP 00000000bf7b8a88 000F4 (v03 HPQOEM TYLSBURG 00000001 00000000)
ACPI: DSDT 00000000bf7b92d7 0A73D (v01 COMPAQ DSDT_PRJ 00000001 MSFT 0100000E)
ACPI: FACS 00000000bf7b8800 00040
ACPI: APIC 00000000bf7b8b7c 00114 (v01 HPQOEM TYLSBURG 00000001 00000000)
ACPI: ASF! 00000000bf7b8c90 00063 (v32 HPQOEM TYLSBURG 00000001 00000000)
ACPI: MCFG 00000000bf7b8cf3 0003C (v01 HPQOEM TYLSBURG 00000001 00000000)
ACPI: TCPA 00000000bf7b8d2f 00032 (v01 HPQOEM TYLSBURG 00000001 00000000)
ACPI: SLIC 00000000bf7b8d61 00176 (v01 HPQOEM SLIC-WKS 00000001 00000000)
ACPI: HPET 00000000bf7b8ed7 00038 (v01 HPQOEM TYLSBURG 00000001 00000000)
ACPI: 00000000bf7b8f0f 001B8 (v01 HPQOEM TYLSBURG 00000001 00000000)
ACPI: SSDT 00000000bf7c4ee6 011FC (v01 INTEL PPM RCM 80000001 INTL 20061109)
ACPI: Local APIC address 0xfee00000
No NUMA configuration found
Faking a node at 0000000000000000-00000000b5164000
Bootmem setup node 0 0000000000000000-00000000b5164000
NODE_DATA [0000000000008000 - 000000000001ffff]
bootmap [0000000000020000 - 0000000000036a2f] pages 17
(8 early reservations) ==> bootmem [0000000000 - 00b5164000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [00031c9000 - 00031e6000] XEN PAGETABLES ==> [00031c9000 - 00031e6000]
#2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
#3 [0001000000 - 0002747680] TEXT DATA BSS ==> [0001000000 - 0002747680]
#4 [0002768000 - 0002c1ec00] RAMDISK ==> [0002768000 - 0002c1ec00]
#5 [0002c1f000 - 00031c9000] XEN START INFO ==> [0002c1f000 - 00031c9000]
#6 [0002748000 - 0002748120] BRK ==> [0002748000 - 0002748120]
#7 [0000100000 - 000068d000] PGTABLE ==> [0000100000
Any thoughts ?
Thanks !
CM
--- On Tue, 5/18/10, ccmail111 <ccmail111@yahoo.com> wrote:
From: ccmail111 <ccmail111@yahoo.com>
Subject: Re: [Xen-devel] boot Xen 4.0
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "yingbin wang" <yingbin.wangyb@gmail.com>, deshantm@gmail.com, xen-devel@lists.xensource.com
Date: Tuesday, May 18, 2010, 5:46 PM
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@iki.fi> wrote:
From: Pasi Kärkkäinen <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
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@gmail.com> wrote:
>
> From: yingbin wang <yingbin.wangyb@gmail.com>
> Subject: Re: [Xen-devel] boot Xen 4.0
> To: "ccmail111" <ccmail111@yahoo.com>
> Cc: "Pasi Kärkkäinen" <pasik@iki.fi>, deshantm@gmail.com,
> xen-devel@lists.xensource.com
> 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@yahoo.com>
> >
> > 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@iki.fi> wrote:
> >
> > From: Pasi Kärkkäinen <pasik@iki.fi>
> > Subject: Re: [Xen-devel] initrd Xen 4.0
> > To: "ccmail111" <ccmail111@yahoo.com>
> > Cc: deshantm@gmail.com, xen-devel@lists.xensource.com
> > 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@gmail.com> wrote:
> > >
> > > From: Todd Deshane <deshantm@gmail.com>
> > > Subject: Re: [Xen-devel] initrd Xen 4.0
> > > To: "ccmail111" <ccmail111@yahoo.com>
> > > Cc: xen-devel@lists.xensource.com
> > > Date: Wednesday, May 12, 2010, 9:46 PM
> > >
> > > Hi,
> > >
> > > See inline.
> > >
> > > On Wed, May 12, 2010 at 12:25 PM, ccmail111
> <[1]ccmail111@yahoo.com>
> > > 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@yahoo.com
> > > 2. [3]http://todddeshane.net/
> > > 3. [4]http://runningxen.com/
> >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > [5]http://lists.xensource.com/xen-devel
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.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
> 6. http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 37698 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-06-04 20:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 20:30 ccmail111 [this message]
2010-06-04 20:34 ` boot Xen 4.0 Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2010-06-21 20:54 ccmail111
2010-06-22 17:30 ` Konrad Rzeszutek Wilk
2010-06-17 18:27 ccmail111
2010-06-10 16:02 ccmail111
2010-06-15 21:26 ` Konrad Rzeszutek Wilk
2010-05-18 19:08 ccmail111
2010-05-18 19:11 ` Pasi Kärkkäinen
2010-05-18 21:46 ` ccmail111
2010-05-26 17:44 ` Konrad Rzeszutek Wilk
2010-05-14 1:42 ccmail111
2010-05-14 5:55 ` Pasi Kärkkäinen
2010-05-15 16:34 ` yingbin wang
2010-05-17 20:17 ` ccmail111
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=549893.93295.qm@web34204.mail.mud.yahoo.com \
--to=ccmail111@yahoo.com \
--cc=deshantm@gmail.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
--cc=yingbin.wangyb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).