thr3ads.net - Xen users - [Xen-users] Xen domU cannot boot via PV-GRUB [Jan 2011]

If this information is useful, please help other people find it:
Share via:

GNUbie

2011-Jan-13 17:03 UTC

[Xen-users] Xen domU cannot boot via PV-GRUB

Hello all,

Please advice on how I can move forward from this bootup problem. I
already tried changing the value of the "root=" option to /dev/sda2
and /dev/xvda2 with no luck. I also tried to re-generate a new initrd
adding the options of "--with xennet --with xenblk" but still with no
luck.

Below are some information of the domU:

- - - < s n i p > - - -
# pwd
/boot

# ls -l
total 7292
lrwxrwxrwx 1 root root       1 Jan 13 16:33 boot -> .
-rw-r--r-- 1 root root   64217 Oct 23 03:50 config-2.6.34.7-56.40.i686
drwxr-xr-x 2 root root    1024 Jan 13 20:03 grub
-rw------- 1 root root 2130577 Nov 10 16:45 initrd-2.6.34.7-56.40.i686.img
drwx------ 2 root root   12288 Jan 13 16:13 lost+found
-rw-r--r-- 1 root root   21047 Jul 28 06:11 message
-rw-r--r-- 1 root root  972728 Oct 23 03:50 System.map-2.6.34.7-56.40.i686
-rwxr-xr-x 1 root root 2110080 Oct 23 03:50 vmlinuz-2.6.34.7-56.40.i686

# cat grub/menu.lst
default=0
timeout=1
hiddenmenu

title GNU/Linux (2.6.34.7-56.40.i686)
    root (hd0,0)
    kernel /boot/vmlinuz-2.6.34.7-56.40.i686 root=LABEL=/ console=hvc0
    initrd /boot/initrd-2.6.34.7-56.40.i686.img

# cat fstab
LABEL=/boot /boot       ext3    defaults            1   2
LABEL=/     /           ext3    defaults            1   1
tmpfs       /dev/shm    tmpfs   defaults            0   0
devpts      /dev/pts    devpts  gid=5,mode=620      0   0
sysfs       /sys        sysfs   defaults            0   0
proc        /proc       proc    defaults            0   0
none        /proc/xen   xenfs   defaults            0   0

# cat /etc/modprobe.conf
alias eth0 xennet
alias scsi_hostadapter xenblk
alias ipv6 off
alias net-pf-10 off
options ipv6 disable=1
- - - < s n i p > - - -



Below are the bootup logs:

- - - < s n i p > - - -
    Xen Minimal OS!
  start_info: 0xb10000(VA)
    nr_pages: 0x6a400
  shared_inf: 0x002e9000(MA)
     pt_base: 0xb13000(VA)
nr_pt_frames: 0x9
    mfn_list: 0x967000(VA)
   mod_start: 0x0(VA)
     mod_len: 0
       flags: 0x0
    cmd_line:  root=/dev/sda2 ro 4
  stack:      0x946780-0x966780
MM: Init
      _text: 0x0(VA)
     _etext: 0x621f5(VA)
   _erodata: 0x76000(VA)
     _edata: 0x7b6d4(VA)
stack start: 0x946780(VA)
       _end: 0x966d34(VA)
  start_pfn: b1f
    max_pfn: 6a400
Mapping memory range 0xc00000 - 0x6a400000
setting 0x0-0x76000 readonly
skipped 0x1000
MM: Initialise page allocator for e6c000(e6c000)-0(6a400000)
MM: done
Demand map pfns at 6a401000-7a401000.
Heap resides at 7a402000-ba402000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x6a401000.
Initialising scheduler
Thread "Idle": pointer: 0x7a402008, stack: 0x6a030000
Initialising xenbus
Thread "xenstore": pointer: 0x7a402478, stack: 0x6a040000
Dummy main: start_info=0x966880
Thread "main": pointer: 0x7a4028e8, stack: 0x6a050000
"main" "root=/dev/sda2" "ro" "4"
vbd 2050 is hd0
******************* BLKFRONT for device/vbd/2050 **********


backend at /local/domain/0/backend/vbd/3321/2050
Failed to read /local/domain/0/backend/vbd/3321/2050/feature-barrier.
Failed to read /local/domain/0/backend/vbd/3321/2050/feature-flush-cache.
4194304 sectors of 0 bytes
**************************
vbd 2051 is hd1
******************* BLKFRONT for device/vbd/2051 **********


backend at /local/domain/0/backend/vbd/3321/2051
Failed to read /local/domain/0/backend/vbd/3321/2051/feature-barrier.
Failed to read /local/domain/0/backend/vbd/3321/2051/feature-flush-cache.
1835008 sectors of 0 bytes
**************************
vbd 2064 is hd2
******************* BLKFRONT for device/vbd/2064 **********


backend at /local/domain/0/backend/vbd/3321/2064
Failed to read /local/domain/0/backend/vbd/3321/2064/feature-barrier.
Failed to read /local/domain/0/backend/vbd/3321/2064/feature-flush-cache.
312705024 sectors of 0 bytes
**************************

