WARNING - OLD ARCHIVES

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

xen-devel

[Xen-devel] can't boot 32-bit SLES10 HVMs since c/s 14436 was introduced

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] can't boot 32-bit SLES10 HVMs since c/s 14436 was introduced
From: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>
Date: Tue, 1 May 2007 13:49:54 -0400
Cc: dexuan.cui@xxxxxxxxx
Delivery-date: Tue, 01 May 2007 10:48:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C24D3B74.601B%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C24D2C49.6009%Keir.Fraser@xxxxxxxxxxxx> <C24D3B74.601B%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceCBQEa5MKKwplxT9CnThPnChkZEgAgSf91AAJCnZMCOHYCcA==
Thread-topic: can't boot 32-bit SLES10 HVMs since c/s 14436 was introduced

I cannot boot 32-bit SLES10 HVMs, SMP nor PAE, on x86_64 SLES10 xen on Unisys ES7000/one with Intel processors.  I initially tried with HVM memory sizes of 2gb and 16gb, but when I give the HVMs only 512mb, they still do not boot.  I have run both with the ES7000 configured as 8x 32gb and 16x 64gb.  The HVMs either hang in the graphical blue SUSE Linux screen or get this kernel panic: Badness in smp_call_function at arch/i386/kernel/smp.c:595.   

 

At Keir’s suggestion, I used a binary search method to narrow down changesets, and after building and testing multiple changesets I was able to determine that c/s 14436 introduces the problem. 

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

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