i reinstalled the tools, this is from xm dmesg
(the 2 cpu thing is very probably hyperthreading. i'll turn it off in
bios if it is needed)
stijn
__ __ ____ ___
\ \/ /___ _ __ |___ \ / _ \
\ // _ \ '_ \ __) || | | |
/ \ __/ | | | / __/ | |_| |
/_/\_\___|_| |_| |_____(_)___/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 2.0 (root@xxxxxxxxxx) (gcc version 3.2.3 20030502 (Red
Hat Linux 3.2.3-42)) Thu Jan 6 14:28:31 CET 2005
Latest ChangeSet: information unavailable
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e6000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000003ef2fc00 (usable)
(XEN) 000000003ef2fc00 - 000000003ef30000 (ACPI NVS)
(XEN) 000000003ef30000 - 000000003ef40000 (ACPI data)
(XEN) 000000003ef40000 - 000000003eff0000 (ACPI NVS)
(XEN) 000000003eff0000 - 000000003f000000 (reserved)
(XEN) 00000000fecf0000 - 00000000fecf1000 (reserved)
(XEN) 00000000fed20000 - 00000000feda0000 (reserved)
(XEN) System RAM: 1006MB (1030968kB)
(XEN) Xen heap: 10MB (10756kB)
(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 000ff780
(XEN) ACPI: RSDP (v000 ACPIAM ) @ 0x000f61b0
(XEN) ACPI: RSDT (v001 INTEL D865GLC 0x20040622 MSFT 0x00000097) @ 0x3ef30000
(XEN) ACPI: FADT (v002 INTEL D865GLC 0x20040622 MSFT 0x00000097) @ 0x3ef30200
(XEN) ACPI: MADT (v001 INTEL D865GLC 0x20040622 MSFT 0x00000097) @ 0x3ef30300
(XEN) ACPI: ASF! (v016 LEGEND I865PASF 0x00000001 MSFT 0x0100000d) @ 0x3ef345b0
(XEN) ACPI: TCPA (v001 INTEL TBLOEMID 0x00000001 MSFT 0x00000097) @ 0x3ef34649
(XEN) ACPI: WDDT (v001 INTEL OEMWDDT 0x00000001 MSFT 0x0100000d) @ 0x3ef3467d
(XEN) ACPI: DSDT (v001 INTEL D865GLC 0x00000001 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] enabled)
(XEN) Processor #1 Unknown CPU [15:3] APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) Using ACPI for processor (LAPIC) configuration information
(XEN) Intel MultiProcessor Specification v1.4
(XEN) Virtual Wire compatibility mode.
(XEN) OEM ID: Product ID: Springdale-G APIC at: 0xFEE00000
(XEN) I/O APIC #2 Version 32 at 0xFEC00000.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Processors: 2
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 2992.634 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) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) masked ExtINT on CPU#1
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) CPU1: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0
(XEN) CPU#1: Physical ID: 0, Logical ID: 1
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU1 has booted.
(XEN) Total of 2 processors activated.
(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 2992.5762 MHz.
(XEN) ..... Bus speed is 199.5050 MHz.
(XEN) ..... bus_scale = 0x0000CC4F
(XEN) checking TSC synchronization across CPUs: passed.
(XEN) Time init:
(XEN) .... System Time: 10701084ns
(XEN) .... cpu_freq: 00000000:B25FF8F4
(XEN) .... scale: 00000001:562C68A6
(XEN) .... Wall Clock: 1105035408s 120000us
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xf0031, 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,P0) -> 18
(XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17
(XEN) PCI->APIC IRQ transform: (B1,I8,P0) -> 20
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
'GUEST_OS=linux,GUEST_VER=2.4,XEN_VER=2.0,VIRT_BASE=0xC0000000'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 00c00000->00f0991c
(XEN) Initrd image: 00f0a000->016da000
(XEN) Dom0 alloc.: 01800000->21800000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c04528d4
(XEN) Init. ramdisk: c0453000->c0c23000
(XEN) Phys-Mach map: c0c23000->c0ca3000
(XEN) Page tables: c0ca3000->c0ca8000
(XEN) Start info: c0ca8000->c0ca9000
(XEN) Boot stack: c0ca9000->c0caa000
(XEN) TOTAL: c0000000->c1000000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Scrubbing DOM0 RAM: ......done.
(XEN) Initrd len 0x7d0000, start at 0xc0453000
(XEN) Scrubbing Free RAM: ...........done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen).
On Thu, 6 Jan 2005 16:45:52 +0000, Andrew Warfield
<andrew.warfield@xxxxxxxxx> wrote:
> If you are working out of the unstable tree you will need to reinstall
> the tools if you haven't done so since the end of last week. We've
> added a switch for control messages below xend, and the error looks a
> bit like it isn't running.
>
> a.
>
> On Thu, 6 Jan 2005 17:36:30 +0100, Stijn De Weirdt
> <stijn.deweirdt@xxxxxxxxx> wrote:
> > no output from xm dmesg. so something else must be wrong (and probably
> > my fault ;)
> > output from xm dmesg after xend start
> >
> > (111, 'Connection refused')
> > Error: Error connecting to xend, is xend running?
> >
> > no so good
> >
> > /var/log/xend.log
> > [2005-01-06 17:00:50 xend] INFO (SrvDaemon:607) Xend Daemon started
> >
> > /var/log/xend-debug.log
> > xu_notifier_new()
> > error connecting to xcs(ctrl)! (111)
> > Traceback (most recent call last):
> > File "/usr/sbin/xend", line 121, in ?
> > sys.exit(main())
> > File "/usr/sbin/xend", line 107, in main
> > return daemon.start()
> > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py",
> > line 522, in start
> > self.run()
> > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py",
> > line 610, in run
> > self.listenNotifier()
> > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py",
> > line 629, in listenNotifier
> > p.startListening()
> > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py",
> > line 90, in startListening
> > self._connectToProtocol()
> > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py",
> > line 108, in _connectToProtocol
> > self.startReading()
> > File "/usr/lib/python2.2/site-packages/twisted/internet/abstract.py",
> > line 205
> > , in startReading
> > self.reactor.addReader(self)
> > File "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor.py",
> > line
> > 89, in addReader
> > self._updateRegistration(fd)
> > File "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor.py",
> > line
> > 52, in _updateRegistration
> > poller.unregister(fd)
> > ValueError: file descriptor cannot be a negative integer (-1)
> >
> > (i tried the writing to /dev/mem, and as ian guessed, it doesn't solve it)
> >
> > stijn
> >
> > On Thu, 6 Jan 2005 08:51:00 -0700 (MST), Ronald G. Minnich
> > <rminnich@xxxxxxxx> wrote:
> > >
> > >
> > > On Thu, 6 Jan 2005, Ian Pratt wrote:
> > >
> > > > This might get you a stage further, but it will fail as soon as the
> > > > driver tries to access the frame bufffer via /dev/mem. We really need to
> > > > get to the bottom of whis this is failing on your system. Please can you
> > > > post the output of 'xm dmesg'.
> > >
> > > I should be clearer. What we do here is get vgabios into a file, and then
> > > tell our emulator to use the file as the 'C segment' but to use /dev/mem
> > > for everything else. In that way we init the physical hardware. X11 ought
> > > to do this but I do not know if they support the option it at this point.
> > > It's easy: our code is just mods to the X11 emulator.
> > >
> > > Is there any easy way to dump the mfn's for a guest -- that would tell us
> > > right away what is going on -- we should see pfn 0xc0 map to mfn
> > > 0xc0, i.e. dom 0 physical c0000 maps to vga bios at machine 0xc0000.
> > >
> > > This is where having /proc/sys/xen/dom/#/{mem,mfn,etc} would be VERY handy
> > > :-)
> > >
> > > ron
> > >
> >
> > -------------------------------------------------------
> > The SF.Net email is sponsored by: Beat the post-holiday blues
> > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> >
>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home