Press `ESC'' to enter the menu... 0
    [H
    [J  Booting ''GNU/Linux (2.6.34.7-56.40.i686)''



root (hd0,0)

 Filesystem type is ext2fs, partition type 0x83

kernel /boot/vmlinuz-2.6.34.7-56.40.i686 root=LABEL=/ console=hvc0

initrd /boot/initrd-2.6.34.7-56.40.i686.img



close blk: backend at /local/domain/0/backend/vbd/3321/2050
close blk: backend at /local/domain/0/backend/vbd/3321/2051
close blk: backend at /local/domain/0/backend/vbd/3321/2064
[    0.000000] Reserving virtual address space above 0xf5800000
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.34.7-56.40.i686
(mockbuild@build-31003.build) (gcc version 4.4.4 20100525 (Red Hat
4.4.4-5) (GCC) ) #1 SMP Fri Oct 22 18:48:33 UTC 2010
[    0.000000] ACPI in unprivileged domain disabled
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
[    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 000000006a400000 (usable)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] last_pfn = 0x6a400 max_arch_pfn = 0x1000000
[    0.000000] init_memory_mapping: 0000000000000000-000000002d3fe000
[    0.000000] RAMDISK: 0156f000 - 019d5000
[    0.000000] 976MB HIGHMEM available.
[    0.000000] 723MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 2d3fe000
[    0.000000]   low ram: 0 - 2d3fe000
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000001 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x0002d3fe
[    0.000000]   HighMem  0x0002d3fe -> 0x0006a400
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000001 -> 0x000000a0
[    0.000000]     0: 0x00000100 -> 0x0006a400
[    0.000000] Using APIC driver default
[    0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[    0.000000] Local APIC disabled by BIOS -- you can enable it with
"lapic"
[    0.000000] APIC: disable apic facility
[    0.000000] APIC: switched to apic NOOP
[    0.000000] Allocating PCI resources starting at 6a400000 (gap:
6a400000:95c00000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 3.0.3-rc5-8.1.14.f
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1
nr_node_ids:1
[    0.000000] PERCPU: Embedded 16 pages/cpu @c1453000 s41172 r0 d24364 u65536
[    0.000000] pcpu-alloc: s41172 r0 d24364 u65536 alloc=16*4096
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 431702
[    0.000000] Kernel command line: root=LABEL=/ console=hvc0
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] Subtract (33 early reservations)
[    0.000000]   #1 [0001b81000 - 0001b93000]  XEN PAGETABLES
[    0.000000]   #2 [0000001000 - 0000002000]   EX TRAMPOLINE
[    0.000000]   #3 [0001000000 - 0001449b5c]   TEXT DATA BSS
[    0.000000]   #4 [000156f000 - 00019d5000]         RAMDISK
[    0.000000]   #5 [00019d5000 - 0001b81000]  XEN START INFO
[    0.000000]   #6 [0000002000 - 0000003000]      TRAMPOLINE
[    0.000000]   #7 [0000003000 - 0000007000]     ACPI WAKEUP
[    0.000000]   #8 [0000100000 - 0000256000]         PGTABLE
[    0.000000]   #9 [000144a000 - 000144b000]         BOOTMEM
[    0.000000]   #10 [0001b93000 - 00028db000]         BOOTMEM
[    0.000000]   #11 [0001449b80 - 0001449b84]         BOOTMEM
[    0.000000]   #12 [0001449bc0 - 0001449c80]         BOOTMEM
[    0.000000]   #13 [0001449c80 - 0001449d08]         BOOTMEM
[    0.000000]   #14 [000144b000 - 000144e000]         BOOTMEM
[    0.000000]   #15 [0001449d40 - 0001449df8]         BOOTMEM
[    0.000000]   #16 [000144e000 - 0001451000]         BOOTMEM
[    0.000000]   #17 [0001449e00 - 0001449e90]         BOOTMEM
[    0.000000]   #18 [0001449ec0 - 0001449f00]         BOOTMEM
[    0.000000]   #19 [0001449f00 - 0001449f40]         BOOTMEM
[    0.000000]   #20 [0001449f40 - 0001449f80]         BOOTMEM
[    0.000000]   #21 [0001449f80 - 0001449f9a]         BOOTMEM
[    0.000000]   #22 [0001449fc0 - 0001449fda]         BOOTMEM
[    0.000000]   #23 [0001453000 - 0001463000]         BOOTMEM
[    0.000000]   #24 [0001463000 - 0001463004]         BOOTMEM
[    0.000000]   #25 [0001463040 - 0001463044]         BOOTMEM
[    0.000000]   #26 [0001463080 - 0001463084]         BOOTMEM
[    0.000000]   #27 [00014630c0 - 00014630c4]         BOOTMEM
[    0.000000]   #28 [0001463100 - 0001463180]         BOOTMEM
[    0.000000]   #29 [0001463180 - 00014631ac]         BOOTMEM
[    0.000000]   #30 [00014631c0 - 00014671c0]         BOOTMEM
[    0.000000]   #31 [00014671c0 - 00014e71c0]         BOOTMEM
[    0.000000]   #32 [00014e71c0 - 00015271c0]         BOOTMEM
[    0.000000] Initializing HighMem for node 0 (0002d3fe:0006a400)
[    0.000000] Memory: 1713860k/1740800k available (2121k kernel code,
26552k reserved, 1275k data, 344k init, 999432k highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xf571e000 - 0xf57ff000   ( 900 kB)
[    0.000000]     pkmap   : 0xf5400000 - 0xf5600000   (2048 kB)
[    0.000000]     vmalloc : 0xedbfe000 - 0xf53fe000   ( 120 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xed3fe000   ( 723 MB)
[    0.000000]       .init : 0xc1352000 - 0xc13a8000   ( 344 kB)
[    0.000000]       .data : 0xc121266b - 0xc1351500   (1275 kB)
[    0.000000]       .text : 0xc1000000 - 0xc121266b   (2121 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:512
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] console [hvc0] enabled
[    0.000000] installing Xen timer for CPU 0
[    0.000000] Detected 2659.994 MHz processor.
[    0.004000] Calibrating delay loop (skipped), value calculated
using timer frequency.. 5319.98 BogoMIPS (lpj=10639976)
[    0.004000] Security Framework initialized
[    0.004000] SELinux:  Disabled at boot.
[    0.004000] Mount-cache hash table entries: 512
[    0.004000] Initializing cgroup subsys ns
[    0.004000] Initializing cgroup subsys cpuacct
[    0.004000] Initializing cgroup subsys devices
[    0.004000] Initializing cgroup subsys freezer
[    0.004000] CPU: Unsupported number of siblings 4
[    0.004000] Performance Events: Core2 events,
[    0.004000] no APIC, boot with the "lapic" boot parameter to
force-enable it.
[    0.004000] no hardware sampling interrupt available.
[    0.004000] Intel PMU driver.
[    0.004000] ... version:                2
[    0.004000] ... bit width:              40
[    0.004000] ... generic registers:      2
[    0.004000] ... value mask:             000000ffffffffff
[    0.004000] ... max period:             000000007fffffff
[    0.004000] ... fixed-purpose events:   3
[    0.004000] ... event mask:             0000000700000003
[    0.004000] SMP alternatives: switching to UP code
[    0.025930] Freeing SMP alternatives: 16k freed
[    0.028065] Brought up 1 CPUs
[    0.028159] devtmpfs: initialized
[    0.028342] Grant table initialized
[    0.028374] NET: Registered protocol family 16
[    0.032220] PCI: Fatal: No config space access function found
[    0.033300] bio: create slab <bio-0> at 0
[    0.033349] ACPI: Interpreter disabled.
[    0.033401] xen_balloon: Initialising balloon driver.
[    0.040267] vgaarb: loaded
[    0.040388] PCI: System does not support PCI
[    0.040394] PCI: System does not support PCI
[    0.040501] NetLabel: Initializing
[    0.040507] NetLabel:  domain hash size = 128
[    0.040511] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.040524] NetLabel:  unlabeled traffic allowed by default
[    0.040564] Switching to clocksource xen
[    0.040622] pnp: PnP ACPI: disabled
[    0.040985] NET: Registered protocol family 2
[    0.041009] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.041108] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[    0.041597] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    0.041848] TCP: Hash tables configured (established 131072 bind 65536)
[    0.041855] TCP reno registered
[    0.041859] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.041879] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.041933] NET: Registered protocol family 1
[    0.041968] Unpacking initramfs...
[    0.049691] Freeing initrd memory: 4504k freed
[    0.051109] platform rtc_cmos: registered platform RTC device (no
PNP device found)
[    0.051608] audit: initializing netlink socket (disabled)
[    0.051624] type=2000 audit(1294934590.244:1): initialized
[    0.063709] highmem bounce pool size: 64 pages
[    0.063718] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.065891] VFS: Disk quotas dquot_6.5.2
[    0.065952] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.066056] msgmni has been set to 1404
[    0.066293] alg: No test for stdrng (krng)
[    0.066386] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 254)
[    0.066395] io scheduler noop registered (default)
[    0.070394] loop: module loaded
[    0.070533] PNP: No PS/2 controller found. Probing ports directly.
[    0.071433] mice: PS/2 mouse device common for all mice
[    0.071475] cpuidle: using governor ladder
[    0.071480] cpuidle: using governor menu
[    0.071533] TCP cubic registered
[    0.071538] NET: Registered protocol family 17
[    0.071556] Using IPI No-Shortcut mode
[    0.071694] registered taskstats version 1
[    0.071708] XENBUS: Device with no driver: device/vif/0
[    0.071713] XENBUS: Device with no driver: device/vbd/2050
[    0.071718] XENBUS: Device with no driver: device/vbd/2064
[    0.071722] XENBUS: Device with no driver: device/vbd/2051
[    0.071797] Freeing unused kernel memory: 344k freed
[    0.072454] Write protecting the kernel text: 2124k
[    0.072695] Write protecting the kernel read-only data: 952k
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 mbcache.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading xen-blkfront.ko module
[    0.456365] blkfront device/vbd/2050 num-ring-pages 1 nr_ents 32.
[    0.460302] blkfront device/vbd/2064 num-ring-pages 1 nr_ents 32.
[    0.484444] blkfront device/vbd/2051 num-ring-pages 1 nr_ents 32.
[    0.487167] blkfront: regular deviceid=0x802 major,minor=8,2,
assuming parts/disk=16
[    0.488610] blkfront: regular deviceid=0x810 major,minor=8,16,
assuming parts/disk=16
[    0.488850]  xvdb: unknown partition table
[    0.559870] blkfront: regular deviceid=0x803 major,minor=8,3,
assuming parts/disk=16
Loading xen-blkfront.ko module
insmod: error inserting ''/lib/xen-blkfront.ko'': -1 File exists
Loading dm-mod.ko module
[    0.638849] device-mapper: uevent: version 1.0.3
[    0.668150] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05)
initialised: dm-devel@redhat.com
Loading dm-log.ko module
Loading dm-region-hash.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Loading dm-region-hash.ko module
insmod: error inserting ''/lib/dm-region-hash.ko'': -1 File
exists
Loading xen-blkfront.ko module
insmod: error inserting ''/lib/xen-blkfront.ko'': -1 File exists
Loading xen-netfront.ko module
[    0.815832] Initialising Xen virtual ethernet driver.
Loading xen-netfront.ko module
insmod: error inserting ''/lib/xen-netfront.ko'': -1 File exists
Scanning and configuring dmraid supported devices
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
[    1.180307] Kernel panic - not syncing: Attempted to kill init!
[    1.180321] Pid: 1, comm: init Not tainted 2.6.34.7-56.40.i686 #1
[    1.180328] Call Trace:
[    1.180339]  [<c120bb0d>] ? printk+0xf/0x12
[    1.180345]  [<c120ba8f>] panic+0x38/0xa7
[    1.180353]  [<c1036887>] do_exit+0x5d/0x631
[    1.180360]  [<c1210304>] ? do_page_fault+0x265/0x2c0
[    1.180366]  [<c1036ec5>] do_group_exit+0x6a/0x93
[    1.180372]  [<c1036f01>] sys_exit_group+0x13/0x17
[    1.180377]  [<c120d8b4>] syscall_call+0x7/0xb
[    1.180385]  [<c1200000>] ? _cpu_down+0x177/0x248
- - - < s n i p > - - -

Thank you in advance.

Regards,

GNUbie

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

Fajar A. Nugraha

2011-Jan-13 22:04 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

On Fri, Jan 14, 2011 at 12:03 AM, GNUbie <gnubie@gmail.com>
wrote:> Hello all,
>
> Please advice on how I can move forward from this bootup problem. I
> already tried changing the value of the "root=" option to
/dev/sda2
> and /dev/xvda2 with no luck. I also tried to re-generate a new initrd
> adding the options of "--with xennet --with xenblk" but still
with no
> luck.
> title GNU/Linux (2.6.34.7-56.40.i686)
>    root (hd0,0)
>    kernel /boot/vmlinuz-2.6.34.7-56.40.i686 root=LABEL=/ console=hvc0
>    initrd /boot/initrd-2.6.34.7-56.40.i686.img
I assume you ACTUALLY have the correct partition/LV with LABEL=/ on
domU''s disk image?
> Loading xen-blkfront.ko module
> [    0.456365] blkfront device/vbd/2050 num-ring-pages 1 nr_ents 32.
> [    0.460302] blkfront device/vbd/2064 num-ring-pages 1 nr_ents 32.
> [    0.484444] blkfront device/vbd/2051 num-ring-pages 1 nr_ents 32.
> [    0.487167] blkfront: regular deviceid=0x802 major,minor=8,2,
> assuming parts/disk=16
> [    0.488610] blkfront: regular deviceid=0x810 major,minor=8,16,
> assuming parts/disk=16
> [    0.488850]  xvdb: unknown partition table
> [    0.559870] blkfront: regular deviceid=0x803 major,minor=8,3,
> assuming parts/disk=16
You should see the disks and detected partition tables on boot. Your
log only xvdb is detected with "unknown partition table", which is
weird. Does the disk image actually HAVE partition on it, or do you
create a filesystem directly on that image? What does your domU config
file looks like? What does "fdisk -l /path/to/your/disk-image" look
like?

-- 
Fajar

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

GNUbie

2011-Jan-14 00:44 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Hello Fajar,

On Fri, Jan 14, 2011 at 6:04 AM, Fajar A. Nugraha <list@fajar.net>
wrote:>
> I assume you ACTUALLY have the correct partition/LV with LABEL=/ on
> domU''s disk image?
Yes. But as I''ve said, I also tried using /dev/sda2 and /dev/xvda2 but
with no luck.
>
>> Loading xen-blkfront.ko module
>> [    0.456365] blkfront device/vbd/2050 num-ring-pages 1 nr_ents 32.
>> [    0.460302] blkfront device/vbd/2064 num-ring-pages 1 nr_ents 32.
>> [    0.484444] blkfront device/vbd/2051 num-ring-pages 1 nr_ents 32.
>> [    0.487167] blkfront: regular deviceid=0x802 major,minor=8,2,
>> assuming parts/disk=16
>> [    0.488610] blkfront: regular deviceid=0x810 major,minor=8,16,
>> assuming parts/disk=16
>> [    0.488850]  xvdb: unknown partition table
>> [    0.559870] blkfront: regular deviceid=0x803 major,minor=8,3,
>> assuming parts/disk=16
>
> You should see the disks and detected partition tables on boot. Your
> log only xvdb is detected with "unknown partition table", which
is
> weird. Does the disk image actually HAVE partition on it, or do you
> create a filesystem directly on that image? What does your domU config
> file looks like? What does "fdisk -l /path/to/your/disk-image"
look
> like?
This system (domU) used to be in another dom0 that uses /dev/xvd*
partitions then I dump''ed and restore''d a copy of this system
to this
new dom0 that uses /dev/sd* partitions.

I remember that the original partitions of this domU from its original
dom0 were:

 202        1   10240001 xvda1 => /
 202        2  356485632 xvda2 => /data
 202        3     917504 xvda3 => swap

But even from the original dom0, the domU do not have a /dev/xvdb partition.

Going back to your question. I don''t remember creating the /dev/xvdb
partition and it doesn''t have an /dev/xvdb partition.

Before I restore''d the dump''ed domU to its new place, I
fdisk''ed the
volume and created two (2) partitions for the /boot and /. Please take
note that the original domU from the original dom0, I dump''ed the
/dev/xvda1 which contains the entire / partition and when I restore''d
it to the new dom0 for this new domU, I made sure that I mounted the
second partition first which is the / then mounted the first partition
inside the /boot.

Now, I''m not aware if there is any other configuration that checks and
expects this /dev/xvdb partition aside from checking the /etc/fstab
which I already changed as per my original message for this thread.

Please advice. Thank you.

Regards,

GNUbie

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

Fajar A. Nugraha

2011-Jan-14 02:17 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

On Fri, Jan 14, 2011 at 7:44 AM, GNUbie <gnubie@gmail.com>
wrote:> Hello Fajar,
>
> On Fri, Jan 14, 2011 at 6:04 AM, Fajar A. Nugraha <list@fajar.net>
wrote:
>>
>> I assume you ACTUALLY have the correct partition/LV with LABEL=/ on
>> domU''s disk image?
>
> Yes. But as I''ve said, I also tried using /dev/sda2 and /dev/xvda2
but
> with no luck.
That''s not what I asked.

The key point is you need to have correct root. If you actually create
the filesystem with "mkfs.ext3 -L /" or run "e2label ...",
then the
label should be there, and you don''t need to worry (on grub.conf
anyway) whether it''s hda2, sda2, or xvda2.

On the other hand, if you create the image from scratch, and did NOT
create the label manually, and transfer the files using
rsync/tar/whatever, you will not have the label.
>
>>
>>> Loading xen-blkfront.ko module
>>> [    0.456365] blkfront device/vbd/2050 num-ring-pages 1 nr_ents
32.
>>> [    0.460302] blkfront device/vbd/2064 num-ring-pages 1 nr_ents
32.
>>> [    0.484444] blkfront device/vbd/2051 num-ring-pages 1 nr_ents
32.
>>> [    0.487167] blkfront: regular deviceid=0x802 major,minor=8,2,
>>> assuming parts/disk=16
>>> [    0.488610] blkfront: regular deviceid=0x810 major,minor=8,16,
>>> assuming parts/disk=16
>>> [    0.488850]  xvdb: unknown partition table
>>> [    0.559870] blkfront: regular deviceid=0x803 major,minor=8,3,
>>> assuming parts/disk=16
>>
>> You should see the disks and detected partition tables on boot. Your
>> log only xvdb is detected with "unknown partition table",
which is
>> weird. Does the disk image actually HAVE partition on it, or do you
>> create a filesystem directly on that image? What does your domU config
>> file looks like? What does "fdisk -l
/path/to/your/disk-image" look
>> like?
>
> This system (domU) used to be in another dom0 that uses /dev/xvd*
> partitions then I dump''ed and restore''d a copy of this
system to this
> new dom0 that uses /dev/sd* partitions.
again, I didn''t ask that, and it''s not relevant really.
I asked
>> What does your domU config
>> file looks like?
... to know how you map the disk from your config file. For example,
in my system:

disk =  [
        ''tap:aio:/z/rhel6/xvda.img,xvda,w'',
        ]

means I map the disk as xvda. Your log is weird, in that it shows 3
block devices detected, but only "xvdb" shown. The config file might
provide some information as to why it happens.

I also asked
>> What does "fdisk -l /path/to/your/disk-image" look like
... cause it might be that you simply don''t have a parition at all. Or
your root is on LVM, not a partition. Mine shows something like this

# fdisk -l /z/rhel6/xvda.img
last_lba(): I don''t know how to handle files with mode 81a4
You must set cylinders.
You can do this from the extra functions menu.

Disk /z/rhel6/xvda.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

            Device Boot      Start         End      Blocks   Id  System
/z/rhel6/xvda.img1   *           1          64      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/z/rhel6/xvda.img2              64        1306     9972736   8e  Linux LVM
Partition 2 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(1305, 106, 17)

... which shows I use LVM, and "/" is located in LVM (cause first
partition is too small to be "/")
>
> I remember that the original partitions of this domU from its original
> dom0 were:
>
>  202        1   10240001 xvda1 => /
>  202        2  356485632 xvda2 => /data
>  202        3     917504 xvda3 => swap
>
> But even from the original dom0, the domU do not have a /dev/xvdb
partition.
I didn''t ask how it was on the original dom0. I asked what your
current image has right now.

If you simply copy the image then the partition might be the same, but
in that case you''ve made an obvious mistake: your "/" was on
xvda1.
Passing "root=/dev/sda2" is simply silly.

It''s useless to go into details right now without knowing what your
current image looks like.
>
> Going back to your question. I don''t remember creating the
/dev/xvdb
> partition and it doesn''t have an /dev/xvdb partition.
I didn''t ask whether you create it or not.
I asked what your domU config looks like, and what fdisk output on
your current image looks like.

If you don''t answer it then there''s nothing I can do to help.

-- 
Fajar

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

GNUbie

2011-Jan-14 02:59 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Hello Fajar,

On Fri, Jan 14, 2011 at 10:17 AM, Fajar A. Nugraha <list@fajar.net>
wrote:>
> That''s not what I asked.
>
> The key point is you need to have correct root. If you actually create
> the filesystem with "mkfs.ext3 -L /" or run "e2label
...", then the
> label should be there, and you don''t need to worry (on grub.conf
> anyway) whether it''s hda2, sda2, or xvda2.
When I format the new volume for this new domU, I added that -L /
option for the sda2 and /boot for the sda1.
> On the other hand, if you create the image from scratch, and did NOT
> create the label manually, and transfer the files using
> rsync/tar/whatever, you will not have the label.
Then, I transferred the files using the dump and restore utilities to
a mounted directory (e.g. /mnt) where:

/mnt => /dev/sda2
/mnt/boot => /dev/sda1
> again, I didn''t ask that, and it''s not relevant really.
> I asked
>
>>> What does your domU config
>>> file looks like?
Honestly, I don''t know because I don''t manage the dom0. But
based on
the documentation, it expects sd* mapping.
> I also asked
>
>>> What does "fdisk -l /path/to/your/disk-image" look like
Right now, the volume is in my other domU''s /dev/sdk:

# fdisk -l /dev/sdk

Disk /dev/sdk: 2147 MB, 2147483648 bytes
255 heads, 63 sectors/track, 261 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x9f08f669

   Device Boot      Start         End      Blocks   Id  System
/dev/sdk1               1          17      136521   83  Linux
/dev/sdk2              18         261     1959930   83  Linux

> I didn''t ask how it was on the original dom0. I asked what your
> current image has right now.
>
> If you simply copy the image then the partition might be the same, but
> in that case you''ve made an obvious mistake: your "/"
was on xvda1.
> Passing "root=/dev/sda2" is simply silly.
>
> It''s useless to go into details right now without knowing what
your
> current image looks like.
Based on the above output for the fdisk command, sdk1 contains the
files and directories for the /boot partition while the sdk2 contains
the rest of the files and directories of the entire / partition. With
this, my /etc/fstab for the new domU has been configured like this:

LABEL=/boot /boot       ext3    defaults            1   2
LABEL=/     /           ext3    defaults            1   1
tmpfs       /dev/shm    tmpfs   defaults            0   0
devpts      /dev/pts    devpts  gid=5,mode=620      0   0
sysfs       /sys        sysfs   defaults            0   0
proc        /proc       proc    defaults            0   0
none        /proc/xen   xenfs   defaults            0   0

And I also tried changing the first 2 lines with:

/dev/sda1   /boot       ext3    defaults            1   2
/dev/sda2   /           ext3    defaults            1   1

Anyway, I just did a grep to this new domU and below were the output:

- - - < s n i p > - - -
# pwd
/

# grep -i xvd */*
Binary file boot/initrd-2.6.34.7-56.40.i686.img matches
Binary file boot/vmlinuz-2.6.34.7-56.40.i686 matches
etc/fstab:#/dev/xvda1  /boot       ext3    defaults            1   2
etc/fstab:#/dev/xvda2  /           ext3    defaults            1   1
Binary file lib/liblvm2app.so.2.2 matches
Binary file lib/liblvm2cmd.so.2.02 matches
sbin/ec2udev:  if echo "$1"|grep -qE
''xvd[a-z][0-9]?'' ; then
sbin/ec2udev:    echo "$1" | sed -e ''s/xvd/sd/''
Binary file sbin/lvchange matches
Binary file sbin/lvconvert matches
Binary file sbin/lvcreate matches
Binary file sbin/lvdisplay matches
Binary file sbin/lvextend matches
Binary file sbin/lvm matches
Binary file sbin/lvmchange matches
Binary file sbin/lvmdiskscan matches
Binary file sbin/lvmsadc matches
Binary file sbin/lvmsar matches
Binary file sbin/lvm.static matches
Binary file sbin/lvreduce matches
Binary file sbin/lvremove matches
Binary file sbin/lvrename matches
Binary file sbin/lvresize matches
Binary file sbin/lvs matches
Binary file sbin/lvscan matches
sbin/mkinitrd:                            [[ ${dep} =~ ^/dev/xvd.+ ]]
&& continue
sbin/mkinitrd:                        [[ ${dep} =~ ^/dev/xvd.+ ]] &&
continue
sbin/mkinitrd:                    [[ ${dep} =~ ^/dev/xvd.+ ]] &&
continue
Binary file sbin/pvchange matches
Binary file sbin/pvck matches
Binary file sbin/pvcreate matches
Binary file sbin/pvdisplay matches
Binary file sbin/pvmove matches
Binary file sbin/pvremove matches
Binary file sbin/pvresize matches
Binary file sbin/pvs matches
Binary file sbin/pvscan matches
Binary file sbin/vgcfgbackup matches
Binary file sbin/vgcfgrestore matches
Binary file sbin/vgchange matches
Binary file sbin/vgck matches
Binary file sbin/vgconvert matches
Binary file sbin/vgcreate matches
Binary file sbin/vgdisplay matches
Binary file sbin/vgexport matches
Binary file sbin/vgextend matches
Binary file sbin/vgimport matches
Binary file sbin/vgmerge matches
Binary file sbin/vgmknodes matches
Binary file sbin/vgreduce matches
Binary file sbin/vgremove matches
Binary file sbin/vgrename matches
Binary file sbin/vgs matches
Binary file sbin/vgscan matches
Binary file sbin/vgsplit matches

# grep -i xvd */*/*
Binary file boot/boot/initrd-2.6.34.7-56.40.i686.img matches
Binary file boot/boot/vmlinuz-2.6.34.7-56.40.i686 matches
grep: dev/mapper/control: Invalid argument
grep: etc/alternatives/mta: No such file or directory
grep: etc/alternatives/mta-mailq: No such file or directory
grep: etc/alternatives/mta-mailqman: No such file or directory
grep: etc/alternatives/mta-newaliases: No such file or directory
grep: etc/alternatives/mta-pam: No such file or directory
grep: etc/alternatives/mta-rmail: No such file or directory
grep: etc/alternatives/mta-rsmtp: No such file or directory
grep: etc/alternatives/mta-runq: No such file or directory
grep: etc/alternatives/mta-sendmail: No such file or directory
etc/blkid/blkid.tab:<device DEVNO="0xca01"
TIME="1287132238.551661"
UUID="66c6f5a3-b64e-4bdf-bb32-9c7cf6a6c431"
TYPE="ext3">/dev/xvda1</device>
etc/blkid/blkid.tab:<device DEVNO="0xca02"
TIME="1287132238.570084"
LABEL="swap" UUID="97ea8a42-fea2-4015-979c-15ff965990ac"
TYPE="swap">/dev/xvda2</device>
etc/blkid/blkid.tab.old:<device DEVNO="0xca01"
TIME="1287025097.904622"
UUID="66c6f5a3-b64e-4bdf-bb32-9c7cf6a6c431"
TYPE="ext3">/dev/xvda1</device>
etc/blkid/blkid.tab.old:<device DEVNO="0xca02"
TIME="1286881135.564786" LABEL="swap2"
UUID="4aa34098-17b2-4033-8e73-e88fdfec157b"
TYPE="swap">/dev/xvda2</device>
etc/makedev.d/02linux-2.6.x:b $STORAGE             202   0  1 256 xvd%c%|%d a 16
grep: etc/pam.d/smtp: No such file or directory
etc/sysconfig/sysstat.ioconf:202:xvd:*:0:a:16:*:16:Xen Virtual Disk
etc/sysconfig/sysstat.ioconf-orig:202:xvd:*:0:a:16:p:16:Xen Virtual Block Device
grep: usr/bin/mailq: No such file or directory
grep: usr/bin/newaliases: No such file or directory
Binary file usr/bin/php matches
Binary file usr/bin/php-cgi matches
grep: usr/bin/pydoc: No such file or directory
grep: usr/bin/pydoc2: No such file or directory
grep: usr/bin/rmail: No such file or directory
grep: usr/bin/rsmtp: No such file or directory
grep: usr/bin/runq: No such file or directory
Binary file usr/lib/libbdevid.so.5.1.19.6 matches
var/mail/root: /dev/xvda1            9.7G  963M  8.2G  11% /
var/mail/root: /dev/xvda1            9.7G  963M  8.2G  11% /
var/mail/root: /dev/xvda1            9.7G  995M  8.2G  11% /
- - - < s n i p > - - -

Thank you once again.

Regards,

GNUbie

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

Fajar A. Nugraha

2011-Jan-14 04:03 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

On Fri, Jan 14, 2011 at 9:59 AM, GNUbie <gnubie@gmail.com>
wrote:> When I format the new volume for this new domU, I added that -L /
> option for the sda2 and /boot for the sda1.
Good
> Then, I transferred the files using the dump and restore utilities to
> a mounted directory (e.g. /mnt) where:
>
> /mnt => /dev/sda2
> /mnt/boot => /dev/sda1
How do you know it''s actually mapped as sda?
>>>> What does your domU config
>>>> file looks like?
>
> Honestly, I don''t know because I don''t manage the dom0.
But based on
> the documentation, it expects sd* mapping.
You need to get it. Even if it''s only to get disk mappings (whatever
format it''s in, whether python or xml)
It''s possible that the domU config maps the disk as xvdb (for
example). Then all attempts to use xvda2 or sda2 will be useless.
>>>> What does "fdisk -l /path/to/your/disk-image" look
like
>
> Right now, the volume is in my other domU''s /dev/sdk:
>
> # fdisk -l /dev/sdk
>
> Disk /dev/sdk: 2147 MB, 2147483648 bytes
> 255 heads, 63 sectors/track, 261 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x9f08f669
>
>   Device Boot      Start         End      Blocks   Id  System
> /dev/sdk1               1          17      136521   83  Linux
> /dev/sdk2              18         261     1959930   83  Linux
>
Good,
Try checking to see if the label actually exists. Run
e2label /dev/sdk1
e2label /dev/sdk2

I had cases where I run e2label to setup the label, but it doesn''t
show up after reboot. Just to make sure.
> my /etc/fstab for the new domU has been configured like this:
>
> LABEL=/boot /boot       ext3    defaults            1   2
> LABEL=/     /           ext3    defaults            1   1
> And I also tried changing the first 2 lines with:
>
> /dev/sda1   /boot       ext3    defaults            1   2
> /dev/sda2   /           ext3    defaults            1   1
At this point you NEED to know what the domU detects the disk as. domU
config file might help.
Also, disable "quiet" on grub config line (if it''s there).
During boot
of Ubuntu Lucid in my setup, it shows these lines:


[    0.205765] XENBUS: Device with no driver: device/vbd/51712
[    0.205782] XENBUS: Device with no driver: device/vif/0
[    0.205797] XENBUS: Device with no driver: device/console/0
[    0.205844]   Magic number: 1:252:3141
[    0.205918] /build/buildd/linux-2.6.32/drivers/rtc/hctosys.c:
unable to open rtc device (rtc0)
[    0.205942] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    0.205957] EDD information not available.
[    0.206219] Freeing unused kernel memory: 800k freed
[    0.206757] Write protecting the kernel read-only data: 7800k
Loading, please wait...
[    0.328049] udev: starting version 151
Begin: Loading essential drivers... ...
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
[    0.774316] blkfront: xvda: barriers enabled
[    0.775478]  xvda: xvda1 xvda2 xvda3


In particular, you need to look at these lines
[    0.205765] XENBUS: Device with no driver: device/vbd/51712 =>
"51712" is block device id for xvda

[    0.774316] blkfront: xvda: barriers enabled
[    0.775478]  xvda: xvda1 xvda2 xvda3 => this shows that
xen_blkfront driver handles the block device xvda, and it correctly
detects three partitions.

Your problem might be something as simple as not having xen block
device frontend installed, either built in or as a module.

-- 
Fajar

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

GNUbie

2011-Jan-14 05:09 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Hello Fajar,

On Fri, Jan 14, 2011 at 12:03 PM, Fajar A. Nugraha <list@fajar.net>
wrote:>
> How do you know it''s actually mapped as sda?
Only in my /etc/fstab for that domU.
> You need to get it. Even if it''s only to get disk mappings
(whatever
> format it''s in, whether python or xml)
> It''s possible that the domU config maps the disk as xvdb (for
> example). Then all attempts to use xvda2 or sda2 will be useless.
I''m afraid how to answer this question. Actually, I am trying to boot
my domU at the AWS EC2 environment which is now an EBS volume. The
domU came from an S3 and I made a copy to the EBS volume. I apologize
in advance if I am in the wrong mailing list.
> Good,
> Try checking to see if the label actually exists. Run
> e2label /dev/sdk1
> e2label /dev/sdk2
# e2label /dev/sdk1
/boot

# e2label /dev/sdk2
/
> At this point you NEED to know what the domU detects the disk as. domU
> config file might help.
:-(
> Also, disable "quiet" on grub config line (if it''s
there). During boot
> of Ubuntu Lucid in my setup, it shows these lines:
I don''t have it on my GRUB config.
> In particular, you need to look at these lines
> [    0.205765] XENBUS: Device with no driver: device/vbd/51712 =>
> "51712" is block device id for xvda
>
> [    0.774316] blkfront: xvda: barriers enabled
> [    0.775478]  xvda: xvda1 xvda2 xvda3 => this shows that
> xen_blkfront driver handles the block device xvda, and it correctly
> detects three partitions.
>
> Your problem might be something as simple as not having xen block
> device frontend installed, either built in or as a module.
I''m wondering why it keeps on expecting the xvd* mapping except that
if the domU config is really expecting for it.

Do I need to rebuild the kernel and initrd?

Below is the kernel config file that comes with the kernel that I''m
using for this domU:

# grep -i xen config-2.6.34.7-56.40.i686
CONFIG_XEN=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=80
CONFIG_XEN_SAVE_RESTORE=y
CONFIG_XEN_DEBUG_FS=y
CONFIG_XEN_BLKDEV_FRONTEND=m
# CONFIG_NETXEN_NIC is not set
CONFIG_XEN_NETDEV_FRONTEND=m
CONFIG_HVC_XEN=y
# Xen driver support
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SCRUB_PAGES=y
CONFIG_XEN_DEV_EVTCHN=m
CONFIG_XENFS=m
CONFIG_XEN_COMPAT_XENFS=y
CONFIG_XEN_SYS_HYPERVISOR=y

# cat /etc/modprobe.conf
alias eth0 xennet
alias scsi_hostadapter xenblk
alias ipv6 off
alias net-pf-10 off
options ipv6 disable=1

Thank you in advance.

Regards,

GNUbie

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

Fajar A. Nugraha

2011-Jan-14 07:47 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

On Fri, Jan 14, 2011 at 12:09 PM, GNUbie <gnubie@gmail.com>
wrote:> I''m wondering why it keeps on expecting the xvd* mapping except
that
> if the domU config is really expecting for it.
Let me make this reaaaaaaly simple. You were able to captrure boot
log. That''s good.
Your previous boot log shows these

[    0.071713] XENBUS: Device with no driver: device/vbd/2050
[    0.071718] XENBUS: Device with no driver: device/vbd/2064
[    0.071722] XENBUS: Device with no driver: device/vbd/2051

whish should roughly mean you have three block devices on that domU.
Do you know what they are? If not, you need to find out (whether from
domU config file, some kind of Amazon EC2 config page, ask Amazon
support, whatever).

You got the following block IDs (you can derive these from 256*major
number + minor number):
sda -> 2048
sda2 -> 2050
sda3 -> 2051
sdb -> 2064

so you do NOT have anything mapped as sda or xvda.
You NEED to know how you currently have it mapped.
You NEED to know what those three block devices that you currently have are.
You NEED to map your current boot device to sda/xvda/hda/whatever
(since you have partitions on it)

Loading xen-blkfront.ko module
[    0.456365] blkfront device/vbd/2050 num-ring-pages 1 nr_ents 32.
[    0.460302] blkfront device/vbd/2064 num-ring-pages 1 nr_ents 32.
[    0.484444] blkfront device/vbd/2051 num-ring-pages 1 nr_ents 32.
[    0.487167] blkfront: regular deviceid=0x802 major,minor=8,2,
assuming parts/disk=16
[    0.488610] blkfront: regular deviceid=0x810 major,minor=8,16,
assuming parts/disk=16
[    0.488850]  xvdb: unknown partition table
[    0.559870] blkfront: regular deviceid=0x803 major,minor=8,3,
assuming parts/disk=16

Those lines show you have xen-blkfront, which is good.
Your kernel uses xvd names instead of sd, which doesn''t really matter
as long as you know what it uses.
But you do NOT see partition mapping on the disks, which is bad. You
should see something like this (from my Ubuntu boot log)

[    0.774316] blkfront: xvda: barriers enabled
[    0.775478]  xvda: xvda1 xvda2 xvda3

or something like this (from my RHEL5 boot log)

Loading xenblk.ko module
Registering block device major 3
 hda: hda1
 hdb: hdb1

Perhaps you forgot to build partition support (CONFIG_MSDOS_PARTITION=y)?

In any case:
- find out EXACTLY what your config is like
- map disks the way you want it (e.g map first disk as xvda, NOT
xvda1). Ask Amazon support if you don''t know how.
- make sure the necessary kernel support is builtin (partition
support, xen frontend block driver, etc.). If you don''t know about
these things simply start with your distro''s default kernel.

-- 
Fajar

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

GNUbie

2011-Jan-14 08:44 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Hello Fajar,

On Fri, Jan 14, 2011 at 3:47 PM, Fajar A. Nugraha <list@fajar.net>
wrote:>
> Let me make this reaaaaaaly simple. You were able to captrure boot
> log. That''s good.
> Your previous boot log shows these
>
> [    0.071713] XENBUS: Device with no driver: device/vbd/2050
> [    0.071718] XENBUS: Device with no driver: device/vbd/2064
> [    0.071722] XENBUS: Device with no driver: device/vbd/2051
>
> whish should roughly mean you have three block devices on that domU.
> Do you know what they are? If not, you need to find out (whether from
> domU config file, some kind of Amazon EC2 config page, ask Amazon
> support, whatever).
Maybe that 3 block devices were from its original domU where
previously (from where this domU came from), it comes with the
following partitions:

/dev/xvda1 => /
/dev/xvda2 => /media/ephemeral0
/dev/xvda3 => SWAP
> You got the following block IDs (you can derive these from 256*major
> number + minor number):
> sda -> 2048
> sda2 -> 2050
> sda3 -> 2051
> sdb -> 2064
>
> so you do NOT have anything mapped as sda or xvda.
> You NEED to know how you currently have it mapped.
> You NEED to know what those three block devices that you currently have
are.
> You NEED to map your current boot device to sda/xvda/hda/whatever
> (since you have partitions on it)
When you say "boot device", are you referring to the whole / or just
the /boot? As I mentioned on my previous message that the /dev/xvda1
or /dev/xvda contains the entire / filesystem including the /boot.

Below is the output of the "fdisk -l" command from a working (old)
domU:

# fdisk -l

Disk /dev/xvda1: 10.5 GB, 10485761024 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/xvda1 doesn''t contain a valid partition table

Disk /dev/xvda2: 160.1 GB, 160104972288 bytes
255 heads, 63 sectors/track, 19464 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/xvda2 doesn''t contain a valid partition table

Disk /dev/xvda3: 939 MB, 939524096 bytes
255 heads, 63 sectors/track, 114 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/xvda3 doesn''t contain a valid partition table
> Perhaps you forgot to build partition support (CONFIG_MSDOS_PARTITION=y)?
# grep -i dos config-2.6.34.7-56.40.i686
# DOS/FAT/NT Filesystems
CONFIG_MSDOS_FS=m
CONFIG_MSDOS_PARTITION=y
> In any case:
> - find out EXACTLY what your config is like
> - map disks the way you want it (e.g map first disk as xvda, NOT
> xvda1). Ask Amazon support if you don''t know how.
> - make sure the necessary kernel support is builtin (partition
> support, xen frontend block driver, etc.). If you don''t know about
> these things simply start with your distro''s default kernel.
I''m using the Amazon Linux AMI 32bit distro which is based on
RedHat/CentOS and I am using the stock kernel of the said
distribution.

By the way, below is the init script inside my initrd image:

- - - < s n i p > - - -
#!/bin/nash

mount -t proc /proc /proc
setquiet
echo Mounting proc filesystem
echo Mounting sysfs filesystem
mount -t sysfs /sys /sys
echo Creating /dev
mount -o mode=0755 -t tmpfs /dev /dev
mkdir /dev/pts
mount -t devpts -o gid=5,mode=620 /dev/pts /dev/pts
mkdir /dev/shm
mkdir /dev/mapper
echo Creating initial device nodes
mknod /dev/null c 1 3
mknod /dev/zero c 1 5
mknod /dev/urandom c 1 9
mknod /dev/systty c 4 0
mknod /dev/tty c 5 0
mknod /dev/console c 5 1
mknod /dev/ptmx c 5 2
mknod /dev/rtc c 10 135
mknod /dev/tty0 c 4 0
mknod /dev/tty1 c 4 1
mknod /dev/tty2 c 4 2
mknod /dev/tty3 c 4 3
mknod /dev/tty4 c 4 4
mknod /dev/tty5 c 4 5
mknod /dev/tty6 c 4 6
mknod /dev/tty7 c 4 7
mknod /dev/tty8 c 4 8
mknod /dev/tty9 c 4 9
mknod /dev/tty10 c 4 10
mknod /dev/tty11 c 4 11
mknod /dev/tty12 c 4 12
mknod /dev/ttyS0 c 4 64
mknod /dev/ttyS1 c 4 65
mknod /dev/ttyS2 c 4 66
mknod /dev/ttyS3 c 4 67
echo Setting up hotplug.
hotplug
echo Creating block device nodes.
mkblkdevs
echo "Loading mbcache.ko module"
insmod /lib/mbcache.ko
echo "Loading jbd.ko module"
insmod /lib/jbd.ko
echo "Loading ext3.ko module"
insmod /lib/ext3.ko
echo "Loading xen-blkfront.ko module"
insmod /lib/xen-blkfront.ko
echo "Loading xen-blkfront.ko module"
insmod /lib/xen-blkfront.ko
echo "Loading dm-mod.ko module"
insmod /lib/dm-mod.ko
echo "Loading dm-log.ko module"
insmod /lib/dm-log.ko
echo "Loading dm-region-hash.ko module"
insmod /lib/dm-region-hash.ko
echo "Loading dm-mirror.ko module"
insmod /lib/dm-mirror.ko
echo "Loading dm-zero.ko module"
insmod /lib/dm-zero.ko
echo "Loading dm-snapshot.ko module"
insmod /lib/dm-snapshot.ko
echo "Loading dm-region-hash.ko module"
insmod /lib/dm-region-hash.ko
echo "Loading xen-blkfront.ko module"
insmod /lib/xen-blkfront.ko
echo "Loading xen-netfront.ko module"
insmod /lib/xen-netfront.ko
echo "Loading xen-netfront.ko module"
insmod /lib/xen-netfront.ko
mkblkdevs
echo Scanning and configuring dmraid supported devices
resume /dev/xvda3
echo Creating root device.
mkrootdev -t ext3 -o defaults,noatime,ro /dev/xvda1
echo Mounting root filesystem.
mount /sysroot
echo Setting up other filesystems.
setuproot
echo Switching to new root and running init.
switchroot
- - - < s n i p > - - -

Below is the list of the modules inside the initrd''s lib directory:

# ls -l lib/
total 388
-rw------- 1 root root  11140 Jan 14 16:32 dm-log.ko
-rw------- 1 root root  16948 Jan 14 16:32 dm-mirror.ko
-rw------- 1 root root  69876 Jan 14 16:32 dm-mod.ko
-rw------- 1 root root  11280 Jan 14 16:32 dm-region-hash.ko
-rw------- 1 root root  35332 Jan 14 16:32 dm-snapshot.ko
-rw------- 1 root root   2796 Jan 14 16:32 dm-zero.ko
-rw------- 1 root root 129192 Jan 14 16:32 ext3.ko
drwx------ 2 root root   1024 Jan 14 16:32 firmware
-rw------- 1 root root  60528 Jan 14 16:32 jbd.ko
-rw------- 1 root root   8676 Jan 14 16:32 mbcache.ko
-rw------- 1 root root  16696 Jan 14 16:32 xen-blkfront.ko
-rw------- 1 root root  20348 Jan 14 16:32 xen-netfront.ko

Does it mean that I have to rebuild the initrd and change/correct all
the xvd* existence to sd*?

Thank you.

Regards,

GNUbie

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

Fajar A. Nugraha

2011-Jan-14 08:51 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

On Fri, Jan 14, 2011 at 3:44 PM, GNUbie <gnubie@gmail.com>
wrote:> Hello Fajar,
>
> On Fri, Jan 14, 2011 at 3:47 PM, Fajar A. Nugraha <list@fajar.net>
wrote:
>>
>> Let me make this reaaaaaaly simple. You were able to captrure boot
>> log. That''s good.
>> Your previous boot log shows these
>>
>> [    0.071713] XENBUS: Device with no driver: device/vbd/2050
>> [    0.071718] XENBUS: Device with no driver: device/vbd/2064
>> [    0.071722] XENBUS: Device with no driver: device/vbd/2051
>>
>> whish should roughly mean you have three block devices on that domU.
>> Do you know what they are? If not, you need to find out (whether from
>> domU config file, some kind of Amazon EC2 config page, ask Amazon
>> support, whatever).
>
> Maybe that 3 block devices were from its original domU where
> previously (from where this domU came from), it comes with the
> following partitions:
>
> /dev/xvda1 => /
> /dev/xvda2 => /media/ephemeral0
> /dev/xvda3 => SWAP
There''s no xvda1 detected on your boot log.

Find out what your actual disk mappings are (again, whether from domU
config file, some kind of Amazon EC2 config page, ask Amazon support,
whatever). Don''t bother doing anything else unless you ABSOLUTELY know
what your disk mappings are.
> When you say "boot device", are you referring to the whole / or
just
> the /boot? As I mentioned on my previous message that the /dev/xvda1
> or /dev/xvda contains the entire / filesystem including the /boot.
Since the fdisk output you show earlier show / and /boot on the same
disk, then simply assign that disk as xvda. Start from there. Don''t
bother doing anything else unless you''ve succesfully done that (and
the boot log actually shows xvda is detected with the correct
partition).

-- 
Fajar

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

GNUbie

2011-Jan-14 11:10 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Hello Fajar,

On Fri, Jan 14, 2011 at 4:51 PM, Fajar A. Nugraha <list@fajar.net>
wrote:>
> There''s no xvda1 detected on your boot log.
>
> Find out what your actual disk mappings are (again, whether from domU
> config file, some kind of Amazon EC2 config page, ask Amazon support,
> whatever). Don''t bother doing anything else unless you ABSOLUTELY
know
> what your disk mappings are.
OK.
> Since the fdisk output you show earlier show / and /boot on the same
> disk, then simply assign that disk as xvda. Start from there.
Don''t
> bother doing anything else unless you''ve succesfully done that
(and
> the boot log actually shows xvda is detected with the correct
> partition).
OK.

Just a side note, I created a new domU from scratch using their stock
image just to compare on what they have in a default settings. Below
are the logs.

- - - < s n i p > - - -
    Xen Minimal OS!
  start_info: 0xb1a000(VA)
    nr_pages: 0x6cc00
  shared_inf: 0x00bae000(MA)
     pt_base: 0xb1d000(VA)
nr_pt_frames: 0x9
    mfn_list: 0x967000(VA)
   mod_start: 0x0(VA)
     mod_len: 0
       flags: 0x0
    cmd_line:  root=/dev/sda1 ro 4
  stack:      0x946780-0x966780
MM: Init
      _text: 0x0(VA)
     _etext: 0x621f5(VA)
   _erodata: 0x76000(VA)
     _edata: 0x7b6d4(VA)
stack start: 0x946780(VA)
       _end: 0x966d34(VA)
  start_pfn: b29
    max_pfn: 6cc00
Mapping memory range 0xc00000 - 0x6cc00000
setting 0x0-0x76000 readonly
skipped 0x1000
MM: Initialise page allocator for e8a000(e8a000)-0(6cc00000)
MM: done
Demand map pfns at 6cc01000-7cc01000.
Heap resides at 7cc02000-bcc02000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x6cc01000.
Initialising scheduler
Thread "Idle": pointer: 0x7cc02008, stack: 0x6c850000
Initialising xenbus
Thread "xenstore": pointer: 0x7cc02478, stack: 0x6c860000
Dummy main: start_info=0x966880
Thread "main": pointer: 0x7cc028e8, stack: 0x6c870000
"main" "root=/dev/sda1" "ro" "4"
vbd 2049 is hd0
******************* BLKFRONT for device/vbd/2049 **********


backend at /local/domain/0/backend/vbd/35/2049
Failed to read /local/domain/0/backend/vbd/35/2049/feature-barrier.
Failed to read /local/domain/0/backend/vbd/35/2049/feature-flush-cache.
16777216 sectors of 0 bytes
**************************
vbd 2051 is hd1
******************* BLKFRONT for device/vbd/2051 **********


backend at /local/domain/0/backend/vbd/35/2051
Failed to read /local/domain/0/backend/vbd/35/2051/feature-barrier.
Failed to read /local/domain/0/backend/vbd/35/2051/feature-flush-cache.
1835008 sectors of 0 bytes
**************************
vbd 2064 is hd2
******************* BLKFRONT for device/vbd/2064 **********


backend at /local/domain/0/backend/vbd/35/2064
Failed to read /local/domain/0/backend/vbd/35/2064/feature-barrier.
Failed to read /local/domain/0/backend/vbd/35/2064/feature-flush-cache.
712971264 sectors of 0 bytes
**************************

Press `ESC'' to enter the menu... 2
Press `ESC'' to enter the menu... 1
Press `ESC'' to enter the menu... 0
    [H
    [J  Booting ''Amazon Linux AMI''



root (hd0)

 Filesystem type is ext2fs, using whole disk

kernel /boot/vmlinuz-2.6.34.7-56.40.amzn1.i686 root=LABEL=/ console=hvc0

initrd /boot/initrd-2.6.34.7-56.40.amzn1.i686.img



close blk: backend at /local/domain/0/backend/vbd/35/2049
close blk: backend at /local/domain/0/backend/vbd/35/2051
close blk: backend at /local/domain/0/backend/vbd/35/2064
[    0.000000] Reserving virtual address space above 0xf5800000
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.34.7-56.40.amzn1.i686
(mockbuild@build-31003.build) (gcc version 4.4.4 20100525 (Red Hat
4.4.4-5) (GCC) ) #1 SMP Fri Oct 22 18:48:33 UTC 2010
[    0.000000] ACPI in unprivileged domain disabled
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
[    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 000000006cc00000 (usable)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] last_pfn = 0x6cc00 max_arch_pfn = 0x1000000
[    0.000000] init_memory_mapping: 0000000000000000-000000002d3fe000
[    0.000000] RAMDISK: 0156f000 - 019d0000
[    0.000000] 1016MB HIGHMEM available.
[    0.000000] 723MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 2d3fe000
[    0.000000]   low ram: 0 - 2d3fe000
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000001 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x0002d3fe
[    0.000000]   HighMem  0x0002d3fe -> 0x0006cc00
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000001 -> 0x000000a0
[    0.000000]     0: 0x00000100 -> 0x0006cc00
[    0.000000] Using APIC driver default
[    0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[    0.000000] Local APIC disabled by BIOS -- you can enable it with
"lapic"
[    0.000000] APIC: disable apic facility
[    0.000000] APIC: switched to apic NOOP
[    0.000000] Allocating PCI resources starting at 6cc00000 (gap:
6cc00000:93400000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 3.0.3-rc5-8.el5
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2
nr_node_ids:1
[    0.000000] PERCPU: Embedded 16 pages/cpu @c1453000 s41172 r0 d24364 u65536
[    0.000000] pcpu-alloc: s41172 r0 d24364 u65536 alloc=16*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 441862
[    0.000000] Kernel command line: root=LABEL=/ console=hvc0
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] Subtract (33 early reservations)
[    0.000000]   #1 [0001b86000 - 0001b98000]  XEN PAGETABLES
[    0.000000]   #2 [0000001000 - 0000002000]   EX TRAMPOLINE
[    0.000000]   #3 [0001000000 - 0001449b5c]   TEXT DATA BSS
[    0.000000]   #4 [000156f000 - 00019d0000]         RAMDISK
[    0.000000]   #5 [00019d0000 - 0001b86000]  XEN START INFO
[    0.000000]   #6 [0000002000 - 0000003000]      TRAMPOLINE
[    0.000000]   #7 [0000003000 - 0000007000]     ACPI WAKEUP
[    0.000000]   #8 [0000100000 - 0000256000]         PGTABLE
[    0.000000]   #9 [000144a000 - 000144b000]         BOOTMEM
[    0.000000]   #10 [0001b98000 - 0002930000]         BOOTMEM
[    0.000000]   #11 [0001449b80 - 0001449b84]         BOOTMEM
[    0.000000]   #12 [0001449bc0 - 0001449c80]         BOOTMEM
[    0.000000]   #13 [0001449c80 - 0001449d08]         BOOTMEM
[    0.000000]   #14 [000144b000 - 000144e000]         BOOTMEM
[    0.000000]   #15 [0001449d40 - 0001449e00]         BOOTMEM
[    0.000000]   #16 [000144e000 - 0001451000]         BOOTMEM
[    0.000000]   #17 [0001449e00 - 0001449e90]         BOOTMEM
[    0.000000]   #18 [0001449ec0 - 0001449f00]         BOOTMEM
[    0.000000]   #19 [0001449f00 - 0001449f40]         BOOTMEM
[    0.000000]   #20 [0001449f40 - 0001449f80]         BOOTMEM
[    0.000000]   #21 [0001449f80 - 0001449f9a]         BOOTMEM
[    0.000000]   #22 [0001449fc0 - 0001449fda]         BOOTMEM
[    0.000000]   #23 [0001453000 - 0001473000]         BOOTMEM
[    0.000000]   #24 [0001473000 - 0001473004]         BOOTMEM
[    0.000000]   #25 [0001473040 - 0001473044]         BOOTMEM
[    0.000000]   #26 [0001473080 - 0001473088]         BOOTMEM
[    0.000000]   #27 [00014730c0 - 00014730c8]         BOOTMEM
[    0.000000]   #28 [0001473100 - 0001473180]         BOOTMEM
[    0.000000]   #29 [0001473180 - 00014731ac]         BOOTMEM
[    0.000000]   #30 [00014731c0 - 00014771c0]         BOOTMEM
[    0.000000]   #31 [00014771c0 - 00014f71c0]         BOOTMEM
[    0.000000]   #32 [00014f71c0 - 00015371c0]         BOOTMEM
[    0.000000] Initializing HighMem for node 0 (0002d3fe:0006cc00)
[    0.000000] Memory: 1754416k/1781760k available (2121k kernel code,
26956k reserved, 1275k data, 344k init, 1040392k highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xf571e000 - 0xf57ff000   ( 900 kB)
[    0.000000]     pkmap   : 0xf5400000 - 0xf5600000   (2048 kB)
[    0.000000]     vmalloc : 0xedbfe000 - 0xf53fe000   ( 120 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xed3fe000   ( 723 MB)
[    0.000000]       .init : 0xc1352000 - 0xc13a8000   ( 344 kB)
[    0.000000]       .data : 0xc121266b - 0xc1351500   (1275 kB)
[    0.000000]       .text : 0xc1000000 - 0xc121266b   (2121 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0,
CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:512
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] console [hvc0] enabled
[    0.000000] installing Xen timer for CPU 0
[    0.000000] Detected 2327.500 MHz processor.
[    0.004000] Calibrating delay loop (skipped), value calculated
using timer frequency.. 4655.00 BogoMIPS (lpj=9310000)
[    0.004000] Security Framework initialized
[    0.004000] SELinux:  Disabled at boot.
[    0.004000] Mount-cache hash table entries: 512
[    0.004000] Initializing cgroup subsys ns
[    0.004000] Initializing cgroup subsys cpuacct
[    0.004000] Initializing cgroup subsys devices
[    0.004000] Initializing cgroup subsys freezer
[    0.004000] CPU: Unsupported number of siblings 4
[    0.004000] Performance Events: Core2 events,
[    0.004000] no APIC, boot with the "lapic" boot parameter to
force-enable it.
[    0.004000] no hardware sampling interrupt available.
[    0.004000] Intel PMU driver.
[    0.004000] ... version:                2
[    0.004000] ... bit width:              40
[    0.004000] ... generic registers:      2
[    0.004000] ... value mask:             000000ffffffffff
[    0.004000] ... max period:             000000007fffffff
[    0.004000] ... fixed-purpose events:   3
[    0.004000] ... event mask:             0000000700000003
[    0.004000] SMP alternatives: switching to UP code
[    0.028356] installing Xen timer for CPU 1
[    0.028388] SMP alternatives: switching to SMP code
[    0.004000] Initializing CPU#1
[    0.004000] CPU: Unsupported number of siblings 4
[    0.058996] Brought up 2 CPUs
[    0.059170] devtmpfs: initialized
[    0.060049] Grant table initialized
[    0.060101] NET: Registered protocol family 16
[    0.060154] PCI: Fatal: No config space access function found
[    0.064081] bio: create slab <bio-0> at 0
[    0.068041] ACPI: Interpreter disabled.
[    0.068078] xen_balloon: Initialising balloon driver.
[    0.068097] vgaarb: loaded
[    0.068097] PCI: System does not support PCI
[    0.068097] PCI: System does not support PCI
[    0.068098] NetLabel: Initializing
[    0.068098] NetLabel:  domain hash size = 128
[    0.068098] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.068098] NetLabel:  unlabeled traffic allowed by default
[    0.068126] Switching to clocksource xen
[    0.068158] pnp: PnP ACPI: disabled
[    0.069539] NET: Registered protocol family 2
[    0.069588] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.069718] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[    0.070300] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    0.070573] TCP: Hash tables configured (established 131072 bind 65536)
[    0.070586] TCP reno registered
[    0.070598] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.070614] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.070809] NET: Registered protocol family 1
[    0.070863] Unpacking initramfs...
[    0.081398] Freeing initrd memory: 4484k freed
[    0.083785] platform rtc_cmos: registered platform RTC device (no
PNP device found)
[    0.085323] audit: initializing netlink socket (disabled)
[    0.085344] type=2000 audit(1294999046.603:1): initialized
[    0.099322] highmem bounce pool size: 64 pages
[    0.099333] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.104120] VFS: Disk quotas dquot_6.5.2
[    0.104293] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.104527] msgmni has been set to 1403
[    0.105192] alg: No test for stdrng (krng)
[    0.105495] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 254)
[    0.105506] io scheduler noop registered (default)
[    0.117357] loop: module loaded
[    0.117777] PNP: No PS/2 controller found. Probing ports directly.
[    0.118822] mice: PS/2 mouse device common for all mice
[    0.118930] cpuidle: using governor ladder
[    0.118938] cpuidle: using governor menu
[    0.119019] TCP cubic registered
[    0.119032] NET: Registered protocol family 17
[    0.119056] Using IPI No-Shortcut mode
[    0.119409] registered taskstats version 1
[    0.119436] XENBUS: Device with no driver: device/vif/0
[    0.119444] XENBUS: Device with no driver: device/vbd/2049
[    0.119451] XENBUS: Device with no driver: device/vbd/2064
[    0.119457] XENBUS: Device with no driver: device/vbd/2051
[    0.119599] Freeing unused kernel memory: 344k freed
[    0.120449] Write protecting the kernel text: 2124k
[    0.120785] Write protecting the kernel read-only data: 952k
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 xen-netfront.ko module
[    0.382526] Initialising Xen virtual ethernet driver.
Loading xen-netfront.ko module
insmod: error inserting ''/lib/xen-netfront.ko'': -1 File exists
Loading xen-blkfront.ko module
[    0.488219] blkfront device/vbd/2049 num-ring-pages 1 nr_ents 32.
[    0.491783] blkfront device/vbd/2064 num-ring-pages 1 nr_ents 32.
[    0.495657] blkfront device/vbd/2051 num-ring-pages 1 nr_ents 32.
[    0.498170] blkfront: regular deviceid=0x801 major,minor=8,1,
assuming parts/disk=16
[    0.499443] blkfront: regular deviceid=0x810 major,minor=8,16,
assuming parts/disk=16
[    0.499831]  xvdb: unknown partition table
[    0.501076] blkfront: regular deviceid=0x803 major,minor=8,3,
assuming parts/disk=16
Loading xen-blkfront.ko module
insmod: error inserting ''/lib/xen-blkfront.ko'': -1 File exists
Loading dm-mod.ko module
[    0.600339] device-mapper: uevent: version 1.0.3
[    0.600546] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05)
initialised: dm-devel@redhat.com
Loading linear.ko module
[    0.602246] md: linear personality registered for level -1
Loading mbcache.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading dm-log.ko module
Loading dm-region-hash.ko module
Loading dm-region-hash.ko module
insmod: error inserting ''/lib/dm-region-hash.ko'': -1 File
exists
Scanning and configuring dmraid supported devices
Creating root device.
Mounting root filesystem.
[    0.766409] kjournald starting.  Commit interval 5 seconds
[    0.766439] EXT3-fs (xvda1): mounted filesystem with ordered data mode
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys

