This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] vcpu-set and save/restore/reboot

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] vcpu-set and save/restore/reboot
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Sat, 28 Apr 2007 01:28:52 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 27 Apr 2007 17:22:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C258026A.677D%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070427172343.GA23955@xxxxxxxxxxxxxxxxxxxxxxx> <C258026A.677D%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Apr 27, 2007 at 07:41:30PM +0100, Keir Fraser wrote:

> > We've noticed in 3.0.4 (and it seems to be intentional) that if you
> > vcpu-set a domain to fewer CPUs, when it restarts (restore or reboot),
> > only those VCPUs are present in xenstore or the domain. This seems
> > strange at least? It's unfortunate since it means the domain can never
> > get those VCPUs back.
> Max_vcpus should still be set to its original build-time value, so the guest
> kernel should still be aware that the maximal number of vcpus *could* exist.
> And the nodes should still exist in xenstore, but marked offline.

This is not the case with 3.0.4 at least. When I reboot a domain I don't
see any entries past the ones we set. I haven't had a chance to test
3.0.5 yet, but it seems to have similar code.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>