From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeroen Groenewegen van der Weyden Subject: Re: [PATCH 20 of 20] n2 MSR handling and capability exposure Date: Fri, 01 Jul 2011 12:11:20 +0200 Message-ID: <4E0D9D48.20308@grosc.com> References: <480cfcea095bddb2e7c4.1307607925@nest-wsm.los-vmm.org> <20110613082700.GA17634@whitby.uk.xensource.com> <1A42CE6F5F474C41B63392A5F80372B2562BF1EC@shsmsx501.ccr.corp.intel.com> <20110615124527.GG17634@whitby.uk.xensource.com> <4DFEE946.9070603@grosc.com> <4E0C84C8.1030804@grosc.com> <20110701090145.GS9784@whitby.uk.xensource.com> <4E0D9948.5000508@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E0D9948.5000508@amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com, Tim Deegan , "eddie.dong@intel.com" , "Christoph.Egger@amd.com" List-Id: xen-devel@lists.xenproject.org Just a remark to avoid misunderstanding The first nested KVM guest is running ok, for as long as i keep it running When starting a second nested KVM guest (in the same Xen DOMU) that is when the Xen DOMU becomes in-responsive. In DOM0 it it shown that it is still running and consuming time. The complete test is like this dom0 opensuse 11.4 x86 xen: unstable cs 23640 domu1 (HVM) sles11sp1 mem: 8 GB vcpu: 4 domu1 guests 1) qemu-kvm: propetary OS 2) qemu-kvm: propetary OS 3) qemu-kvm: SLES10SP3 4) qemu-kvm: SLES10SP3 mfg, Jeroen Op 1-7-2011 11:54, Christoph Egger schreef: > > KVM on Xen works for me. Also KVM on Xen on Xen. > > Christoph > > > On 07/01/11 11:01, Tim Deegan wrote: >> Eddie? Did you test with KVM guests? Is this expected to work? >> >> Tim. >> >> At 15:14 +0100 on 30 Jun (1309446872), Jeroen Groenewegen van der >> Weyden wrote: >>> Hi Tim/Eddi/Christoph, >>> >>> I just gave it a go again with cs23640. But the behaviour is still the >>> same. so L1 becomes inresponsive after starting the second nested >>> quest. >>> I can deliver any trace input you want/need. >>> >>> mfg, >>> Jeroen. >>> >>> Op 20-6-2011 8:31, Jeroen Groenewegen van der Weyden schreef: >>>> Hi, >>>> >>>> Based on these patch series, I gave it go. >>>> I noticed until now that the system becomes in-responsive a few second >>>> after activating the second nested guest. >>>> steps: >>>> 1) dom0 creates domu (pass) >>>> 2) domU creates first kvm guest (pass) >>>> 3) domU creates second kvm guest (fail) >>>> after the third step the domu becomes in-responsive. eg no network / >>>> vnc console response. in dom0 is shows domu is stil running. >>>> >>>> I'm able to provide any input needed, just tell me what you need (and >>>> how). >>>> >>>> mfg, >>>> Jeroen >>>> >>>> My HW setup >>>> mobo asus z8nr-d12 >>>> proc: 2 times e5645 >>>> mem: 96 GB >>>> >>>> My goal/test >>>> in short: HW -> dom0 -> domU -> 4 time kvm guest >>>> >>>> dom0 >>>> opensuse 11.4 x86 >>>> xen: unstable cs 23553 >>>> >>>> domu (HVM) >>>> sles11sp1 >>>> mem: 8 GB >>>> vcpu: 4 >>>> >>>> domu guests >>>> 1) qemu-kvm: propetary OS >>>> 2) qemu-kvm: propetary OS >>>> 3) qemu-kvm: SLES10SP3 >>>> 4) qemu-kvm: SLES10SP3 >>>> >>>> >>>> >>>> Op 15-6-2011 14:45, Tim Deegan schreef: >>>>> At 10:29 +0800 on 14 Jun (1308047377), Dong, Eddie wrote: >>>>>>>> + case MSR_IA32_VMX_MISC: >>>>>>>> + case MSR_IA32_VMX_CR0_FIXED0: >>>>>>>> + case MSR_IA32_VMX_CR0_FIXED1: >>>>>>>> + case MSR_IA32_VMX_CR4_FIXED0: >>>>>>>> + case MSR_IA32_VMX_CR4_FIXED1: >>>>>>>> + case MSR_IA32_VMX_VMCS_ENUM: >>>>>>>> + gdprintk(XENLOG_WARNING, "VMX MSR %x not fully supported >>>>>>> yet.\n", msr); >>>>>>> >>>>>>> Are you planning to fix this before checking in this series? I'm >>>>>>> pretty >>>>>>> sure that at least MSR_IA32_VMX_VMCS_ENUM should be trivial, >>>>>>> since you >>>>>>> define your own VMCS format. >>>>>>> >>>>>> Sure, the updated patch is attached. >>>>> Thanks. I've applied the full series. I cleaned up a few things for >>>>> the 32-bit build as well. >>>>> >>>>> Cheers, >>>>> >>>>> Tim. > >