From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christopher S. Aker" Subject: Re: BUG at domain.c:144 Date: Thu, 7 Apr 2005 14:39:28 -0500 Message-ID: <000a01c53ba9$83f43a60$0201a8c0@hawk> References: <002e01c53a7e$a25cd3d0$0201a8c0@hawk> <81f8f6c8aca9491c3f6a5b78da0ade37@cl.cam.ac.uk> <000901c53ba3$1c87ff70$0201a8c0@hawk> <2170d729d4e6a1c56f87985558551774@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Ian Pratt , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > What type of cpu does the non-working machine have? My guess would be > that it is exercising some start-of-day code path in Linux that is > doing something that is invalid on Xen. 2.66Ghz Xeons. It's a pretty standard, well-supported box (SuperMicro 6013P-i). Xen-.0.5 works fine on this machine. -Chris