WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] cannot boot any domU

Hi,

> Sorry, no answers, only questions (and I apologize if you've answered
> this and I missed it):
> 
> Have your tried the live CD demo on the same hardware?
> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads.html

No. That is a good idea. I will do that next week.

> 
> After you reboot, is there anything meaningful in /var/log/xend.log or
> /var/log/xend-debug.log?

/var/log/xend.log has this for each attempt:

[2005-08-04 08:03:04 xend] INFO (XendRoot:112) EVENT> xend.start 0
[2005-08-04 08:07:59 xend] INFO (SrvDaemon:610) Xend Daemon started

/var/log/xend-debug.log has this:

[root@garlic ~]# cat /var/log/xend-debug.log
xfrd: error while loading shared libraries: libcurl.so.2:
cannot open shared object file: No such file or directory
network start bridge=xen-br0 netdev=eth0 antispoof=no

Is the libcurl error fatal?

I have curl-7.12.1-1 and curl-devel-7.12.1-1 RPMs installed
and they provide 

[root@garlic ~]# rpm -q -l curl-7.12.1-1 | grep libcurl
/usr/lib/libcurl.so.3
/usr/lib/libcurl.so.3.0.0

I did the quick and (quite) dirty fix of

ln -s /usr/lib/libcurl.so.3 /usr/lib/libcurl.so.2

but it didn't help with booting a domU...still hangs
immediately.

Scott

