All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl Jones <lists@outervoid.net>
To: xen-devel@lists.xensource.com
Subject: Xen stable won't boot
Date: Sat, 02 Jul 2005 09:42:09 +1200	[thread overview]
Message-ID: <42C5B8B1.20009@outervoid.net> (raw)

Hi,

I have a couple of dual Xeon 3.0GHZ machines. Both have 4GB of memory. 
I'm trying to get them to boot Xen stable/2.0.6 (have tried 2.0.5 as well).

Because they are remote, getting error messages can be tricky.

When 'noreboot' is set in grubs conf, they stop after the 'scrubbing 
free RAM' message. If I remove the noreboot, I'm told a 'CPU trap' error 
occurs before it reboots, which I'm guessing is the CPU FATAL TRAP?

This thread 
http://lists.xensource.com/archives/html/xen-devel/2005-05/msg00510.html 
seems to be similar, but they are using xen 3.0-devel.

It's running CentOS 4 and boots up fine with a 2.6.9 (and 2.6.11.7 
vanilla) kernel.

Any help much appreciated. If there is anything other information I can 
provide, just let me know.

Thanks,

Carl

# lspci
00:00.0 Host bridge: Intel Corp. E7320 Memory Controller Hub (rev 0c)
00:02.0 PCI bridge: Intel Corp. E7525/E7520/E7320 PCI Express Port A 
(rev 0c)
00:03.0 PCI bridge: Intel Corp. E7525/E7520/E7320 PCI Express Port A1 
(rev 0c)
00:1c.0 PCI bridge: Intel Corp. 6300ESB 64-bit PCI-X Bridge (rev 02)
00:1d.0 USB Controller: Intel Corp. 6300ESB USB Universal Host 
Controller (rev 02)
00:1d.1 USB Controller: Intel Corp. 6300ESB USB Universal Host 
Controller (rev 02)
00:1d.4 System peripheral: Intel Corp. 6300ESB Watchdog Timer (rev 02)
00:1d.5 PIC: Intel Corp. 6300ESB I/O Advanced Programmable Interrupt 
Controller (rev 02)
00:1d.7 USB Controller: Intel Corp. 6300ESB USB2 Enhanced Host 
Controller (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 0a)
00:1f.0 ISA bridge: Intel Corp. 6300ESB LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corp. 6300ESB PATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 6300ESB SMBus Controller (rev 02)
03:03.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet 
Controller
03:04.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet 
Controller
04:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)

# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 4
model name      : Intel(R) Xeon(TM) CPU 3.00GHz
stepping        : 1
cpu MHz         : 3000.900
cache size      : 1024 KB
physical id     : 0
siblings        : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm pni 
monitor ds_cpl cid xtpr
bogomips        : 5914.62

from grub:

title Xen
         root (hd0,0)
         kernel /xen-2.0.6.gz dom0_mem=196608 noreboot
         module /vmlinuz-2.6.11.10-xen0 root=/dev/md1 ro console=tty0
         module /initrd-2.6.11.10-xen0.img

                 reply	other threads:[~2005-07-01 21:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42C5B8B1.20009@outervoid.net \
    --to=lists@outervoid.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.