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

Re: [Xen-devel] with kernel's option 'nosmp', dom0 does not init LSI Log

To: Константин Алексеев <kv.alekseev@xxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] with kernel's option 'nosmp', dom0 does not init LSI Logic / Symbios Logic SAS1064ET
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Wed, 17 Aug 2011 07:53:56 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Aug 2011 23:55:04 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=w50dTpjfNJoRZRfbJ1scMKW8wItg+NBtw5mFR77IpRg=; b=HWOj+kMKDvIXUszAYlPlxFKWZVpDGp1GNxdqhqARSEd/XybFy8QSEJL796aq/Ik2rr a2ZXTKdN5eg3xmV6KUxUsoBPl9NQF0jItSjTJijYW+uSni3aLkNr5Qv8uUusw1fzS8ib 9hKJq7b+fea0tbgM7f1tUGZLF7XYqEBfMfdMI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAMb_DiSDrzT0e4xFufxBzEO6q7O4DCD3JXEOckgVSD3iY1BUpw@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acxcqm7MvWOyDB8Kp0qkdHN6UTBBfQ==
Thread-topic: [Xen-devel] with kernel's option 'nosmp', dom0 does not init LSI Logic / Symbios Logic SAS1064ET
User-agent: Microsoft-Entourage/12.30.0.110427
On 17/08/2011 07:16, "Константин Алексеев" <kv.alekseev@xxxxxxxxx> wrote:

> 2011/8/17 Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>:
>> Did you follow also the suggestions in the bugzilla from Ian (about dom0_..)
>> ?
>> Did that fix the issue?
> 
> If you mean suggestions from Ian in debian bug report, then yes,
> I use dom0_max_vcpus=1 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= 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 and
Xen. There's no good reason to specify it for general use.

 -- Keir



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

<Prev in Thread] Current Thread [Next in Thread>