From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: dom0 crash without any message Date: Mon, 3 Jun 2013 18:45:25 +0100 Message-ID: <51ACD635.7040904@citrix.com> References: <1370277458.24512.47.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: William Dauchy Cc: Ian Campbell , xen-devel List-Id: xen-devel@lists.xenproject.org On 03/06/13 18:38, William Dauchy wrote: > Hello > On Mon, Jun 3, 2013 at 6:37 PM, Ian Campbell wrote: >> earlyprintk=xen on the dom0 kernel command line might add something >> useful to the logs. > true, I forgot about that option. It's now crashing on "Max apic_id > exceeded!". Of course the boot continues with nolapic option. > Do you know how can I workaround that without nolapic option? > > -- > William You need to boot with dom0_max_vcpus=16 or so If I remember our internal tickets correctly, some PVops gets confused with more than 16 vcpus. ~Andrew