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

RE: [Xen-users] Xen on K6 processors

  • To: "Florian Fainelli" <florian@xxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Tue, 13 Feb 2007 11:08:59 +0100
  • Delivery-date: Tue, 13 Feb 2007 10:15:12 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcdO7RbIRLojz/hkQ46F+Vob9PQR0wAaRwlw
  • Thread-topic: [Xen-users] Xen on K6 processors


> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Florian Fainelli
> Sent: 12 February 2007 21:12
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Xen on K6 processors
> Hi all,
> I am currently trying to make Xen work on a Cobalt Raq4 box. 
> The hypervisor as 
> well as the dom0 kernel works, unfortunately, it silently 
> crashes and reboot 
> back to cobalt-rom.
> I read somewhere that Xen is not compatible with non i686 
> capable processors, 
> is that true, and if so, how could we adress this limitation ?

Whilst the "not compatible with non-i686 processor" may well be true,
that's certainly not the reason for your crashes - as the K6 is a i686
compatible processor. 

Do you by any chance have a serial port - in which case you should add
"console=com1 com1=115200,8n1" to the kernel line in grub.conf. (that's
the line with xen.gz on it).  
If not, perhaps you can get more info with the "noreboot" option on the
kernel line for Xen - that way it won't just get back to the boot-rom
when it crashes. 

Adding "sync_console" may also help, particularly if you're using serial
port (as will "noreboot").

> Thank you very much in advance for your answer.
> Best regards, Florian

Xen-users mailing list



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