INIT: version 2.86 booting

[    4.742223] usbcore: registered new interface driver usbfs
[    4.742259] usbcore: registered new interface driver hub
[    4.742389] usbcore: registered new device driver usb
mount: mount point /proc/bus/usb does not exist
		Welcome to Amazon Linux AMI
		Press ''I'' to enter interactive startup.
Setting clock : Fri Jan 14 09:57:33 UTC 2011 [  OK  ]

Starting udev: udevd[387]: udev: missing sysfs features; please update
the kernel or disable the kernel''s CONFIG_SYSFS_DEPRECATED option;
udev may fail to work correctly


[  OK  ]

Setting hostname localhost.localdomain:  [  OK  ]

Setting up Logical Volume Management:   File-based locking
initialisation failed.
  No volume groups found
[  OK  ]

Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/xvda1
/: clean, 27564/1048576 files, 252312/2097152 blocks
[  OK  ]

Remounting root filesystem in read-write mode:  [  OK  ]

Mounting local filesystems:  [  OK  ]

Enabling local filesystem quotas:  [  OK  ]

could not parse required file /etc/security/console.perms.d/*.perms
Enabling /etc/fstab swaps:  [  OK  ]

INIT: Entering runlevel: 3

Entering non-interactive startup
Starting background readahead: [  OK  ]

Bringing up loopback interface:  [  OK  ]

Bringing up interface eth0:
Determining IP information for eth0...cp: cannot stat
`/etc/resolv.conf'': No such file or directory
 done.
[  OK  ]

Starting system logger: Jan 14 09:58:03 ip-10-128-154-84 syslogd 1.4.1: restart.

[  OK  ]

Starting kernel logger: [  OK  ]

Jan 14 09:58:04 ip-10-128-154-84 klogd: klogd 1.4.1, log source /proc/kmsg
started.

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000] Reserving
virtual address space above 0xf5800000

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000] Initializing
cgroup subsys cpuset

Starting irqbalance: Jan 14 09:58:04 ip-10-128-154-84 klogd: [
0.000000] Initializing cgroup subsys cpu

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000] Linux version
2.6.34.7-56.40.amzn1.i686 (mockbuild@build-31003.build) (gcc version
4.4.4 20100525 (Red Hat 4.4.4-5) (GCC) ) #1 SMP Fri Oct 22 18:48:33
UTC 2010

[  OK  ]

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000] ACPI in
unprivileged domain disabled

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000] BIOS-provided
physical RAM map:

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000]  Xen:
0000000000000000 - 00000000000a0000 (usable)

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000]  Xen:
00000000000a0000 - 0000000000100000 (reserved)

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000]  Xen:
0000000000100000 - 000000006cc00000 (usable)

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000] NX (Execute
Disable) protection: active

Jan 14 09:58:04 ip-10-128-154-84 klogd: [    0.000000] DMI not present
or invalid.

Jan 14 09:58:04 ip-10-128-154-84 cpuspeed: CPU Frequency scaling is
currently not supported on xen kernels

Jan 14 09:58:05 ip-10-128-154-84 klogd: [    0.000000] last_pfn 0x6cc00
max_arch_pfn = 0x1000000

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000]
init_memory_mapping: 0000000000000000-000000002d3fe000

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] RAMDISK:
0156f000 - 019d0000

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] 1016MB HIGHMEM available.

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] 723MB LOWMEM available.

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000]   mapped low
ram: 0 - 2d3fe000

Running cloud-initJan 14 09:58:06 ip-10-128-154-84 klogd: [
0.000000]   low ram: 0 - 2d3fe000


cloud-init:  initializationJan 14 09:58:06 ip-10-128-154-84 klogd: [
 0.000000] Zone PFN ranges:

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000]   DMA
0x00000001 -> 0x00001000

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000]   Normal
0x00001000 -> 0x0002d3fe

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000]   HighMem
0x0002d3fe -> 0x0006cc00

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Movable zone
start PFN for each node

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000]
early_node_map[2] active PFN ranges

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000]     0:
0x00000001 -> 0x000000a0

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000]     0:
0x00000100 -> 0x0006cc00

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Using APIC driver default

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] SMP: Allowing 2
CPUs, 0 hotplug CPUs

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Local APIC
disabled by BIOS -- you can enable it with "lapic"

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] APIC: disable
apic facility

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] APIC: switched
to apic NOOP

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Allocating PCI
resources starting at 6cc00000 (gap: 6cc00000:93400000)

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Booting
paravirtualized kernel on Xen

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Xen version:
3.0.3-rc5-8.el5

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] setup_percpu:
NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] PERCPU:
Embedded 16 pages/cpu @c1453000 s41172 r0 d24364 u65536

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] pcpu-alloc:
s41172 r0 d24364 u65536 alloc=16*4096

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] pcpu-alloc: [0] 0 [0] 1

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Built 1
zonelists in Zone order, mobility grouping on.  Total pages: 441862

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Kernel command
line: root=LABEL=/ console=hvc0

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] PID hash table
entries: 4096 (order: 2, 16384 bytes)

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Dentry cache
hash table entries: 131072 (order: 7, 524288 bytes)

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Inode-cache
hash table entries: 65536 (order: 6, 262144 bytes)

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Enabling fast
FPU save and restore... done.

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Enabling
unmasked SIMD FPU exception support... done.

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Initializing CPU#0

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000] Subtract (33
early reservations)

Jan 14 09:58:06 ip-10-128-154-84 klogd: [    0.000000]   #1
[0001b86000 - 0001b98000]  XEN PAGETABLES

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #2
[0000001000 - 0000002000]   EX TRAMPOLINE

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #3
[0001000000 - 0001449b5c]   TEXT DATA BSS

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #4
[000156f000 - 00019d0000]         RAMDISK

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #5
[00019d0000 - 0001b86000]  XEN START INFO

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #6
[0000002000 - 0000003000]      TRAMPOLINE

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #7
[0000003000 - 0000007000]     ACPI WAKEUP

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #8
[0000100000 - 0000256000]         PGTABLE

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #9
[000144a000 - 000144b000]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #10
[0001b98000 - 0002930000]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #11
[0001449b80 - 0001449b84]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #12
[0001449bc0 - 0001449c80]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #13
[0001449c80 - 0001449d08]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #14
[000144b000 - 000144e000]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #15
[0001449d40 - 0001449e00]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #16
[000144e000 - 0001451000]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #17
[0001449e00 - 0001449e90]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #18
[0001449ec0 - 0001449f00]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #19
[0001449f00 - 0001449f40]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #20
[0001449f40 - 0001449f80]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #21
[0001449f80 - 0001449f9a]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #22
[0001449fc0 - 0001449fda]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #23
[0001453000 - 0001473000]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #24
[0001473000 - 0001473004]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #25
[0001473040 - 0001473044]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #26
[0001473080 - 0001473088]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #27
[00014730c0 - 00014730c8]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #28
[0001473100 - 0001473180]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #29
[0001473180 - 00014731ac]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #30
[00014731c0 - 00014771c0]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #31
[00014771c0 - 00014f71c0]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]   #32
[00014f71c0 - 00015371c0]         BOOTMEM

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] Initializing
HighMem for node 0 (0002d3fe:0006cc00)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] Memory:
1754416k/1781760k available (2121k kernel code, 26956k reserved, 1275k
data, 344k init, 1040392k highmem)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] virtual kernel
memory layout:

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]     fixmap  :
0xf571e000 - 0xf57ff000   ( 900 kB)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]     pkmap   :
0xf5400000 - 0xf5600000   (2048 kB)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]     vmalloc :
0xedbfe000 - 0xf53fe000   ( 120 MB)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]     lowmem  :
0xc0000000 - 0xed3fe000   ( 723 MB)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]       .init :
0xc1352000 - 0xc13a8000   ( 344 kB)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]       .data :
0xc121266b - 0xc1351500   (1275 kB)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000]       .text :
0xc1000000 - 0xc121266b   (2121 kB)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] SLUB:
Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] Hierarchical
RCU implementation.

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] NR_IRQS:512

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] Console: colour
dummy device 80x25

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] console [tty0] enabled

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] console [hvc0] enabled

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] installing Xen
timer for CPU 0

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.000000] Detected
2327.500 MHz processor.

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Calibrating
delay loop (skipped), value calculated using timer frequency.. 4655.00
BogoMIPS (lpj=9310000)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Security
Framework initialized

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] SELinux:
Disabled at boot.

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Mount-cache
hash table entries: 512

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Initializing
cgroup subsys ns

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Initializing
cgroup subsys cpuacct

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Initializing
cgroup subsys devices

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Initializing
cgroup subsys freezer

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] CPU:
Unsupported number of siblings 4

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Performance
Events: Core2 events,

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] no APIC, boot
with the "lapic" boot parameter to force-enable it.

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] no hardware
sampling interrupt available.

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Intel PMU driver.

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] ... version:
            2

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] ... bit width:
            40

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] ... generic
registers:      2

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] ... value mask:
            000000ffffffffff

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] ... max period:
            000000007fffffff

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] ...
fixed-purpose events:   3

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] ... event mask:
            0000000700000003

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] SMP
alternatives: switching to UP code

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.028356] installing Xen
timer for CPU 1

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.028388] SMP
alternatives: switching to SMP code

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] Initializing CPU#1

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.004000] CPU:
Unsupported number of siblings 4

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.058996] Brought up 2 CPUs

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.059170] devtmpfs: initialized

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.060049] Grant table initialized

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.060101] NET: Registered
protocol family 16

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.060154] PCI: Fatal: No
config space access function found

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.064081] bio: create
slab <bio-0> at 0

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068041] ACPI:
Interpreter disabled.

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068078] xen_balloon:
Initialising balloon driver.

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068097] vgaarb: loaded

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068097] PCI: System
does not support PCI

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068097] PCI: System
does not support PCI

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068098] NetLabel: Initializing

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068098] NetLabel:
domain hash size = 128

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068098] NetLabel:
protocols = UNLABELED CIPSOv4

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068098] NetLabel:
unlabeled traffic allowed by default

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068126] Switching to
clocksource xen

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.068158] pnp: PnP ACPI: disabled

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.069539] NET: Registered
protocol family 2

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.069588] IP route cache
hash table entries: 32768 (order: 5, 131072 bytes)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.069718] TCP established
hash table entries: 131072 (order: 8, 1048576 bytes)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.070300] TCP bind hash
table entries: 65536 (order: 7, 524288 bytes)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.070573] TCP: Hash
tables configured (established 131072 bind 65536)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.070586] TCP reno registered

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.070598] UDP hash table
entries: 512 (order: 2, 16384 bytes)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.070614] UDP-Lite hash
table entries: 512 (order: 2, 16384 bytes)

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.070809] NET: Registered
protocol family 1

Jan 14 09:58:07 ip-10-128-154-84 klogd: [    0.070863] Unpacking initramfs...

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.081398] Freeing initrd
memory: 4484k freed

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.083785] platform
rtc_cmos: registered platform RTC device (no PNP device found)

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.085323] audit:
initializing netlink socket (disabled)

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.085344] type=2000
audit(1294999046.603:1): initialized

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.099322] highmem bounce
pool size: 64 pages

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.099333] HugeTLB
registered 2 MB page size, pre-allocated 0 pages

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.104120] VFS: Disk
quotas dquot_6.5.2

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.104293] Dquot-cache
hash table entries: 1024 (order 0, 4096 bytes)

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.104527] msgmni has been
set to 1403

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.105192] alg: No test
for stdrng (krng)

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.105495] Block layer
SCSI generic (bsg) driver version 0.4 loaded (major 254)

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.105506] io scheduler
noop registered (default)

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.117357] loop: module loaded

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.117777] PNP: No PS/2
controller found. Probing ports directly.

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.118822] mice: PS/2
mouse device common for all mice

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.118930] cpuidle: using
governor ladder

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.118938] cpuidle: using
governor menu

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.119019] TCP cubic registered

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.119032] NET: Registered
protocol family 17

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.119056] Using IPI
No-Shortcut mode

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.119409] registered
taskstats version 1

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.119436] XENBUS: Device
with no driver: device/vif/0

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.119444] XENBUS: Device
with no driver: device/vbd/2049

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.119451] XENBUS: Device
with no driver: device/vbd/2064

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.119457] XENBUS: Device
with no driver: device/vbd/2051

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.119599] Freeing unused
kernel memory: 344k freed

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.120449] Write
protecting the kernel text: 2124k

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.120785] Write
protecting the kernel read-only data: 952k

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.382526] Initialising
Xen virtual ethernet driver.

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.488219] blkfront
device/vbd/2049 num-ring-pages 1 nr_ents 32.

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.491783] blkfront
device/vbd/2064 num-ring-pages 1 nr_ents 32.

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.495657] blkfront
device/vbd/2051 num-ring-pages 1 nr_ents 32.

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.498170] blkfront:
regular deviceid=0x801 major,minor=8,1, assuming parts/disk=16

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.499443] blkfront:
regular deviceid=0x810 major,minor=8,16, assuming parts/disk=16

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.499831]  xvdb: unknown
partition table

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.501076] blkfront:
regular deviceid=0x803 major,minor=8,3, assuming parts/disk=16

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.600339] device-mapper:
uevent: version 1.0.3

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.600546] device-mapper:
ioctl: 4.17.0-ioctl (2010-03-05) initialised: dm-devel@redhat.com

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.602246] md: linear
personality registered for level -1

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.766409] kjournald
starting.  Commit interval 5 seconds

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    0.766439] EXT3-fs
(xvda1): mounted filesystem with ordered data mode

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    4.742223] usbcore:
registered new interface driver usbfs

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    4.742259] usbcore:
registered new interface driver hub

Jan 14 09:58:08 ip-10-128-154-84 klogd: [    4.742389] usbcore:
registered new device driver usb

Jan 14 09:58:08 ip-10-128-154-84 klogd: [   23.343407] rtc_cmos: probe
of rtc_cmos failed with error -16

Jan 14 09:58:08 ip-10-128-154-84 klogd: [   23.795668] md:
Autodetecting RAID arrays.

Jan 14 09:58:08 ip-10-128-154-84 klogd: [   23.795672] md: Scanned 0
and added 0 devices.

Jan 14 09:58:08 ip-10-128-154-84 klogd: [   23.795673] md: autorun ...

Jan 14 09:58:08 ip-10-128-154-84 klogd: [   23.795674] md: ... autorun DONE.

Jan 14 09:58:08 ip-10-128-154-84 klogd: [   24.572227] EXT3-fs
(xvda1): using internal journal

cloud-init start-local running: Fri, 14 Jan 2011 09:58:08 +0000. up
41.73 seconds
Jan 14 09:58:08 ip-10-128-154-84 [CLOUDINIT] 2011-01-14 09:58:08,269 -
cloud-init[INFO]: cloud-init start-local running: Fri, 14 Jan 2011
09:58:08 +0000. up 41.73 seconds

no instance data found in start-local
cloud-init start running: Fri, 14 Jan 2011 09:58:08 +0000. up 42.05 seconds
Jan 14 09:58:08 ip-10-128-154-84 [CLOUDINIT] 2011-01-14 09:58:08,589 -
cloud-init[INFO]: cloud-init start running: Fri, 14 Jan 2011 09:58:08
+0000. up 42.05 seconds

found data source: DataSourceEc2
[  OK  ]

cloud-init:  sshJan 14 09:58:09 ip-10-128-154-84 [CLOUDINIT]
2011-01-14 09:58:09,072 - cloud-init-cfg[INFO]: cloud-init-cfg
[''ssh'']

ec2:
ec2: #############################################################
ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
ec2: 2048 c7:7e:07:17:41:87:9b:2d:93:f0:14:51:e9:bc:1e:95
/etc/ssh/ssh_host_rsa_key.pub (RSA)
ec2: 1024 de:10:1c:6f:1f:c8:b3:70:2d:f7:db:be:06:e1:bb:8c
/etc/ssh/ssh_host_dsa_key.pub (DSA)
ec2: -----END SSH HOST KEY FINGERPRINTS-----
ec2: #############################################################
[  OK  ]

cloud-init:  mountsJan 14 09:58:10 ip-10-128-154-84 ec2:

Jan 14 09:58:10 ip-10-128-154-84 ec2:
#############################################################

Jan 14 09:58:10 ip-10-128-154-84 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----

Jan 14 09:58:10 ip-10-128-154-84 ec2: 2048
c7:7e:07:17:41:87:9b:2d:93:f0:14:51:e9:bc:1e:95
/etc/ssh/ssh_host_rsa_key.pub (RSA)

Jan 14 09:58:10 ip-10-128-154-84 ec2: 1024
de:10:1c:6f:1f:c8:b3:70:2d:f7:db:be:06:e1:bb:8c
/etc/ssh/ssh_host_dsa_key.pub (DSA)

Jan 14 09:58:10 ip-10-128-154-84 ec2: -----END SSH HOST KEY FINGERPRINTS-----

Jan 14 09:58:10 ip-10-128-154-84 ec2:
#############################################################

Jan 14 09:58:11 ip-10-128-154-84 [CLOUDINIT] 2011-01-14 09:58:10,890 -
cloud-init-cfg[INFO]: cloud-init-cfg [''mounts'']

Jan 14 09:58:11 ip-10-128-154-84 klogd: [   45.028900] Adding 917500k
swap on /dev/xvda3.  Priority:-1 extents:1 across:917500k SS

Jan 14 09:58:11 ip-10-128-154-84 klogd: [   45.272824] kjournald
starting.  Commit interval 5 seconds

Jan 14 09:58:11 ip-10-128-154-84 klogd: [   45.313889] EXT3-fs (xvdb):
using internal journal

Jan 14 09:58:11 ip-10-128-154-84 klogd: [   45.313898] EXT3-fs (xvdb):
mounted filesystem with ordered data mode

[  OK  ]

cloud-init:  package-setupJan 14 09:58:12 ip-10-128-154-84 [CLOUDINIT]
2011-01-14 09:58:12,072 - cloud-init-cfg[INFO]: cloud-init-cfg
[''package-setup'']

Jan 14 09:58:14 ip-10-128-154-84 klogd: [   47.510541] NET: Registered
protocol family 10

Jan 14 09:58:14 ip-10-128-154-84 klogd: [   47.510708] lo: Disabled
Privacy Extensions

[  OK  ]

cloud-init:  runcmd[  OK  ]

Mounting other filesystems:  [  OK  ]

Jan 14 09:58:19 ip-10-128-154-84 [CLOUDINIT] 2011-01-14 09:58:19,666 -
cloud-init-cfg[INFO]: cloud-init-cfg [''runcmd'']

Retrigger failed udev events[  OK  ]

Generating SSH1 RSA host key: [  OK  ]

Starting sshd: [  OK  ]

Starting ntpd: [  OK  ]

Jan 14 09:58:20 ip-10-128-154-84 ntpd[904]: ntpd 4.2.4p8@1.1612-o Fri
Oct  1 22:46:36 UTC 2010 (1)

Jan 14 09:58:20 ip-10-128-154-84 ntpd[905]: precision = 0.499 usec

Jan 14 09:58:20 ip-10-128-154-84 ntpd[905]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled

Jan 14 09:58:20 ip-10-128-154-84 ntpd[905]: Listening on interface #1
wildcard, ::#123 Disabled

Jan 14 09:58:20 ip-10-128-154-84 ntpd[905]: Listening on interface #2
lo, ::1#123 Enabled

Jan 14 09:58:20 ip-10-128-154-84 ntpd[905]: Listening on interface #3
eth0, fe80::1031:40ff:fe00:99a6#123 Enabled

Jan 14 09:58:20 ip-10-128-154-84 ntpd[905]: Listening on interface #4
lo, 127.0.0.1#123 Enabled

Jan 14 09:58:20 ip-10-128-154-84 ntpd[905]: Listening on interface #5
eth0, 10.128.154.84#123 Enabled

Jan 14 09:58:20 ip-10-128-154-84 ntpd[905]: Listening on routing
socket on fd #22 for interface updates

Jan 14 09:58:20 ip-10-128-154-84 ntpd[905]: kernel time sync status 2040

Starting sendmail: [  OK  ]

Starting sm-client: [  OK  ]

Starting crond: [  OK  ]

Starting anacron: [  OK  ]

Starting atd: [  OK  ]
[  OK  ]

Starting yum-updatesd: [  OK  ]

Running cloud-init user-scripts (none found)[  OK  ]

---

# dmesg
[    0.000000] Reserving virtual address space above 0xf5800000
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.34.7-56.40.amzn1.i686
(mockbuild@build-31003.build) (gcc version 4.4.4 20100525 (Red Hat
4.4.4-5) (GCC) ) #1 SMP Fri Oct 22 18:48:33 UTC 2010
[    0.000000] ACPI in unprivileged domain disabled
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
[    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 000000006cc00000 (usable)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] e820 update range: 0000000000000000 - 0000000000001000
(usable) ==> (reserved)
[    0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[    0.000000] last_pfn = 0x6cc00 max_arch_pfn = 0x1000000
[    0.000000] initial memory mapped : 0 - 027ff000
[    0.000000] init_memory_mapping: 0000000000000000-000000002d3fe000
[    0.000000]  0000000000 - 002d3fe000 page 4k
[    0.000000] kernel direct mapping tables up to 2d3fe000 @ 100000-26d000
[    0.000000] RAMDISK: 0156f000 - 019d0000
[    0.000000] 1016MB HIGHMEM available.
[    0.000000] 723MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 2d3fe000
[    0.000000]   low ram: 0 - 2d3fe000
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000001 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x0002d3fe
[    0.000000]   HighMem  0x0002d3fe -> 0x0006cc00
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000001 -> 0x000000a0
[    0.000000]     0: 0x00000100 -> 0x0006cc00
[    0.000000] On node 0 totalpages: 445343
[    0.000000] free_area_init_node: node 0, pgdat c134db40,
node_mem_map c1b98020
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 3967 pages, LIFO batch:0
[    0.000000]   Normal zone: 1416 pages used for memmap
[    0.000000]   Normal zone: 179830 pages, LIFO batch:31
[    0.000000]   HighMem zone: 2033 pages used for memmap
[    0.000000]   HighMem zone: 258065 pages, LIFO batch:31
[    0.000000] Using APIC driver default
[    0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[    0.000000] Local APIC disabled by BIOS -- you can enable it with
"lapic"
[    0.000000] APIC: disable apic facility
[    0.000000] APIC: switched to apic NOOP
[    0.000000] nr_irqs_gsi: 16
[    0.000000] Allocating PCI resources starting at 6cc00000 (gap:
6cc00000:93400000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 3.0.3-rc5-8.el5
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2
nr_node_ids:1
[    0.000000] PERCPU: Embedded 16 pages/cpu @c1453000 s41172 r0 d24364 u65536
[    0.000000] early_res array is doubled to 64 at [7000 - 77ff]
[    0.000000] pcpu-alloc: s41172 r0 d24364 u65536 alloc=16*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] trying to map vcpu_info 0 at c1456010, mfn cdd5c, offset 16
[    0.000000] register_vcpu_info failed: err=-38
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 441862
[    0.000000] Kernel command line: root=LABEL=/ console=hvc0
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] Subtract (33 early reservations)
[    0.000000]   #1 [0001b86000 - 0001b98000]  XEN PAGETABLES
[    0.000000]   #2 [0000001000 - 0000002000]   EX TRAMPOLINE
[    0.000000]   #3 [0001000000 - 0001449b5c]   TEXT DATA BSS
[    0.000000]   #4 [000156f000 - 00019d0000]         RAMDISK
[    0.000000]   #5 [00019d0000 - 0001b86000]  XEN START INFO
[    0.000000]   #6 [0000002000 - 0000003000]      TRAMPOLINE
[    0.000000]   #7 [0000003000 - 0000007000]     ACPI WAKEUP
[    0.000000]   #8 [0000100000 - 0000256000]         PGTABLE
[    0.000000]   #9 [000144a000 - 000144b000]         BOOTMEM
[    0.000000]   #10 [0001b98000 - 0002930000]         BOOTMEM
[    0.000000]   #11 [0001449b80 - 0001449b84]         BOOTMEM
[    0.000000]   #12 [0001449bc0 - 0001449c80]         BOOTMEM
[    0.000000]   #13 [0001449c80 - 0001449d08]         BOOTMEM
[    0.000000]   #14 [000144b000 - 000144e000]         BOOTMEM
[    0.000000]   #15 [0001449d40 - 0001449e00]         BOOTMEM
[    0.000000]   #16 [000144e000 - 0001451000]         BOOTMEM
[    0.000000]   #17 [0001449e00 - 0001449e90]         BOOTMEM
[    0.000000]   #18 [0001449ec0 - 0001449f00]         BOOTMEM
[    0.000000]   #19 [0001449f00 - 0001449f40]         BOOTMEM
[    0.000000]   #20 [0001449f40 - 0001449f80]         BOOTMEM
[    0.000000]   #21 [0001449f80 - 0001449f9a]         BOOTMEM
[    0.000000]   #22 [0001449fc0 - 0001449fda]         BOOTMEM
[    0.000000]   #23 [0001453000 - 0001473000]         BOOTMEM
[    0.000000]   #24 [0001473000 - 0001473004]         BOOTMEM
[    0.000000]   #25 [0001473040 - 0001473044]         BOOTMEM
[    0.000000]   #26 [0001473080 - 0001473088]         BOOTMEM
[    0.000000]   #27 [00014730c0 - 00014730c8]         BOOTMEM
[    0.000000]   #28 [0001473100 - 0001473180]         BOOTMEM
[    0.000000]   #29 [0001473180 - 00014731ac]         BOOTMEM
[    0.000000]   #30 [00014731c0 - 00014771c0]         BOOTMEM
[    0.000000]   #31 [00014771c0 - 00014f71c0]         BOOTMEM
[    0.000000]   #32 [00014f71c0 - 00015371c0]         BOOTMEM
[    0.000000] Initializing HighMem for node 0 (0002d3fe:0006cc00)
[    0.000000] Memory: 1754416k/1781760k available (2121k kernel code,
26956k reserved, 1275k data, 344k init, 1040392k highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xf571e000 - 0xf57ff000   ( 900 kB)
[    0.000000]     pkmap   : 0xf5400000 - 0xf5600000   (2048 kB)
[    0.000000]     vmalloc : 0xedbfe000 - 0xf53fe000   ( 120 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xed3fe000   ( 723 MB)
[    0.000000]       .init : 0xc1352000 - 0xc13a8000   ( 344 kB)
[    0.000000]       .data : 0xc121266b - 0xc1351500   (1275 kB)
[    0.000000]       .text : 0xc1000000 - 0xc121266b   (2121 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0,
CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:512
[    0.000000] CPU 0 irqstacks, hard=c1453000 soft=c1454000
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] console [hvc0] enabled
[    0.000000] installing Xen timer for CPU 0
[    0.000000] Detected 2327.500 MHz processor.
[    0.004000] Calibrating delay loop (skipped), value calculated
using timer frequency.. 4655.00 BogoMIPS (lpj=9310000)
[    0.004000] Security Framework initialized
[    0.004000] SELinux:  Disabled at boot.
[    0.004000] Mount-cache hash table entries: 512
[    0.004000] Initializing cgroup subsys ns
[    0.004000] Initializing cgroup subsys cpuacct
[    0.004000] Initializing cgroup subsys devices
[    0.004000] Initializing cgroup subsys freezer
[    0.004000] CPU: Unsupported number of siblings 4
[    0.004000] Performance Events: Core2 events,
[    0.004000] no APIC, boot with the "lapic" boot parameter to
force-enable it.
[    0.004000] no hardware sampling interrupt available.
[    0.004000] Intel PMU driver.
[    0.004000] ... version:                2
[    0.004000] ... bit width:              40
[    0.004000] ... generic registers:      2
[    0.004000] ... value mask:             000000ffffffffff
[    0.004000] ... max period:             000000007fffffff
[    0.004000] ... fixed-purpose events:   3
[    0.004000] ... event mask:             0000000700000003
[    0.004000] SMP alternatives: switching to UP code
[    0.028353] CPU 1 irqstacks, hard=c1463000 soft=c1464000
[    0.028356] installing Xen timer for CPU 1
[    0.028388] SMP alternatives: switching to SMP code
[    0.004000] Initializing CPU#1
[    0.004000] CPU: Unsupported number of siblings 4
[    0.058996] Brought up 2 CPUs
[    0.059013] sizeof(vma)=92 bytes
[    0.059018] sizeof(page)=32 bytes
[    0.059019] sizeof(inode)=352 bytes
[    0.059021] sizeof(dentry)=132 bytes
[    0.059022] sizeof(ext3inode)=508 bytes
[    0.059023] sizeof(buffer_head)=56 bytes
[    0.059025] sizeof(skbuff)=184 bytes
[    0.059026] sizeof(task_struct)=3232 bytes
[    0.059170] devtmpfs: initialized
[    0.060049] Grant table initialized
[    0.060101] NET: Registered protocol family 16
[    0.060154] PCI: Fatal: No config space access function found
[    0.064081] bio: create slab <bio-0> at 0
[    0.068041] ACPI: Interpreter disabled.
[    0.068078] xen_balloon: Initialising balloon driver.
[    0.068097] vgaarb: loaded
[    0.068097] PCI: System does not support PCI
[    0.068097] PCI: System does not support PCI
[    0.068098] NetLabel: Initializing
[    0.068098] NetLabel:  domain hash size = 128
[    0.068098] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.068098] NetLabel:  unlabeled traffic allowed by default
[    0.068126] Switching to clocksource xen
[    0.068158] pnp: PnP ACPI: disabled
[    0.069539] NET: Registered protocol family 2
[    0.069588] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.069718] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[    0.070300] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    0.070573] TCP: Hash tables configured (established 131072 bind 65536)
[    0.070586] TCP reno registered
[    0.070598] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.070614] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.070809] NET: Registered protocol family 1
[    0.070830] PCI: CLS 0 bytes, default 64
[    0.070863] Unpacking initramfs...
[    0.081398] Freeing initrd memory: 4484k freed
[    0.083785] platform rtc_cmos: registered platform RTC device (no
PNP device found)
[    0.085323] audit: initializing netlink socket (disabled)
[    0.085344] type=2000 audit(1294999046.603:1): initialized
[    0.099322] highmem bounce pool size: 64 pages
[    0.099333] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.104120] VFS: Disk quotas dquot_6.5.2
[    0.104293] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.104527] msgmni has been set to 1403
[    0.105192] alg: No test for stdrng (krng)
[    0.105495] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 254)
[    0.105506] io scheduler noop registered (default)
[    0.117357] loop: module loaded
[    0.117777] PNP: No PS/2 controller found. Probing ports directly.
[    0.118822] mice: PS/2 mouse device common for all mice
[    0.118930] cpuidle: using governor ladder
[    0.118938] cpuidle: using governor menu
[    0.119019] TCP cubic registered
[    0.119032] NET: Registered protocol family 17
[    0.119056] Using IPI No-Shortcut mode
[    0.119409] registered taskstats version 1
[    0.119436] XENBUS: Device with no driver: device/vif/0
[    0.119444] XENBUS: Device with no driver: device/vbd/2049
[    0.119451] XENBUS: Device with no driver: device/vbd/2064
[    0.119457] XENBUS: Device with no driver: device/vbd/2051
[    0.119599] Freeing unused kernel memory: 344k freed
[    0.120449] Write protecting the kernel text: 2124k
[    0.120785] Write protecting the kernel read-only data: 952k
[    0.382526] Initialising Xen virtual ethernet driver.
[    0.488219] blkfront device/vbd/2049 num-ring-pages 1 nr_ents 32.
[    0.491783] blkfront device/vbd/2064 num-ring-pages 1 nr_ents 32.
[    0.495657] blkfront device/vbd/2051 num-ring-pages 1 nr_ents 32.
[    0.498170] blkfront: regular deviceid=0x801 major,minor=8,1,
assuming parts/disk=16
[    0.499443] blkfront: regular deviceid=0x810 major,minor=8,16,
assuming parts/disk=16
[    0.499831]  xvdb: unknown partition table
[    0.501076] blkfront: regular deviceid=0x803 major,minor=8,3,
assuming parts/disk=16
[    0.600339] device-mapper: uevent: version 1.0.3
[    0.600546] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05)
initialised: dm-devel@redhat.com
[    0.602246] md: linear personality registered for level -1
[    0.766409] kjournald starting.  Commit interval 5 seconds
[    0.766439] EXT3-fs (xvda1): mounted filesystem with ordered data mode
[    4.742223] usbcore: registered new interface driver usbfs
[    4.742259] usbcore: registered new interface driver hub
[    4.742389] usbcore: registered new device driver usb
[   23.343407] rtc_cmos: probe of rtc_cmos failed with error -16
[   23.795668] md: Autodetecting RAID arrays.
[   23.795672] md: Scanned 0 and added 0 devices.
[   23.795673] md: autorun ...
[   23.795674] md: ... autorun DONE.
[   24.572227] EXT3-fs (xvda1): using internal journal
[   45.028900] Adding 917500k swap on /dev/xvda3.  Priority:-1
extents:1 across:917500k SS
[   45.272824] kjournald starting.  Commit interval 5 seconds
[   45.313889] EXT3-fs (xvdb): using internal journal
[   45.313898] EXT3-fs (xvdb): mounted filesystem with ordered data mode
[   47.510541] NET: Registered protocol family 10
[   47.510708] lo: Disabled Privacy Extensions
[   57.780009] eth0: no IPv6 routers present

# uname -r
2.6.34.7-56.40.amzn1.i686

# cat /etc/fstab
#
LABEL=/     /           ext3    defaults,noatime  1   1
tmpfs       /dev/shm    tmpfs   defaults        0   0
devpts      /dev/pts    devpts  gid=5,mode=620  0   0
sysfs       /sys        sysfs   defaults        0   0
proc        /proc       proc    defaults        0   0
/dev/sdb	/media/ephemeral0	auto	defaults,comment=cloudconfig	0	2
/dev/sda3	none	swap	sw,comment=cloudconfig	0	0

# df -T -h
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/xvda1    ext3    7.9G  873M  7.0G  11% /
tmpfs        tmpfs    860M     0  860M   0% /dev/shm
/dev/xvdb     ext3    335G  195M  318G   1% /media/ephemeral0

# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw,noatime,errors=continue,data=ordered 0 0
/dev /dev tmpfs rw,relatime,mode=755 0 0
/proc /proc proc rw,relatime 0 0
/sys /sys sysfs rw,relatime 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
/dev/xvdb /media/ephemeral0 ext3 rw,relatime,errors=continue,data=ordered 0 0

# cat /proc/partitions
major minor  #blocks  name

 202        1    8388608 xvda1
 202       16  356485632 xvdb
 202        3     917504 xvda3

# ls -l /boot/
total 5172
-rw-r--r-- 1 root root   64217 Oct 22 18:50 config-2.6.34.7-56.40.amzn1.i686
drwxr-xr-x 2 root root    4096 Nov 30 01:51 grub
-rw------- 1 root root 2119707 Nov 30 01:51 initrd-2.6.34.7-56.40.amzn1.i686.img
-rw-r--r-- 1 root root  972728 Oct 22 18:50 System.map-2.6.34.7-56.40.amzn1.i686
-rwxr-xr-x 1 root root 2110080 Oct 22 18:50 vmlinuz-2.6.34.7-56.40.amzn1.i686

# cat /boot/grub/menu.lst
# created by imagebuilder
default=0
timeout=3
hiddenmenu

title Amazon Linux AMI
    root (hd0)
    kernel /boot/vmlinuz-2.6.34.7-56.40.amzn1.i686 root=LABEL=/ console=hvc0
    initrd /boot/initrd-2.6.34.7-56.40.amzn1.i686.img

# lsmod
Module                  Size  Used by
ipv6                  212103  18
binfmt_misc             5300  1
dm_mirror              10373  0
rtc_core               10588  0
rtc_lib                 1725  1 rtc_core
usbcore               102339  0
nls_base                5462  1 usbcore
dm_region_hash          7411  1 dm_mirror
dm_log                  6972  2 dm_mirror,dm_region_hash
ext3                   97660  2
jbd                    42919  1 ext3
mbcache                 4877  1 ext3
linear                  3062  0
dm_mod                 50123  2 dm_mirror,dm_log
xen_blkfront            9398  3
xen_netfront           12173  0
- - - < s n i p > - - -

Thank you, Fajar.

Regards,

GNUbie

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

Fajar A. Nugraha

2011-Jan-14 12:22 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

On Fri, Jan 14, 2011 at 6:10 PM, GNUbie <gnubie@gmail.com>
wrote:> Just a side note, I created a new domU from scratch using their stock
> image just to compare on what they have in a default settings. Below
> are the logs.
> [    0.119444] XENBUS: Device with no driver: device/vbd/2049
2049 is xvda1
> # cat /proc/partitions
> major minor  #blocks  name
>
>  202        1    8388608 xvda1
>  202       16  356485632 xvdb
>  202        3     917504 xvda3
if you have access to domU disk settings, you''ll see that one image is
mapped to xvda1 instead of xvda, and another image is mapped as xvda3.
In this case, "/boot" is in the same filesystem as "/",
which resides
on an image file formatted directly without partition, and mapped as
xvda1. That''s fine. Not a "redhat-blessed" configuration, but
it
works, IF you know what you''re doing.

On your previous boot log, you didn''t even know what you''re
mapping,
and to where (e.g there was an image mapped directly as xvda2, but the
image you created is partitioned).

Looking at your reference setup, it seems the easiest way for you
proceed is to simply create a filesystem directly on the image file,
without creating partition, and map it as xvda1. You can then proceed
like your current reference setup.

Another way is to keep using the disk image you created, but you need
to modify some things. First of all modify the mapping to use xvda
instead of xvda1. Then you also need to modify domU''s config, since
pv-grub needs "extra" line to tell where menu.lst is, and the extra
line for disk mapped as xvda1 is different from where the disk mapped
as xvda. Since you mentioned you don''t have access to domU config
file, I doubt you can make this change.

-- 
Fajar

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

Fajar A. Nugraha

2011-Jan-14 12:26 UTC

head link

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

On Fri, Jan 14, 2011 at 7:22 PM, Fajar A. Nugraha <list@fajar.net>
wrote:> On Fri, Jan 14, 2011 at 6:10 PM, GNUbie <gnubie@gmail.com> wrote:
>> Just a side note, I created a new domU from scratch using their stock
>> image just to compare on what they have in a default settings. Below
>> are the logs.
>
>> [    0.119444] XENBUS: Device with no driver: device/vbd/2049
>
> 2049 is xvda1
Sorry, meant to say sda1.

Newer kernels will silently change all [h/s]d? mappings to xvd?, so if
you use newer kernels (2.6.3x is new enough) there''s no difference
whether you use hda/sda/xvda in domU config file. That''s why your
reference boot log and /proc/partition says xvda1 instead of sda1.

-- 
Fajar

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

Xen users - Jan 2011 - Xen domU cannot boot via PV-GRUB

[Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB

Re: [Xen-users] Xen domU cannot boot via PV-GRUB