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] Re: [Xen-users] Nested Virtualisation question

To: Jeroen Groenewegen van der Weyden <groen692@xxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] Nested Virtualisation question
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Sat, 09 Apr 2011 07:22:30 +0100
Cc: "Christoph.Egger@xxxxxxx" <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 08 Apr 2011 23:23:32 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:cc:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=dNuU/S7J/COveZdIWtDWDd6WVZj9QQ8sLPrdkBDxKDI=; b=kR6AEeZBvl4vn96wmwzPMXMWL3+SGG4kihHvyQ8G07GZPeETDg4v3whKrDX2cf7LxI 5GNYcDk2Xuqy64M+wT6PSO2O8qFU2mzF/JfJZunKgSUn2TaayLerE17FxwIy9uaGP4LQ MB4EAkwrXsjCImIOvDG4cYGlf7LSb/O35415s=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=riAEpzbLY+Iuyosr1wNoYr9nAhr9SKm1kB7m8uujNvJyeo2ImUN6IV8ReB04gk0Qeh gM9FQQKjz3flcrvenM7Pi+exmfwGZGxg/3kmrFXQu2elDq5CQWyM8+VVcZZ5T0X10Dim 66M7dqrbDoVXKSxIW8JVo6v7Hf7myXlUxj2RA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D9FE981.2080108@xxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acv2foD0boqjE+wNCkK2P36/bwZPcA==
Thread-topic: [Xen-devel] Re: [Xen-users] Nested Virtualisation question
User-agent: Microsoft-Entourage/
On 09/04/2011 06:07, "Jeroen Groenewegen van der Weyden"
<groen692@xxxxxxxxx> wrote:

> The result with c/s23197
> Regular domain now start, en stop normaly, (xl seems to have a problem
> though, after domain closes a domain null remains in de xl list/ xmdoe
> not have this.)
> for nestedVM I added the "nestedhvm=1" in the config file of the domain.
> but the domain does not start because of "invalid argument"

NestedHVM currently requires you to be using an AMD processor with hardware
nested paging (known as HAP by Xen). Most likely you need to add hap=1 to
your config file (and hope your processor supports it).

 -- Keir

> +++++++++ beging console
> hydra:/etc/xen/vm # xm create groscNestedVM
> Using config file "./groscNestedVM".
> Error: (22, 'Invalid argument')
> +++++++++ end console
> +++++++++ begin xend.log
> hydra:/etc/xen/vm # tail /var/log/xen/xend.log
>      dominfo = XendDomainInfo.create(config)
>    File "/usr/lib64/python2.7/site-packages/xen/xend/XendDomainInfo.py",
> line 106, in create
>      vm.start()
>    File "/usr/lib64/python2.7/site-packages/xen/xend/XendDomainInfo.py",
> line 473, in start
>      XendTask.log_progress(0, 30, self._constructDomain)
>    File "/usr/lib64/python2.7/site-packages/xen/xend/XendTask.py", line
> 209, in log_progress
>      retval = func(*args, **kwds)
>    File "/usr/lib64/python2.7/site-packages/xen/xend/XendDomainInfo.py",
> line 2598, in _constructDomain
>      xc.hvm_set_param(self.domid, HVM_PARAM_NESTEDHVM, long(nestedhvm))
> Error: (22, 'Invalid argument')
> +++++++++++ end xend.log
> Op 7-4-2011 12:29, Tim Deegan schreef:
>> At 08:14 +0100 on 07 Apr (1302164093), Keir Fraser wrote:
>>> On 07/04/2011 08:09, "Keir Fraser"<keir.xen@xxxxxxxxx>  wrote:
>>>> Probably the same as this, happening often in the automated tests:
>>> Likely reason: nestedhvm_vcpu_initialise() being called unconditionally in
>>> hvm_vcpu_initialise() even though nestedhvm has not been configured for this
>>> domain. This then fails because there is no nestedhvm handler for Intel yet.
>> This bug should be fixed by 23175:e5a750d1bf9b, arriving at a staging
>> tree near you at any moment.
>>> And beyond that it's most likely an issue of a broken failure path, or a
>>> problem in the HAP code with cleaning up a half-created guest.
>> This one I'll look into now.
>> Tim.

Xen-devel mailing list

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