xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: "Константин Алексеев" <kv.alekseev@gmail.com>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
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	[thread overview]
Message-ID: <CA712414.1F5B9%keir.xen@gmail.com> (raw)
In-Reply-To: <CAMb_DiSDrzT0e4xFufxBzEO6q7O4DCD3JXEOckgVSD3iY1BUpw@mail.gmail.com>

On 17/08/2011 07:16, "Константин Алексеев" <kv.alekseev@gmail.com> wrote:

> 2011/8/17 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:
>> 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

      reply	other threads:[~2011-08-17  6:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16  8:27 with kernel's option 'nosmp', dom0 does not init LSI Logic / Symbios Logic SAS1064ET Константин Алексеев
2011-08-17  2:14 ` Konrad Rzeszutek Wilk
2011-08-17  5:28   ` Константин Алексеев
     [not found]   ` <CAMb_DiRz4ZTdBNH5br0icKqEk9MDURuOhpdJbdS4YxS2mkgVUg@mail.gmail.com>
2011-08-17  5:29     ` Konrad Rzeszutek Wilk
2011-08-17  6:16       ` Константин Алексеев
2011-08-17  6:53         ` Keir Fraser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA712414.1F5B9%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kv.alekseev@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).