thr3ads.net - Fedora xen - [Fedora-xen] unable to launch domU (FC 8) [Dec 2008]

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

Siddharth Wagh

2008-Dec-12 15:11 UTC

[Fedora-xen] unable to launch domU (FC 8)

THERE ARE NO SPECIFIC ERROR MESSAGES, BUT THE DOMAIN IS NOT GETTING LAUNCHED
EITHER. HERE IS THE GENERATED OUTPUT FILE. CAN YOU SPOT AN ERROR IN IT? ANY
HELP APPRECIATED.

-----------------------------------------------------------

Using config file "./vm1".
Started domain domU1
Linux version 2.6.21.7-5.fc8xen (mockbuild@xenbuilder2.fedora.redhat.com)
(gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Thu Aug 7 12:44:49
EDT 2008

BIOS-provided physical RAM map:

sanitize start

sanitize bail 0

copy_e820_map() start: 0000000000000000 size: 0000000004800000 end:
0000000004800000 type: 1

 Xen: 0000000000000000 - 0000000004800000 (usable)

0MB HIGHMEM available.

72MB LOWMEM available.

Using x86 segment limits to approximate NX protection

Zone PFN ranges:

  DMA             0 ->    18432

  Normal      18432 ->    18432

  HighMem     18432 ->    18432

early_node_map[1] active PFN ranges

    0:        0 ->    18432

ACPI in unprivileged domain disabled

Detected 2784.390 MHz processor.

Built 1 zonelists.  Total pages: 18288

Kernel command line: root=/dev/VolGroup00/LogVol00 4

Enabling fast FPU save and restore... done.

Enabling unmasked SIMD FPU exception support... done.

Initializing CPU#0

CPU 0 irqstacks, hard=c136c000 soft=c134c000

PID hash table entries: 512 (order: 9, 2048 bytes)

Xen reported: 2784.310 MHz processor.

Console: colour dummy device 80x25

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Software IO TLB disabled

vmalloc area: c5000000-f4ffe000, maxmem 2d7fe000

Memory: 60372k/73728k available (2071k kernel code, 5096k reserved, 1080k
data, 188k init, 0k highmem)

virtual kernel memory layout:

    fixmap  : 0xf5315000 - 0xf57fe000   (5028 kB)

    pkmap   : 0xf5000000 - 0xf5200000   (2048 kB)

    vmalloc : 0xc5000000 - 0xf4ffe000   ( 767 MB)

    lowmem  : 0xc0000000 - 0xc4800000   (  72 MB)

      .init : 0xc1319000 - 0xc1348000   ( 188 kB)

      .data : 0xc1205e6e - 0xc1313fd4   (1080 kB)

      .text : 0xc1000000 - 0xc1205e6e   (2071 kB)

Checking if this processor honours the WP bit even in supervisor mode... Ok.

Calibrating delay using timer specific routine.. 5572.51 BogoMIPS
(lpj=11145020)

Security Framework v1.0.0 initialized

SELinux:  Initializing.

selinux_register_security:  Registering secondary module capability

Capability LSM initialized as secondary

Mount-cache hash table entries: 512

CPU: Trace cache: 12K uops, L1 D cache: 8K

CPU: L2 cache: 512K

Checking ''hlt'' instruction... OK.

SMP alternatives: switching to UP code

Freeing SMP alternatives: 13k freed

Brought up 1 CPUs

NET: Registered protocol family 16

Brought up 1 CPUs

PCI: Fatal: No config space access function found

PCI: setting up Xen PCI frontend stub

Setting up standard PCI resources

ACPI: Interpreter disabled.

Linux Plug and Play Support v0.97 (c) Adam Belay

pnp: PnP ACPI: disabled

xen_mem: Initialising balloon driver.

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

PCI: System does not support PCI

PCI: System does not support PCI

NetLabel: Initializing

NetLabel:  domain hash size = 128

NetLabel:  protocols = UNLABELED CIPSOv4

NetLabel:  unlabeled traffic allowed by default

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 4096 (order: 3, 49152 bytes)

TCP bind hash table entries: 4096 (order: 3, 32768 bytes)

TCP: Hash tables configured (established 4096 bind 4096)

TCP reno registered

audit: initializing netlink socket (disabled)

audit(1228851551.569:1): initialized

VFS: Disk quotas dquot_6.5.1

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

ksign: Installing public key data

Loading keyring

io scheduler noop registered

io scheduler anticipatory registered

io scheduler deadline registered

io scheduler cfq registered (default)

pci_hotplug: PCI Hot Plug PCI Core version: 0.5

rtc: IRQ 8 is not free.

Non-volatile memory driver v1.2

Linux agpgart interface v0.102 (c) Dave Jones

RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize

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

Xen virtual console successfully installed as xvc0

Linux version 2.6.21.7-5.fc8xen (mockbuild@xenbuilder2.fedora.redhat.com)
(gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Thu Aug 7 12:44:49
EDT 2008

BIOS-provided physical RAM map:

sanitize start

sanitize bail 0

copy_e820_map() start: 0000000000000000 size: 0000000004800000 end:
0000000004800000 type: 1

 Xen: 0000000000000000 - 0000000004800000 (usable)

0MB HIGHMEM available.

72MB LOWMEM available.

Using x86 segment limits to approximate NX protection

Zone PFN ranges:

  DMA             0 ->    18432

  Normal      18432 ->    18432

  HighMem     18432 ->    18432

early_node_map[1] active PFN ranges

    0:        0 ->    18432

ACPI in unprivileged domain disabled

Detected 2784.390 MHz processor.

Built 1 zonelists.  Total pages: 18288

Kernel command line: root=/dev/VolGroup00/LogVol00 4

Enabling fast FPU save and restore... done.

Enabling unmasked SIMD FPU exception support... done.

Initializing CPU#0

CPU 0 irqstacks, hard=c136c000 soft=c134c000

PID hash table entries: 512 (order: 9, 2048 bytes)

Xen reported: 2784.310 MHz processor.

Console: colour dummy device 80x25

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Software IO TLB disabled

vmalloc area: c5000000-f4ffe000, maxmem 2d7fe000

Memory: 60372k/73728k available (2071k kernel code, 5096k reserved, 1080k
data, 188k init, 0k highmem)

virtual kernel memory layout:

    fixmap  : 0xf5315000 - 0xf57fe000   (5028 kB)

    pkmap   : 0xf5000000 - 0xf5200000   (2048 kB)

    vmalloc : 0xc5000000 - 0xf4ffe000   ( 767 MB)

    lowmem  : 0xc0000000 - 0xc4800000   (  72 MB)

      .init : 0xc1319000 - 0xc1348000   ( 188 kB)

      .data : 0xc1205e6e - 0xc1313fd4   (1080 kB)

      .text : 0xc1000000 - 0xc1205e6e   (2071 kB)

Checking if this processor honours the WP bit even in supervisor mode... Ok.

Calibrating delay using timer specific routine.. 5572.51 BogoMIPS
(lpj=11145020)

Security Framework v1.0.0 initialized

SELinux:  Initializing.

selinux_registe
Thanks & Regards,
Siddharth Wagh
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If something is so complicated that you can''t explain it in 10 seconds,
then
it''s probably not worth knowing anyway.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Bill McGonigle

2008-Dec-12 22:41 UTC

head link

Re: [Fedora-xen] unable to launch domU (FC 8)

Boy, that''s not much to go on, and the console often fails to capture 
all output, but:

On 2008-12-12 10:11 AM, Siddharth Wagh wrote:> Linux version 2.6.21.7-5.fc8xen
This is the latest f8 xen kernel (at least that my f8 machine has) - 
have you tried booting an earlier kernel in pygrub?

For some reason I don''t fully understand kernel-xen updates often fail 
to include xenblk and xennet modules in the initrd and leave the domU 
unable to find its root disk.

Something like:

mkinitrd  -v -f --with=xennet --with=xenblk initrd-`uname -r`.img `uname 
-r`

with the correct versions will get you going again if this is the case.

Also make sure the menu.lst entry isn''t setup for Dom0 after the
update,
I''ve seen that too (i.e. xen kernel, linux kernel as a module).

-Bill

-- 
Bill McGonigle, Owner           Work: 603.448.4440
BFC Computing, LLC              Home: 603.448.1668
bill@bfccomputing.com           Cell: 603.252.2606
http://www.bfccomputing.com/    Page: 603.442.1833
Blog: http://blog.bfccomputing.com/
VCard: http://bfccomputing.com/vcard/bill.vcf

Fedora xen - Dec 2008 - unable to launch domU (FC 8)

[Fedora-xen] unable to launch domU (FC 8)

Re: [Fedora-xen] unable to launch domU (FC 8)