From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>
Cc: george.dunlap@eu.citrix.com, xen-devel@lists.xenproject.org,
"Wei Liu" <wei.liu@citrix.com>, "Juergen Groß" <jgross@suse.com>
Subject: Re: Xen 4.8 + Linux 4.9 + Credit2 = can't bootup
Date: Thu, 12 Jan 2017 22:20:43 -0500 [thread overview]
Message-ID: <b60f77d7-0471-816e-82cf-f25a1ed287de@oracle.com> (raw)
In-Reply-To: <22647.51874.920172.895166@mariner.uk.xensource.com>
On 01/12/2017 01:27 PM, Ian Jackson wrote:
> Dario Faggioli writes ("Re: [Xen-devel] Xen 4.8 + Linux 4.9 + Credit2 = can't bootup"):
>> Anyway, we should have some multi-socket boxes on OSSTest, AFAICR.
>
> I think we do but I haven't got a systematic way of answering that
> question other than by manual eyeballing of the spec sheets.
>
> IF there were something easy to look for in the dmesg output (say) I
> could probably grep historical logs.
[root@ovs104 ~]# xl dmesg | grep Scrubbing
(XEN) Scrubbing Free RAM on 2 nodes using 16 CPUs
[root@ovs104 ~]#
or
[root@ovs104 ~]# xl info | grep nr_nodes
nr_nodes : 2
[root@ovs104 ~]#
may be useful.
BTW, when I said that the problem that this thread was started with
required multi-socket system I should have also said that dom0 needs to
span nodes (or so I think).
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-13 3:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 15:05 [linux-linus test] 104237: regressions - FAIL osstest service owner
2017-01-05 1:52 ` Xen 4.8 + Linux 4.9 + Credit2 = can't bootup Konrad Rzeszutek Wilk
2017-01-05 2:05 ` Andrew Cooper
2017-01-05 8:39 ` Dario Faggioli
2017-01-05 9:33 ` Anshul Makkar
2017-01-05 2:10 ` Konrad Rzeszutek Wilk
2017-01-05 3:13 ` Boris Ostrovsky
2017-01-06 15:55 ` Boris Ostrovsky
2017-01-12 12:50 ` Dario Faggioli
2017-01-12 16:22 ` Boris Ostrovsky
2017-01-12 16:41 ` Dario Faggioli
2017-01-12 18:27 ` Ian Jackson
2017-01-13 3:20 ` Boris Ostrovsky [this message]
2017-01-13 8:31 ` Dario Faggioli
2017-01-13 15:39 ` Boris Ostrovsky
2017-01-13 16:27 ` Ian Jackson
2017-01-13 23:13 ` Boris Ostrovsky
2017-01-16 11:38 ` Ian Jackson
2017-01-19 11:36 ` Xen 4.8 + Linux 4.9 + Credit2 = can't bootup [and 1 more messages] Ian Jackson
2017-01-16 15:38 ` Xen 4.8 + Linux 4.9 + Credit2 = can't bootup Roger Pau Monné
2017-01-16 15:39 ` Ian Jackson
2017-01-12 18:24 ` Ian Jackson
2017-01-19 17:06 ` [linux-linus test] 104237: regressions - FAIL Boris Ostrovsky
2017-01-19 16:23 ` [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 osstest service owner
2017-01-19 18:05 ` [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 [and 1 more messages] Ian Jackson
2017-01-19 18:44 ` Boris Ostrovsky
2017-01-20 11:09 ` Ian Jackson
2017-01-20 16:29 ` Boris Ostrovsky
2017-01-20 16:59 ` Boris Ostrovsky
2017-01-19 18:07 ` [linux-linus test] 104237: regressions - FAIL Ian Jackson
2017-01-19 19:09 ` Boris Ostrovsky
2017-01-19 19:15 ` Boris Ostrovsky
2017-01-19 20:37 ` Julien Grall
2017-01-19 21:01 ` Boris Ostrovsky
2017-01-20 12:06 ` Ian Jackson
2017-01-23 12:16 ` Ian Jackson
2017-01-23 14:31 ` Boris Ostrovsky
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=b60f77d7-0471-816e-82cf-f25a1ed287de@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=wei.liu@citrix.com \
--cc=xen-devel@lists.xenproject.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).