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 16:54:22 -0400 [thread overview]
Message-ID: <5032A3FE.30402@oracle.com> (raw)
In-Reply-To: <CC55042A.4992C%keir@xen.org>
On 08/18/2012 03:34 AM, Keir Fraser wrote:
> On 18/08/2012 07:38, "Keir Fraser" <keir.xen@gmail.com> wrote:
>
>>
>>> I think if a VM can be successfully started, then save/restore should
>>> also work. So I made a patch and did some testing.
>>
>> The check for 64 VCPUs is to cover the fact we only save/restore a 64-bit
>> vcpumap. That would need fixing too surely, ot CPUs > 64 would be offline
>> after restore I would imagine.
>
> How about the attached patch? It might actually work properly, unlike yours.
> ;)
>
>>> The above problem is gone but there are new ones.
>>>
>>> Let me summarize the result here.
>>>
>>> With the patch, save/restore works fine as long as it can be started,
>>> except two cases.
>>>
>>> 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.
>
>>> 2) 32-bit PVM guests can be configured with VCPUs > 64 and started,
>>> but `xm save' does not work.
>
> That's because your changes to the save/restore code were wrong. Try my
> patch instead.
>
> -- Keir
>
Tested. Your patch works perfectly for all cases. :)
Thanks,
Junjie
next prev parent reply other threads:[~2012-08-20 20:54 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 [this message]
2012-08-20 21:05 ` Junjie Wei
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=5032A3FE.30402@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).