From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: with kernel's option 'nosmp', dom0 does not init LSI Logic / Symbios Logic SAS1064ET Date: Wed, 17 Aug 2011 07:53:56 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable 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: =?windows-1251?B?yu7t8fLg7fLo7Q==?= =?windows-1251?B?IMDr5erx5eXi?= , Konrad Rzeszutek Wilk Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 17/08/2011 07:16, "=CA=EE=ED=F1=F2=E0=ED=F2=E8=ED =C0=EB=E5=EA=F1=E5=E5=E2" wrote: > 2011/8/17 Konrad Rzeszutek Wilk : >> Did you follow also the suggestions in the bugzilla from Ian (about dom0= _..) >> ? >> Did that fix the issue? >=20 > If you mean suggestions from Ian in debian bug report, then yes, > I use dom0_max_vcpus=3D1 and everything works well. > Ian asked to test this bug with the latest kernel and report it. > That's what I'm doing It's really an unsupported configuration. If you want to limit dom0 vcpus then dom0_max_vcpus=3D on Xen command line is the correct way. Specifying nosmp causes the machine to boot up in a legacy configuration which we do not test, and is likely to cause mismatches in expectations between dom0 an= d Xen. There's no good reason to specify it for general use. -- Keir