[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Xen failing to boot under Debian Etch. (FATAL TRAP)


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "David Morris" <david.morris@xxxxxxxxxx>
  • Date: Fri, 7 Sep 2007 11:48:21 -0700
  • Delivery-date: Fri, 07 Sep 2007 11:49:10 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcfxSzpG76/N5HbyT+e8yMlNfdUw7wANECHg
  • Thread-topic: [Xen-users] Xen failing to boot under Debian Etch. (FATAL TRAP)

Perhaps I'm confused by obtuse naming, but it looks to me that you are running 
AMD 64bit kernels and hypervisors on an Intel system. Is this a AMD vs Intel 
compatibility issue?

> -----Original Message-----
> From: James Ray [mailto:j.ray@xxxxxxxxxx]
> Sent: Friday, September 07, 2007 2:06 AM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Xen failing to boot under Debian Etch. 
> (FATAL TRAP)
> 
> 
> Hi,
>       Running xen on a Debian Etch platform and about every 1 
> in 10 boots I
> am getting the following error:
> (XEN) ************************************
> (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN 
> INTERRUPT
> CONTEXT.
> (XEN) System shutting down -- need manual reset.
> (XEN) ************************************
> 
> (I have attached a file with the full output also of an OK boot and a
> failed one also).
> 
> This is a Quad-Core, Dual CPU system currently running with 4Gb of RAM
> with a Intel S5000PAL server motherboard. I have tried tweaking around
> the APIC options to be bigsmp to no help at all. I am kind of 
> at a loss
> right now as to how to progress. I have upgraded the BIOS to 
> the latest
> revision to no avail also.
> 
> Here are the xen package versions from my system:
> # dpkg -l | egrep '(\||xen)'
> | 
> Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-
> installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> uppercase=bad)
> ||/ Name                                Version
> Description
> ii  linux-image-2.6-xen-amd64           2.6.18+6etch2
> Linux kernel 2.6 image on AMD64
> ii  linux-image-2.6.18-4-xen-amd64      2.6.18.dfsg.1-12etch2
> Linux 2.6.18 image on AMD64
> ii  linux-image-2.6.18-5-xen-amd64      2.6.18.dfsg.1-13etch2
> Linux 2.6.18 image on AMD64
> ii  linux-modules-2.6.18-4-xen-amd64    2.6.18.dfsg.1-12etch2
> Linux 2.6.18 modules on AMD64
> ii  linux-modules-2.6.18-5-xen-amd64    2.6.18.dfsg.1-13etch2
> Linux 2.6.18 modules on AMD64
> ii  xen-hypervisor-3.0.3-1-amd64        3.0.3-0-2
> The Xen Hypervisor on AMD64
> ii  xen-ioemu-3.0.3-1                   3.0.3-0-2
> XEN administrative tools
> ii  xen-linux-system-2.6.18-4-xen-amd64 2.6.18.dfsg.1-12etch2
> XEN system with Linux 2.6.18 image on AMD64
> ii  xen-tools                           2.8-2
> Tools to manage debian XEN virtual servers
> ii  xen-utils-3.0.3-1                   3.0.3-0-2
> XEN administrative tools
> ii  xen-utils-common                    3.0.3-0-2
> XEN administrative tools - common files
> 
> And here is my grub boot section:
> title           Xen 3.0.3-1-amd64 / Debian GNU/Linux, kernel
> 2.6.18-5-xen-amd64
> root            (hd0,0)
> kernel          /xen-3.0.3-1-amd64.gz com2=19200,8n1 console=com2
> module          /vmlinuz-2.6.18-5-xen-amd64 
> root=/dev/mapper/hornet-root
> ro console=ttyS1,19200 console=tty0
> module          /initrd.img-2.6.18-5-xen-amd64
> 
> If I can help with any further information please let me know. Anyone
> any ideas on how to fix this problem?
> 
> (I will start running the Intel Platform Test Suite to check 
> its not the
> hardware, but I doubt it is since this happens the same on 
> two identical
> boxes)
> 
> -- 
> James Ray.                          <j.ray@xxxxxxxxxx>
> Computing Services
> Queen Mary, University of London
> 

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.