From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Gorm Hansen Subject: Re: Crash with 3.0.3 on domain creation Date: Thu, 26 Oct 2006 13:08:17 +0200 Message-ID: <1161860897.2365.6.camel@localhost.localdomain> References: Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: 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: xen-devel List-Id: xen-devel@lists.xenproject.org On Thu, 2006-10-19 at 08:32 +0100, Keir Fraser wrote: > On 18/10/06 11:18 pm, "Jacob Gorm Hansen" wrote: > > > I have tried switching xen-3.0.2 compat. mode on and of in dom0 and > > domU, but that has zero effect. The guest kernel is a vanilla domU, > > compiled from the same xen tree as xen and domU. I have verified that I > > am not using stale .so versions or anything like that. xenstored and > > xenconsoled are both running. Things worked fine in xen 3.0.2. > > I can't imagine this will be hard to track down. Since it's in domctl() this > will only be triggerable from dom0. It'd just be nice to know whether the > Python tools can trigger this. Got back to this and found the problem: If xc_domain_max_vcpus() is not called before the domain gets build, Xen will crash when trying to test for the HVM guest bit in the hvm_guest() macro. Would it make sense to start out with one rather than no vcpus to prevent this crash? Jacob