xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xl vcpu-set crashes Dom0
Date: Mon, 28 Feb 2011 20:51:12 +0000	[thread overview]
Message-ID: <C991BB40.13F14%keir.xen@gmail.com> (raw)
In-Reply-To: <4D6BDA07.2010707@amd.com>

On 28/02/2011 17:23, "Andre Przywara" <andre.przywara@amd.com> wrote:

> Hi,
> 
> as mentioned earlier today I had some issues with patch 22934, which
> decreases the number of vCPUs for Dom0 in case of cpupool-numa-split.
> I now found that this is not directly related to this patch, as it
> triggers also with "xl vcpu-set". So far I tried the following combinations:
> c/s 22956 on a machine with 48 physical CPUs:
> not restricted dom0:
> xl vcpu-set 0 6  => crashes
>          xl vcpu-set 0 47 => crashes
> dom0_max_vcpus=6
> xl vcpu-set 0 5  => crashes
>          xm vcpu-set 0 5  => crashes
> 
> The only message I get is:
> root@dosorca:~# xm vcpu-set 0 5
> (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

Dom0 has oopsed. If you have a synchronous log of dmesg (e.g., via serial)
then you should be able to get an oops message and backtrace from dom0
kernel. My first guess would be this is a bug in the kernel's handling of
cpu hotplug requests via xenstore.

 -- Keir

> Debugging turned out that for instance the libxl_set_vcpuonline()
> returns without an error, but the machine then crashes afterwards.
> 
> Can someone reproduce this? Any ideas?
> 
> Regards,
> Andre.

      reply	other threads:[~2011-02-28 20:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 17:23 xl vcpu-set crashes Dom0 Andre Przywara
2011-02-28 20:51 ` 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=C991BB40.13F14%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=andre.przywara@amd.com \
    --cc=juergen.gross@ts.fujitsu.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).