From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeroen Groenewegen van der Weyden Subject: Re: Re: [Xen-users] Nested Virtualisation question Date: Sat, 09 Apr 2011 12:18:07 +0200 Message-ID: <4DA0325F.2000203@grosc.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "Christoph.Egger@amd.com" , "xen-devel@lists.xensource.com" , Tim Deegan List-Id: xen-devel@lists.xenproject.org The HAP is default set to one, I check this also with a dry run. Please confirm all this support just amd, because I only have Intel overhere. mfg, Jeroen Op 9-4-2011 8:22, Keir Fraser schreef: > On 09/04/2011 06:07, "Jeroen Groenewegen van der Weyden" > 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" 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. >>> >>> > >