From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Only CPU0 active after ACPI S3, xen 4.1.3
Date: Fri, 30 Nov 2012 17:07:05 +0100 [thread overview]
Message-ID: <50B8D9A9.60502@invisiblethingslab.com> (raw)
In-Reply-To: <50B88B8402000078000ACC4C@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1418 bytes --]
On 30.11.2012 10:33, Jan Beulich wrote:
>>>> On 29.11.12 at 19:55, Marek Marczykowski <marmarek@invisiblethingslab.com> wrote:
>> After resume from ACPI S3 system has only CPU0 enabled, every vCPU from
>> every
>> domain works on CPU0 [1]. When trying to pin some vCPU to CPU1 got error:
>> xl vcpu-pin testvm 1 1
>> libxl: error: libxl.c:2565:libxl_set_vcpuaffinity setting vcpu affinity:
>> Invalid argument
>>
>> What went wrong? How can I reenable CPU1-CPU3?
>
> According to the "xl dmesg" output you sent, CPU1-3 are all
> online (their presence in the output following "Dumping timer
> queues:" confirms this). So I suppose you will need to go do
> some debugging to find out where and why the set-affinity
> operation fails, and/or why the scheduler puts everything on
> a single pCPU (if it really does, the output of "xl vcpu-list" is
> only a hint towards that). Rather than using 'c', 'r' might have
> been the more useful debug key.
That was the rare case when resume worked at all... in most cased I've got
reboot, before anything appear on the screen (even backlight is off) - xen
panic? dom0 kernel panic?
I've already rebooted the system, will try above debug key next time.
I don't have serial console, but have USB-to-serial port - is it possible to
use it as xen console (in xen 4.1.3)?
--
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 553 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-11-30 16:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 18:55 Only CPU0 active after ACPI S3, xen 4.1.3 Marek Marczykowski
2012-11-30 9:33 ` Jan Beulich
2012-11-30 16:07 ` Marek Marczykowski [this message]
2012-11-30 16:12 ` Jan Beulich
2012-11-30 16:18 ` Marek Marczykowski
2012-12-03 7:39 ` Jan Beulich
2012-12-04 13:27 ` Marek Marczykowski
2012-12-20 15:59 ` Marek Marczykowski
2012-12-20 16:37 ` Jan Beulich
2012-12-20 19:41 ` Ben Guthro
2012-12-20 23:17 ` Marek Marczykowski
2012-12-21 4:52 ` Marek Marczykowski
2012-12-21 8:55 ` Jan Beulich
2012-12-21 13:33 ` Marek Marczykowski
2012-12-21 13:34 ` Marek Marczykowski
2012-12-21 13:42 ` Jan Beulich
2012-12-21 13:59 ` Marek Marczykowski
2012-12-21 14:03 ` Ben Guthro
2012-12-21 14:05 ` Jan Beulich
2012-12-21 15:30 ` Marek Marczykowski
2012-12-21 15:54 ` Ben Guthro
2012-12-21 16:03 ` Jan Beulich
2012-12-21 16:18 ` Ben Guthro
2012-12-23 2:49 ` Marek Marczykowski
2012-12-23 13:45 ` Ben Guthro
2012-12-31 12:51 ` Ben Guthro
2013-01-03 8:52 ` Jan Beulich
2013-01-16 11:22 ` George Dunlap
2013-01-16 11:58 ` George Dunlap
2013-01-16 13:08 ` Jan Beulich
2013-01-16 13:58 ` George Dunlap
2013-01-16 14:31 ` Jan Beulich
2013-01-03 8:52 ` Jan Beulich
2013-01-12 7:05 ` Marek Marczykowski
2013-01-14 3:28 ` Marek Marczykowski
2012-11-30 21:33 ` Konrad Rzeszutek Wilk
2012-11-30 22:12 ` Ben Guthro
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=50B8D9A9.60502@invisiblethingslab.com \
--to=marmarek@invisiblethingslab.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/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).