> 
> 
> On 8/5/05, Scott Koranda <skoranda@xxxxxxxxxxxxxxxxxxxx> wrote:
> > > On Friday 05 August 2005 01:42, Marcus Brown wrote:
> > >
> > > >
> > > > I'm interested in how 'immediate' this is as I suspect you have a
> > > > problem with your initrd. You might be able to see something with
> > > >
> > > > xm create xmfc4 && xm console n
> > > >
> > > > (You need to know what the next console number will be, of course!:))
> > >
> > > you also can "xm create -c xmfc4 " which starts the domain and immediatly
> > > attaches the console, so you'll see the entire boot process.
> > >
> > 
> > I have been using the syntax "xm create -c" from the beginning
> > since I was following the manual (in particular the ttylinux
> > example). Unfortunately all I see (in its entirety) is this:
> > 
> > [root@garlic xen]# xm create -c xmfc4
> > Using config file "xmfc4".
> > 
> > As soon as that single line is printed the hardware hangs up.
> > I do not think Xen even gets started enough to print anything
> > to a console.
> > 
> > The same is true when I try the ttylinux example. I only get
> > that single line and then the hardware hangs.
> > 
> > By the way, before I try starting a domU I see this:
> > 
> > [root@garlic ~]# xm info
> > system                 : Linux
> > host                   : garlic.phys.uwm.edu
> > release                : 2.6.11.10-xen0
> > version                : #1 Sun May 22 11:38:50 BST 2005
> > machine                : i686
> > cores                  : 0
> > hyperthreads_per_core  : 2
> > cpu_mhz                : 3000
> > memory                 : 1015
> > free_memory            : 870
> > [root@garlic ~]# xm list
> > Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> > Domain-0           0      123    0  r----      8.6
> > [root@garlic ~]# xm dmesg
> > ERROR: cannot use unconfigured serial port COM1
> >  __  __            ____    ___   __
> >  \ \/ /___ _ __   |___ \  / _ \ / /_
> >   \  // _ \ '_ \    __) || | | | '_ \
> >   /  \  __/ | | |  / __/ | |_| | (_) |
> >  /_/\_\___|_| |_| |_____(_)___(_)___/
> > 
> >  http://www.cl.cam.ac.uk/netos/xen
> >  University of Cambridge Computer Laboratory
> > 
> >  Xen version 2.0.6 (xenod@xxxxxxxxxxxx) (gcc version 3.3.3
> > 20040412 (Red Hat Linux 3.3.3-7)) Sun May 22 11:31:19 BST 2005
> >  Latest ChangeSet: 2005/05/22 11:30:28 1.1720
> > 42905f44tK_V2k-UIPH1EmnW4Bg6Dg
> > 
> > (XEN) Physical RAM map:
> > (XEN)  0000000000000000 - 000000000009fc00 (usable)
> > (XEN)  000000000009fc00 - 00000000000a0000 (reserved)
> > (XEN)  00000000000f0000 - 0000000000100000 (reserved)
> > (XEN)  0000000000100000 - 000000003f7f0000 (usable)
> > (XEN)  000000003f7f0000 - 000000003f7f8000 (ACPI data)
> > (XEN)  000000003f7f8000 - 000000003f800000 (ACPI NVS)
> > (XEN)  00000000fec00000 - 00000000fec01000 (reserved)
> > (XEN)  00000000fee00000 - 00000000fee01000 (reserved)
> > (XEN)  00000000fff00000 - 0000000100000000 (reserved)
> > (XEN) System RAM: 1015MB (1039932kB)
> > (XEN) Xen heap: 10MB (10764kB)
> > (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000
> > 00000000, vendor = 0
> > (XEN) CPU#0: Physical ID: 0, Logical ID: 0
> > (XEN) CPU caps: bfebfbff 00000000 00000000 00000000
> > (XEN) found SMP MP-table at 000fc0f0
> > (XEN) ACPI: RSDP (v000 AMI
> > ) @ 0x000fa3b0
> > (XEN) ACPI: RSDT (v001 AMIINT INTEL865 0x00000010 MSFT
> > 0x00000097) @ 0x3f7f0000
> > (XEN) ACPI: FADT (v001 AMIINT INTEL865 0x00000011 MSFT
> > 0x00000097) @ 0x3f7f0030
> > (XEN) ACPI: MADT (v001 AMIINT INTEL865 0x00000009 MSFT
> > 0x00000097) @ 0x3f7f00c0
> > (XEN) ACPI: DSDT (v001  INTEL    I865G 0x00001000 MSFT
> > 0x0100000d) @ 0x00000000
> > (XEN) ACPI: Local APIC address 0xfee00000
> > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> > (XEN) Processor #0 Unknown CPU [15:3] APIC version 20
> > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled)
> > (XEN) Using ACPI for processor (LAPIC) configuration
> > information
> > (XEN) Intel MultiProcessor Specification v1.4
> > (XEN)     Virtual Wire compatibility mode.
> > (XEN) OEM ID: INTEL    Product ID: I865G/GE/PE  APIC at:
> > 0xFEE00000
> > (XEN) I/O APIC #2 Version 32 at 0xFEC00000.
> > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
> > (XEN) Processors: 1
> > (XEN) Using scheduler: Borrowed Virtual Time (bvt)
> > (XEN) Initializing CPU#0
> > (XEN) Detected 3000.191 MHz processor.
> > (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000
> > 00000000, vendor = 0
> > (XEN) CPU#0: Physical ID: 0, Logical ID: 0
> > (XEN) CPU caps: bfebfbff 00000000 00000000 00000000
> > (XEN) CPU0 booted
> > (XEN) enabled ExtINT on CPU#0
> > (XEN) ESR value before enabling vector: 00000000
> > (XEN) ESR value after enabling vector: 00000000
> > (XEN) Error: only one processor found.
> > (XEN) ENABLING IO-APIC IRQs
> > (XEN) Setting 2 in the phys_id_present_map
> > (XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
> > (XEN) init IO_APIC IRQs
> > (XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
> > (XEN) Using local APIC timer interrupts.
> > (XEN) Calibrating APIC timer for CPU0...
> > (XEN) ..... CPU speed is 3000.1452 MHz.
> > (XEN) ..... Bus speed is 200.0095 MHz.
> > (XEN) ..... bus_scale = 0x0000CCD7
> > (XEN) Time init:
> > (XEN) .... System Time: 10735130ns
> > (XEN) .... cpu_freq:    00000000:B2D34AD4
> > (XEN) .... scale:       00000001:554FC001
> > (XEN) .... Wall Clock:  1123248619s 120000us
> > (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=1
> > (XEN) PCI: Using configuration type 1
> > (XEN) PCI: Probing PCI hardware
> > (XEN) PCI: Probing PCI hardware (bus 00)
> > (XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
> > (XEN) Transparent bridge - PCI device 8086:244e
> > (XEN) PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0
> > (XEN) PCI->APIC IRQ transform: (B0,I2,P0) -> 16
> > (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16
> > (XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19
> > (XEN) PCI->APIC IRQ transform: (B0,I29,P2) -> 18
> > (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16
> > (XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23
> > (XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18
> > (XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17
> > (XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17
> > (XEN) PCI->APIC IRQ transform: (B1,I6,P0) -> 20
> > (XEN) mtrr: v2.0 (20020519)
> > (XEN) *** LOADING DOMAIN 0 ***
> > (XEN) Xen-ELF header found:
> > 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'
> > (XEN) PHYSICAL MEMORY ARRANGEMENT:
> > (XEN)  Kernel image:  00c00000->010308cc
> > (XEN)  Initrd image:  01031000->010c2e00
> > (XEN)  Dom0 alloc.:   01400000->09400000
> > (XEN) VIRTUAL MEMORY ARRANGEMENT:
> > (XEN)  Loaded kernel: c0100000->c055eac4
> > (XEN)  Init. ramdisk: c055f000->c05f0e00
> > (XEN)  Phys-Mach map: c05f1000->c0611000
> > (XEN)  Page tables:   c0611000->c0614000
> > (XEN)  Start info:    c0614000->c0615000
> > (XEN)  Boot stack:    c0615000->c0616000
> > (XEN)  TOTAL:         c0000000->c0800000
> > (XEN)  ENTRY ADDRESS: c0100000
> > (XEN) Scrubbing DOM0 RAM: ..done.
> > (XEN) Initrd len 0x91e00, start at 0xc055f000
> > (XEN) Scrubbing Free RAM: ...........done.
> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to
> > switch input to Xen).
> > 
> > 
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >

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