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

[Xen-users] Re: [Xen-devel] Xen Dom U kernel

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>
Subject: [Xen-users] Re: [Xen-devel] Xen Dom U kernel
From: kishore kumar <bodkekumar@xxxxxxxxx>
Date: Fri, 16 Apr 2010 15:24:53 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 18 Apr 2010 08:46: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=pHrkPKWuVULZ4sFF7yP9zPCvt0SzTagQVBlf3ipvCTI=; b=UVzkVCkNI6V0I3rIF/X+INsnnz0CATChqSIYcTfqq4UQISKS3yCNrk0dP+qMBvXXDJ d3uJSCLCWyNLRT3rfI31pwREFpy7cksGfBl2eXOgV1Df2A54ba1ZfbAgexCwoGs+1smT 1nMkmIghBeE7SIIuox5jxFqDwUvRUu4gaJOgw=
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=ZA32GFyUV2BBijNimr6hTRG4s/lhh1YDZ8OQUXcbsNgD1elSn1fCJFN0dnI861I/M8 +eiFefTx/1TF26B58CY+xdFbppF5ahlquFvBMphyNSyw0GG+vmSyaULB9cSVi88iJ4HD UftokfLSb2bRLJ0OhY6T8ykc5NHbuuYnLEpeE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BC60244.5070300@xxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <x2s9f975f341004091613z94f85bb9g58c4abb548c71386@xxxxxxxxxxxxxx> <4BC60244.5070300@xxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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?
 
 
[root@localhost xen]# xm list

Name ID Mem VCPUs State Time(s)

Domain-0 0 3621 12 r----- 377.1

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

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

Started domain DomainU (id=1)

Initializing cgroup subsys cpuset

Initializing cgroup subsys cpu

Linux version 2.6.32.10 (kishore@xxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-46)) #2 SMP Wed Mar 17 15:56:57 PDT 2010

Command line: root=/dev/VolGroup01/LogVol00 ro ip=:127.0.255.255::::eth0:dhcp 4

KERNEL supported cpus:

Intel GenuineIntel

AMD AuthenticAMD

Centaur CentaurHauls

ACPI in unprivileged domain disabled

BIOS-provided physical RAM map:

Xen: 0000000000000000 - 00000000000a0000 (usable)

Xen: 00000000000a0000 - 0000000000100000 (reserved)

Xen: 0000000000100000 - 0000000020000000 (usable)

DMI not present or invalid.

last_pfn = 0x20000 max_arch_pfn = 0x400000000

init_memory_mapping: 0000000000000000-0000000020000000

No NUMA configuration found

Faking a node at 0000000000000000-0000000020000000

Bootmem setup node 0 0000000000000000-0000000020000000

NODE_DATA [0000000000008000 - 000000000001ffff]

bootmap [0000000000020000 - 0000000000023fff] pages 4

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

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

#1 [00027aa000 - 00027c3000] XEN PAGETABLES ==> [00027aa000 - 00027c3000]

#2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]

#3 [0001000000 - 0002686dd8] TEXT DATA BSS ==> [0001000000 - 0002686dd8]

#4 [00026a7000 - 00027aa000] XEN START INFO ==> [00026a7000 - 00027aa000]

#5 [0000100000 - 00001e6000] PGTABLE ==> [0000100000 - 00001e6000]

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 1 CPUs, 0 hotplug CPUs

No local APIC present

APIC: disable apic facility

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)

NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:1 nr_node_ids:1

PERCPU: Embedded 478 pages/cpu @ffff8800027d4000 s1928024 r8192 d21672 u1957888

pcpu-alloc: s1928024 r8192 d21672 u1957888 alloc=478*4096

pcpu-alloc: [0] 0

Xen: using vcpu_info placement

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

Policy zone: DMA32

Kernel command line: root=/dev/VolGroup01/LogVol00 ro ip=:127.0.255.255::::eth0:dhcp 4

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

Initializing CPU#0

Checking aperture...

No AGP bridge found

Memory: 483300k/524288k available (4593k kernel code, 384k absent, 40604k reserved, 3427k data, 3392k init)

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

Hierarchical RCU implementation.

NR_IRQS:4352 nr_irqs:256

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: L1 I cache: 32K, L1 D cache: 32K

CPU: L2 cache: 256K

CPU: L3 cache: 12288K

CPU 0/0x5 -> Node 0

CPU: Unsupported number of siblings 32

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

SMP alternatives: switching to UP code

Freeing SMP alternatives: 24k freed

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

ftrace: allocating 27790 entries in 109 pages

Brought up 1 CPUs

Grant table initialized

regulator: core version 0.5

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

NET: Registered protocol family 16

xenbus_probe wake_waiting

xenbus_probe_init ok

PCI: setting up Xen PCI frontend stub

bio: create slab <bio-0> at 0

ACPI: Interpreter disabled.

xenbus_probe_backend_init bus registered ok

xenbus_probe_devices backend

xenbus_probe_devices failed xenbus_directory

backend_probe_and_watch devices probed ok

backend_probe_and_watch watch add ok ok

backend_probe_and_watch all done

xenbus_probe_frontend_init bus registered ok

xenbus_probe_devices device

xenbus_probe_devices 1/2 vif

xenbus_probe_device_type type vif

xenbus_probe_device_type 1/1 0

xenbus_probe_device_type done

xenbus_probe_devices 2/2 console

xenbus_probe_device_type type console

xenbus_probe_device_type 1/1 0

xenbus_probe_device_type done

xenbus_probe_devices done

frontend_probe_and_watch devices probed ok

frontend_probe_and_watch watch add ok ok

frontend_probe_and_watch all done

xen_balloon: Initialising balloon driver with page order 0.

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

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

NET: Registered protocol family 1

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(1271430253.458: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 944

cryptomgr_test used greatest stack depth: 5864 bytes left

cryptomgr_test used greatest stack depth: 5816 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 anticipatory 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 ""

registering netback

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

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.15.0-ioctl (2009-04-01) 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: v2.6:USB HID core driver

nf_conntrack version 0.5.0 (4066 buckets, 16264 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/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

md: Waiting for all devices to be available before autodetect

md: If you don't use raid, use raid=noautodetect

md: Autodetecting RAID arrays.

md: Scanned 0 and added 0 devices.

md: autorun ...

md: ... autorun DONE.

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)

Pid: 1, comm: swapper Not tainted 2.6.32.10 #2

Call Trace:

[<ffffffff8105b747>] panic+0xa5/0x167

[<ffffffff819d2fa6>] ? printk_all_partitions+0x1e7/0x20d

[<ffffffff81460926>] ? klist_next+0x1f/0xa5

[<ffffffff81144ded>] ? sys_mount+0xab/0xbd

[<ffffffff81475ea8>] ? _read_unlock+0x2b/0x30

[<ffffffff819af25e>] mount_block_root+0x258/0x283

[<ffffffff819af2df>] mount_root+0x56/0x5a

[<ffffffff819af453>] prepare_namespace+0x170/0x19d

[<ffffffff819ae9a7>] kernel_init+0x1b8/0x1cc

[<ffffffff81013eaa>] child_rip+0xa/0x20

[<ffffffff8104edcf>] ? finish_task_switch+0x0/0xcc

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

[<ffffffff8108ae5b>] ? trace_hardirqs_off_caller+0x2f/0x89

[<ffffffff81013ea0>] ? child_rip+0x0/0x20



On Wed, Apr 14, 2010 at 10:58 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
On 04/09/2010 04:13 PM, kishore kumar wrote:
> How do I  build Dom U kernel??

Your dom0 kernel will also boot as domU (either PV or HVM).

   J

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