xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Junjie Wei <junjie.wei@oracle.com>
To: Keir Fraser <keir@xen.org>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: VM save/restore
Date: Mon, 20 Aug 2012 17:05:38 -0400	[thread overview]
Message-ID: <5032A6A2.7070802@oracle.com> (raw)
In-Reply-To: <CC55042A.4992C%keir@xen.org>

On 08/18/2012 03:34 AM, Keir Fraser wrote:
>>>
>>> 1) 32-bit guests can be configured with VCPUs > 32 and started,
>>>      but the guest can only make use of 32 of them.
>
> HVM guest? I don't know why this is. You will have to investigate some more
> what has happened to the rest of your VCPUs! I think it should definitely
> work. Cc Jan in case he has any thoughts.
>

It looks like that for 32-bit guests, the VCPU -> CPU mapping only works 
for the first 32 VCPUs. It can be reliably reproduced.

Thanks,
Junjie


[root@ovs087 HVM_X86]# rpm -qa | grep xen
xenpvboot-0.1-8.el5
xen-tools-4.1.2-39
xen-devel-4.1.2-39
xen-4.1.2-39

[root@ovs087 HVM_X86]# uname -a
Linux ovs087 2.6.39-200.30.1.el5uek #1 SMP Thu Jul 12 21:47:09 EDT 2012 
x86_64 x86_64 x86_64 GNU/Linux

[root@ovs087 HVM_X86]# cat vm.cfg | grep vcpus
vcpus = 36

[root@ovs087 HVM_X86]# xm list 65
Name                                        ID   Mem VCPUs      State 
Time(s)
OVM_OL5U7_X86_PVHVM_10GB                    65  2048    32     r----- 
   33.3

[root@ovs087 HVM_X86]# xm vcpu-list 65
Name                                ID  VCPU   CPU State   Time(s) CPU 
Affinity
OVM_OL5U7_X86_PVHVM_10GB            65     0     4   -b-      10.7 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65     1     0   -b-       1.8 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65     2     4   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65     3     2   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65     4     7   -b-       1.1 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65     5     5   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65     6     0   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65     7     3   r--      10.6 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65     8     4   -b-       0.9 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65     9     7   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    10     7   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    11     2   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    12     6   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    13     4   -b-       0.9 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    14     7   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    15     5   -b-       0.9 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    16     0   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    17     6   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    18     4   -b-       0.9 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    19     5   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    20     7   -b-       0.9 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    21     0   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    22     5   -b-       0.9 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    23     4   -b-       0.9 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    24     4   -b-       0.9 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    25     0   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    26     2   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    27     6   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    28     4   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    29     7   -b-       0.9 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    30     2   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    31     0   -b-       1.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    32     -   --p       0.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    33     -   --p       0.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    34     -   --p       0.0 any cpu
OVM_OL5U7_X86_PVHVM_10GB            65    35     -   --p       0.0 any cpu

  parent reply	other threads:[~2012-08-20 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 21:28 VM save/restore Junjie Wei
2012-08-18  6:38 ` Keir Fraser
2012-08-18  7:34   ` Keir Fraser
2012-08-20 20:54     ` Junjie Wei
2012-08-20 21:05     ` Junjie Wei [this message]
2012-08-20 20:58   ` Junjie Wei
2012-08-22 21:17     ` Keir Fraser

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=5032A6A2.7070802@oracle.com \
    --to=junjie.wei@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --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).