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-users

Re: [Xen-devel] Xen Dom U kernel

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Xen Dom U kernel
From: kishore kumar <bodkekumar@xxxxxxxxx>
Date: Tue, 20 Apr 2010 15:27:56 -0700
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Apr 2010 15:29:04 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=LZWJvZbyglygz76H1OCKG3q5nRiQeU1OM7OMhyjV8jg=; b=osuBCRVpxs4rYVUarUDNmg+L6YHazFoJk6nNeRUnVkuDoTT3GXTR0zC2Hzh4L1iM1+ NRVTCVuZrYoN2EsqlnU8lvqbqTbsfeYHc/vgHTUs1CHIF2BHTVvjRpDVywPU1bp3IPSg /7vlbKuEV44FfQeQ6e2az+jEqSphpHPr0MoH8=
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=ROFxMDVCUh1J0Q1+ntawSWlQ9nBZTuuILrhcOY5HDpL2On656ZZHONy4CFco/litng xRUYAqt3wv8gsbnD/RaJnoGKwoxgfMr5u6YI9zvy90myxUyRI08ZEcjsd/FlsIaKKDCD IhNA6xNYttxjVLuvcOuJiHygRpKj1S6A6cl50=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100419192755.GT1878@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>
References: <x2s9f975f341004091613z94f85bb9g58c4abb548c71386@xxxxxxxxxxxxxx> <4BC60244.5070300@xxxxxxxx> <x2o9f975f341004161524u5fd8c5a1k2983656037e9bc53@xxxxxxxxxxxxxx> <20100417122221.GI1878@xxxxxxxxxxx> <m2l9f975f341004191208kabc2fea9p7b086f1dc5ef1371@xxxxxxxxxxxxxx> <20100419192755.GT1878@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I pulled  PV guest dom U kernel from
Konrad's xen.git in git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git 
  • pv/merge.2.6.33
  • and did
    make menuconfig
    make
    make modules_install install. And below is the output I pasted. 
     
    Can you please let me know what went wrong here? 
     

    [root@localhost xen]# xm create -c /home/kishore/mar_15/xmexample1

    Using config file "/home/kishore/mar_15/xmexample1".

    Started domain Kishore_DomainU (id=1)

    Initializing cgroup subsys cpuset

    Initializing cgroup subsys cpu

    Linux version 2.6.33 (kishore@xxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #1 SMP Tue Apr 20 13:14:56 PDT 2010

    Command line: root=/volGroup01/Logvol00 ro ip=:127.0.255.255::::eth0:dhcp 4

    ACPI in unprivileged domain disabled

    BIOS-provided physical RAM map:

    Xen: 0000000000000000 - 00000000000a0000 (usable)

    Xen: 00000000000a0000 - 0000000000100000 (reserved)

    Xen: 0000000000100000 - 0000000020000000 (usable)

    NX (Execute Disable) protection: active

    DMI not present or invalid.

    No AGP bridge found

    last_pfn = 0x20000 max_arch_pfn = 0x400000000

    init_memory_mapping: 0000000000000000-0000000020000000

    RAMDISK: 029d4000 - 03008000

    No NUMA configuration found

    Faking a node at 0000000000000000-0000000020000000

    Bootmem setup node 0 0000000000000000-0000000020000000

    NODE_DATA [0000000000007000 - 000000000001efff]

    bootmap [000000000001f000 - 0000000000022fff] pages 4

    (8 early reservations) ==> bootmem [0000000000 - 0020000000]

    #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]

    #1 [000310b000 - 0003128000] XEN PAGETABLES ==> [000310b000 - 0003128000]

    #2 [0001000000 - 00029b3878] TEXT DATA BSS ==> [0001000000 - 00029b3878]

    #3 [00029d4000 - 0003008000] RAMDISK ==> [00029d4000 - 0003008000]

    #4 [0003008000 - 000310b000] XEN START INFO ==> [0003008000 - 000310b000]

    #5 [0000001000 - 0000003000] TRAMPOLINE ==> [0000001000 - 0000003000]

    #6 [0000003000 - 0000007000] ACPI WAKEUP ==> [0000003000 - 0000007000]

    #7 [0000100000 - 00001e2000] PGTABLE ==> [0000100000 - 00001e2000]

    Zone PFN ranges:

    DMA 0x00000000 -> 0x00001000

    DMA32 0x00001000 -> 0x00100000

    Normal 0x00100000 -> 0x00100000

    Movable zone start PFN for each node

    early_node_map[2] active PFN ranges

    0: 0x00000000 -> 0x000000a0

    0: 0x00000100 -> 0x00020000

    SMP: Allowing 5 CPUs, 0 hotplug CPUs

    No local APIC present

    APIC: disable apic facility

    APIC: switched to apic NOOP

    PM: Registered nosave memory: 00000000000a0000 - 0000000000100000

    Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000)

    Booting paravirtualized kernel on Xen

    Xen version: 3.4.3-rc4-pre (preserve-AD)

    setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:5 nr_node_ids:1

    PERCPU: Embedded 478 pages/cpu @ffff880003c2f000 s1928344 r8192 d21352 u1957888

    pcpu-alloc: s1928344 r8192 d21352 u1957888 alloc=478*4096

    pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4

    Xen: using vcpu_info placement

    Built 1 zonelists in Node order, mobility grouping on. Total pages: 128951

    Policy zone: DMA32

    Kernel command line: root=/volGroup01/Logvol00 ro ip=:127.0.255.255::::eth0:dhcp 4

    PID hash table entries: 2048 (order: 2, 16384 bytes)

    Checking aperture...

    No AGP bridge found

    Memory: 472204k/524288k available (4689k kernel code, 384k absent, 51700k reserved, 6678k data, 3392k init)

    SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=5, Nodes=1

    Hierarchical RCU implementation.

    NR_IRQS:4352 nr_irqs:312

    Console: colour dummy device 80x25

    console [tty0] enabled

    console [hvc0] enabled

    Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar

    ... MAX_LOCKDEP_SUBCLASSES: 8

    ... MAX_LOCK_DEPTH: 48

    ... MAX_LOCKDEP_KEYS: 8191

    ... CLASSHASH_SIZE: 4096

    ... MAX_LOCKDEP_ENTRIES: 16384

    ... MAX_LOCKDEP_CHAINS: 32768

    ... CHAINHASH_SIZE: 16384

    memory used by lock dependency info: 6367 kB

    per task-struct memory footprint: 2688 bytes

    allocated 5242880 bytes of page_cgroup

    please try 'cgroup_disable=memory' option if you don't want memory cgroups

    installing Xen timer for CPU 0

    Detected 3200.112 MHz processor.

    Calibrating delay loop (skipped), value calculated using timer frequency.. 6400.22 BogoMIPS (lpj=3200112)

    Security Framework initialized

    SELinux: Initializing.

    Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)

    Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)

    Mount-cache hash table entries: 256

    Initializing cgroup subsys ns

    Initializing cgroup subsys cpuacct

    Initializing cgroup subsys memory

    Initializing cgroup subsys devices

    Initializing cgroup subsys freezer

    Initializing cgroup subsys net_cls

    CPU: Unsupported number of siblings 32

    Performance Events: unsupported p6 CPU model 44 no PMU driver, software events only.

    lockdep: fixing up alternatives.

    SMP alternatives: switching to UP code

    ftrace: converting mcount calls to 0f 1f 44 00 00

    ftrace: allocating 27220 entries in 107 pages

    installing Xen timer for CPU 1

    lockdep: fixing up alternatives.

    SMP alternatives: switching to SMP code

    CPU: Unsupported number of siblings 32

    installing Xen timer for CPU 2

    CPU: Unsupported number of siblings 32

    installing Xen timer for CPU 3

    CPU: Unsupported number of siblings 32

    installing Xen timer for CPU 4

    CPU: Unsupported number of siblings 32

    Brought up 5 CPUs

    Grant table initialized

    regulator: core version 0.5

    Time: 165:165:165 Date: 165/165/65

    NET: Registered protocol family 16

    PCI: setting up Xen PCI frontend stub

    bio: create slab <bio-0> at 0

    ACPI: Interpreter disabled.

    xen_balloon: Initialising balloon driver.

    vgaarb: loaded

    SCSI subsystem initialized

    usbcore: registered new interface driver usbfs

    usbcore: registered new interface driver hub

    usbcore: registered new device driver usb

    PCI: System does not support PCI

    PCI: System does not support PCI

    NetLabel: Initializing

    NetLabel: domain hash size = 128

    NetLabel: protocols = UNLABELED CIPSOv4

    NetLabel: unlabeled traffic allowed by default

    Switching to clocksource xen

    kstop/0 used greatest stack depth: 6568 bytes left

    kstop/1 used greatest stack depth: 6552 bytes left

    pnp: PnP ACPI: disabled

    NET: Registered protocol family 2

    IP route cache hash table entries: 4096 (order: 3, 32768 bytes)

    TCP established hash table entries: 16384 (order: 6, 262144 bytes)

    TCP bind hash table entries: 16384 (order: 8, 1179648 bytes)

    TCP: Hash tables configured (established 16384 bind 16384)

    TCP reno registered

    UDP hash table entries: 256 (order: 3, 40960 bytes)

    UDP-Lite hash table entries: 256 (order: 3, 40960 bytes)

    NET: Registered protocol family 1

    Trying to unpack rootfs image as initramfs...

    Freeing initrd memory: 6352k freed

    DMA-API: preallocated 32768 debug entries

    DMA-API: debugging enabled by kernel config

    platform rtc_cmos: registered platform RTC device (no PNP device found)

    audit: initializing netlink socket (disabled)

    type=2000 audit(1271770990.281:1): initialized

    HugeTLB registered 2 MB page size, pre-allocated 0 pages

    VFS: Disk quotas dquot_6.5.2

    Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

    msgmni has been set to 934

    cryptomgr_test used greatest stack depth: 5368 bytes left

    alg: No test for stdrng (krng)

    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)

    io scheduler noop registered

    io scheduler deadline registered

    io scheduler cfq registered (default)

    pci_hotplug: PCI Hot Plug PCI Core version: 0.5

    pciehp: PCI Express Hot Plug Controller Driver version: 0.4

    acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5

    pci-stub: invalid id string ""

    Non-volatile memory driver v1.3

    Linux agpgart interface v0.103

    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

    brd: module loaded

    loop: module loaded

    input: Macintosh mouse button emulation as /class/input/input0

    Fixed MDIO Bus: probed

    ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 2.0.44-k2

    ixgbe: Copyright (c) 1999-2010 Intel Corporation.

    Intel(R) PRO/10GbE Network Driver - version 1.0.135-k2-NAPI

    Copyright (c) 1999-2008 Intel Corporation.

    Initialising Xen virtual ethernet driver.

    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver

    uhci_hcd: USB Universal Host Controller Interface driver

    blkfront: xvda2: barriers enabled

    PNP: No PS/2 controller found. Probing ports directly.

    i8042.c: No controller found.

    mice: PS/2 mouse device common for all mice

    rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0

    device-mapper: uevent: version 1.0.3

    device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@xxxxxxxxxx

    cpuidle: using governor ladder

    cpuidle: using governor menu

    usbcore: registered new interface driver hiddev

    usbcore: registered new interface driver usbhid

    usbhid: USB HID core driver

    nf_conntrack version 0.5.0 (3738 buckets, 14952 max)

    CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use

    nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or

    sysctl net.netfilter.nf_conntrack_acct=1 to enable it.

    ip_tables: (C) 2000-2006 Netfilter Core Team

    TCP cubic registered

    Initializing XFRM netlink socket

    NET: Registered protocol family 17

    registered taskstats version 1

    No TPM chip found, activating TPM-bypass!

    XENBUS: Device with no driver: device/console/0

    Magic number: 1:252:3141

    drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

    Initalizing network drop monitor service

    Freeing unused kernel memory: 3392k freed

    Write protecting the kernel read-only data: 10240k

    Freeing unused kernel memory: 1436k freed

    BUG: unable to handle kernel paging request at ffff880001499000

    IP: [<ffffffff8122b8a0>] memset_c+0x20/0x30

    PGD 1a44067 PUD 1a48067 PMD 3118067 PTE 10000001499025

    Oops: 0003 [#1] SMP

    last sysfs file:

    CPU 4

    Pid: 1, comm: swapper Not tainted 2.6.33 #1 /

    RIP: e030:[<ffffffff8122b8a0>] [<ffffffff8122b8a0>] memset_c+0x20/0x30

    RSP: e02b:ffff88001fdf7e68 EFLAGS: 00010206

    RAX: cccccccccccccccc RBX: ffffea0000000000 RCX: 0000000000000200

    RDX: 0000000000000000 RSI: 00000000000000cc RDI: ffff880001499000

    RBP: ffff88001fdf7e90 R08: 0000000000000000 R09: ffff880001499000

    R10: ffff88001fc04248 R11: ffff88001fdf7ba0 R12: ffff880001499000

    R13: ffff880001600000 R14: ffffffff81789ef8 R15: 0000000000000000

    FS: 0000000000000000(0000) GS:ffff8800043a7000(0000) knlGS:0000000000000000

    CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b

    CR2: ffff880001499000 CR3: 0000000001a43000 CR4: 0000000000002660

    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

    DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400

    Process swapper (pid: 1, threadinfo ffff88001fdf6000, task ffff88001fdf8000)

    Stack:

    ffffffff8102fdda 6db6db6db6db6db7 0000000000000400 ffff880000000000

    <0> ffffffff81600000 ffff88001fdf7ec0 ffffffff810305c6 ffffffff81e5d8a0

    <0> 0000000000000200 0000000000000200 ffffffff81b12f80 ffff88001fdf7ed0

    Call Trace:

    [<ffffffff8102fdda>] ? free_init_pages+0xa4/0xca

    [<ffffffff810305c6>] mark_rodata_ro+0xea/0x150

    [<ffffffff81002200>] init_post+0x30/0x114

    [<ffffffff81cf29a8>] kernel_init+0x1be/0x1cd

    [<ffffffff8100ab64>] kernel_thread_helper+0x4/0x10

    [<ffffffff8148d910>] ? restore_args+0x0/0x30

    [<ffffffff8100ab60>] ? kernel_thread_helper+0x0/0x10

    Code: 83 f9 ff 75 ed c9 4c 89 c0 c3 90 49 89 f9 41 89 d0 41 83 e0 07 89 d1 c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 f7 e6 <f3> 48 ab 44 89 c1 f3 aa 4c 89 c8 c3 0f 1f 40 00 eb ce 0f 1f 84

    RIP [<ffffffff8122b8a0>] memset_c+0x20/0x30

    RSP <ffff88001fdf7e68>

    CR2: ffff880001499000

    ---[ end trace 578e9e3c60fdfb1a ]---

    swapper used greatest stack depth: 4952 bytes left

    Kernel panic - not syncing: Attempted to kill init!

    Pid: 1, comm: swapper Tainted: G D 2.6.33 #1

    Call Trace:

    [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02

    [<ffffffff8105145a>] panic+0xa5/0x171

    [<ffffffff81054e15>] ? do_exit+0x325/0x6f5

    [<ffffffff81006891>] ? xen_force_evtchn_callback+0xd/0xf

    [<ffffffff81054e15>] ? do_exit+0x325/0x6f5

    [<ffffffff81054e65>] ? do_exit+0x375/0x6f5

    [<ffffffff81054e15>] ? do_exit+0x325/0x6f5

    [<ffffffff81006f4f>] ? xen_restore_fl_direct_end+0x0/0x1

    [<ffffffff81081534>] ? lock_release+0x182/0x18d

    [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02

    [<ffffffff8107ed49>] ? trace_hardirqs_on+0xd/0xf

    [<ffffffff8148cefb>] ? _raw_write_unlock_irq+0x37/0x3b

    [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02

    [<ffffffff81054b6c>] do_exit+0x7c/0x6f5

    [<ffffffff81052cf2>] ? kmsg_dump+0x153/0x183

    [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02

    [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02

    [<ffffffff8148e850>] oops_end+0xbf/0xc7

    [<ffffffff81030eb2>] no_context+0x1fa/0x209

    [<ffffffff812200af>] ? compat_blkdev_driver_ioctl+0x1e2/0xf02

    [<ffffffff81004748>] ? xen_pmd_val+0xe/0x10

    [<ffffffff81031118>] __bad_area_nosemaphore+0x198/0x1bb

    [<ffffffff8148d940>] ? irq_return+0x0/0x10

    [<ffffffff810311c5>] bad_area_nosemaphore+0x13/0x15

    [<ffffffff81490256>] do_page_fault+0x16d/0x2a2

    [<ffffffff8148dbb5>] page_fault+0x25/0x30

    [<ffffffff8122b8a0>] ? memset_c+0x20/0x30

    [<ffffffff8102fdda>] ? free_init_pages+0xa4/0xca

    [<ffffffff810305c6>] mark_rodata_ro+0xea/0x150

    [<ffffffff81002200>] init_post+0x30/0x114

    [<ffffffff81cf29a8>] kernel_init+0x1be/0x1cd

    [<ffffffff8100ab64>] kernel_thread_helper+0x4/0x10

    [<ffffffff8148d910>] ? restore_args+0x0/0x30

    [<ffffffff8100ab60>] ? kernel_thread_helper+0x0/0x10

     
     
     


     
    On Mon, Apr 19, 2010 at 12:27 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
    On Mon, Apr 19, 2010 at 12:08:35PM -0700, kishore kumar wrote:
    >    I included
    >    kernel = "/boot/vmlinuz-2.6.32.10"
    >    ramdisk = "/boot/initrd-2.6.32.10.img" (This is the same as my Dom 0.  As
    >    I am trying to boot the same Dom 0 as my Dom U without any changes)
    >

    You cannot use the dom0 initrd/ramdisk for domU!

    dom0 initrd contains drivers for the physical hardware, while in the domU initrd
    you need to have drivers for the _virtual_ hardware!

    In the log below root was not found because the drivers for the xen block devices
    are not loaded.

    -- Pasi


    >    disk = ['phy:sda2,sda2,w']
    >    root= "/dev/VolGroup01/LogVol00 ro"
    >
    >      I see my .config and I have
    >    CONFIG_XEN_BLKDEV_FRONTEND=m
    >    CONFIG_XEN_BLKDEV_BACKEND=y
    >    CONFIG_XEN_BACKEND=y
    >
    >    Below is the output pasted.  Any help please on what is going wrong here?
    >
    >    XENBUS: Device with no driver: device/vbd/2050
    >
    >    XENBUS: Device with no driver: device/vif/0
    >
    >    XENBUS: Device with no driver: device/console/0
    >
    >    Magic number: 1:252:3141
    >
    >    drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
    >
    >    Initalizing network drop monitor service
    >
    >    Freeing unused kernel memory: 3392k freed
    >
    >    Write protecting the kernel read-only data: 6912k
    >
    >    Red Hat nash version 5.1.19.6 starting
    >
    >    Mounting proc filesystem
    >
    >    Mounting sysfs filesystem
    >
    >    Creating /dev
    >
    >    Creating initial device nodes
    >
    >    Setting up hotplug.
    >
    >    Creating block device nodes.
    >
    >    Loading ehci-hcd.ko module
    >
    >    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    >
    >    insmod used greatest stack depth: 5712 bytes left
    >
    >    Loading ssb.ko module
    >
    >    Loading ohci-hcd.ko module
    >
    >    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    >
    >    Loading uhci-hcd.ko module
    >
    >    uhci_hcd: USB Universal Host Controller Interface driver
    >
    >    Scanning and configuring dmraid supported devices
    >
    >    Scanning logical volumes
    >
    >    Reading all physical volumes. This may take a while...
    >
    >    lvm used greatest stack depth: 5328 bytes left
    >
    >    Activating logical volumes
    >
    >    Volume group "VolGroup01" not found
    >
    >    Trying to resume from /dev/VolGroup01/LogVol01
    >
    >    Unable to access resume device (/dev/VolGroup01/LogVol01)
    >
    >    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
    >
    >    init used greatest stack depth: 4888 bytes left
    >
    >    Kernel panic - not syncing: Attempted to kill init!
    >
    >    Pid: 1, comm: init Not tainted 2.6.32.10 #2
    >
    >    Call Trace:
    >
    >    [<ffffffff8105b747>] panic+0xa5/0x167
    >
    >    [<ffffffff8100ed81>] ? xen_force_evtchn_callback+0xd/0xf
    >
    >    [<ffffffff81475d48>] ? _write_unlock_irq+0x30/0x3c
    >
    >    [<ffffffff8108c9f4>] ? trace_hardirqs_on_caller+0x110/0x134
    >
    >    [<ffffffff8108ca25>] ? trace_hardirqs_on+0xd/0xf
    >
    >    [<ffffffff81475d4f>] ? _write_unlock_irq+0x37/0x3c
    >
    >    [<ffffffff8105efa7>] do_exit+0x7e/0x701
    >
    >    [<ffffffff8105f6c6>] sys_exit_group+0x0/0x1b
    >
    >    [<ffffffff8105f6dd>] sys_exit_group+0x17/0x1b
    >
    >    [<ffffffff81012d72>] system_call_fastpath+0x16/0x1b
    >
    >    On Sat, Apr 17, 2010 at 5:22 AM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote:
    >
    >      On Fri, Apr 16, 2010 at 03:24:53PM -0700, kishore kumar wrote:
    >      >    I am using my Dom 0 kernel to boot as my Dom U.
    >      >    I edited /etc/xen/xmexample1 file and modified only below lines
    >      >
    >      >    kernel="/boot/vmlinux-2.6.32.10"
    >      >    memory=512
    >      >    vcpus=5
    >      >    root = "/dev/VolGroup01/LogVol00 ro"
    >      >    Below is the output I pasted after freezing.  Not sure what is
    >      wrong.  Can
    >      >    you please help me here??
    >      >    I doubt if I have provided the correct root option?
    >      >
    >
    >      I bet that kernel has xen block frontend driver as a module?
    >
    >      You don't seem to have ramdisk/initrd image,
    >      so you simply don't have the driver loaded at all
    >      to access the root disk in the guest.
    >
    >      You must create an initrd image that loads the driver module in the
    >      guest.
    >      >
    >      >    VFS: Cannot open root device "VolGroup01/LogVol00" or
    >      unknown-block(0,0)
    >      >
    >      >    Please append a correct "root=" boot option; here are the available
    >      >    partitions:
    >      >
    >      >    Kernel panic - not syncing: VFS: Unable to mount root fs on
    >      >    unknown-block(0,0)
    >      >
    >
    >      Root was not found - this is usually because you don't have the xen
    >      blockdev frontend driver loaded.
    >      -- Pasi
    >
    > References
    >
    >    Visible links
    >    1. mailto:pasik@xxxxxx

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