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/
Home Products Support Community News


[Xen-users] trying to boot dom0 kernel: nothing happens

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] trying to boot dom0 kernel: nothing happens
From: John Bucy <bucy@xxxxxxxxx>
Date: Mon, 06 Jun 2005 19:22:18 -0400
Delivery-date: Tue, 07 Jun 2005 10:39:30 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I'm trying to boot the 2.0.6 binary distribution on an SMP dell box.
The dom0 is a debian/sarge installation that's maybe 2 months
out-of-date. Not knowing otherwise, I suspect that SMP/ACPI is the
source of trouble here.  I've tried various permutations of the boot
options for both xen and the dom0 kernel and they don't seem to have
much effect.  In particular, nosmp/acpi=off doesn't seem to prevent it
from parsing the bios tables, etc.

Here's the output:

  Booting 'Xen'

kernel /xen-2.0.6.gz dom0_mem=64000 com1=9600,8n1 console=com1 acpi=off
sync_console nosmp
   [Multiboot-elf, <0x100000:0x3f050:0x35fb0>, shtab=0x175078,
root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83
module /vmlinuz-2.6-xen0 root=/dev/sda3 console=ttyS0
   [Multiboot-module @ 0x176000, 0x4308cc bytes]

 __  __            ____    ___   __
 \ \/ /___ _ __   |___ \  / _ \ / /_
  \  // _ \ '_ \    __) || | | | '_ \
  /  \  __/ | | |  / __/ | |_| | (_) |
 /_/\_\___|_| |_| |_____(_)___(_)___/

 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

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 00000000000a0000 (usable)
(XEN)  00000000000f0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000017ffe000 (usable)
(XEN)  0000000017ffe000 - 0000000018000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee10000 (reserved)
(XEN)  00000000ffe00000 - 0000000100000000 (reserved)
(XEN) System RAM: 383MB (392824kB)
(XEN) Xen heap: 10MB (10784kB)
(XEN) CPU0: Before vendor init, caps: 0383fbff 00000000 00000000, vendor
= 0
(XEN) CPU caps: 0383fbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000fe710
(XEN) ACPI: RSDP (v000 DELL                                      ) @
(XEN) ACPI: RSDT (v001 DELL    WS 410  0x00000002 ASL  0x00000061) @
(XEN) ACPI: FADT (v001 DELL    WS 410  0x00000002 ASL  0x00000061) @
(XEN) ACPI: MADT (v001 DELL    WS 410  0x00000002 ASL  0x00000061) @
(XEN) ACPI: DSDT (v001   DELL    dt_ex 0x00001000 MSFT 0x0100000b) @
(XEN) ACPI: Local APIC address 0xfee00000

after this, nothing happens.

Also, the vga console doesn't seem to work for me at all -- after grub
jumps into xen, the monitor on the box goes black and says that the
signal is out of spec.  If I have console=com1,vga, I get the xen banner
on serial at the same time as the vga goes dark.  The box is in a lab
far away from my desk so I only really care about serial.

Any ideas?


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>