All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	George Dunlap <george.dunlap@eu.citrix.com>
Subject: Re: Xen-4.4-rc2 - Some Nested Virt testing
Date: Tue, 21 Jan 2014 18:16:01 +0000	[thread overview]
Message-ID: <52DEB961.40506@citrix.com> (raw)
In-Reply-To: <52DEB887.8070409@citrix.com>

On 21/01/2014 18:12, Andrew Cooper wrote:
> Hello,
>
> I have been giving nested virt a try, and have my first bug to report. 
> This is still ongoing, and is by no means complete yet.
>
> Setup:
> Each reference to XenServer is a trunk XenServer based on 4.4-rc2
>
> Single Intel Haswell SDP (Grantley platform):
> Native hypervisor: XenServer
>
> Two L1 guests:
>   XenServer (running with EPT)
>   XenServer (running with shadow)
>
>
> When attempting to create an L2 EPT HVM domain under an L1 shadow
> domain, the L1 shadow domain is killed with:
>
> (XEN) <vm_launch_fail> error code 7
> (XEN) domain_crash_sync called from vmcs.c:1293
> (XEN) Domain 16 (vcpu#3) crashed on cpu#2:
> (XEN) ----[ Xen-4.4.0-xs82349-d  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    2
> (XEN) RIP:    0000:[<0000000000000000>]
> (XEN) RFLAGS: 0000000000000002   CONTEXT: hvm guest
> (XEN) rax: 0000000000000000   rbx: ffff83043cad8000   rcx: ffff83043cadff80
> (XEN) rdx: ffff82d0801d6ea0   rsi: 0000000000000000   rdi: ffff82d0801e2e8c
> (XEN) rbp: ffff82d080105680   rsp: 0000000000000000   r8:  ffff830064100000
> (XEN) r9:  ffff82d0801056ee   r10: ffff83043cadff70   r11: 0000000000000000
> (XEN) r12: ffff83043cadff50   r13: ffff830441e42000   r14: ffff830064100000
> (XEN) r15: ffff82d080189425   cr0: 0000000000000039   cr4: 0000000000002050
> (XEN) cr3: 0000000000000000   cr2: 0000000000000000
> (XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: 0000   cs: 0000

I suppose it is worth adding that `xl dmesg` from the L1 shadow
XenServer shows:

(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - MSR direct-access bitmap
(XEN)  - Unrestricted Guest
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) Brought up 4 CPUs

Which indicates that EPT is available even in a shadow L1 domain.  I
can't think of a technical reason why it wouldn't work.

>
>
> I am continuing experiments with different VMs under each L1 hypervisor,
> to see what else breaks.
>
> ~Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2014-01-21 18:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 18:12 Xen-4.4-rc2 - Some Nested Virt testing Andrew Cooper
2014-01-21 18:16 ` Andrew Cooper [this message]
2014-01-22  9:38 ` Jan Beulich
2014-01-22 10:40   ` Andrew Cooper
2014-01-24 14:58 ` George Dunlap
2014-01-24 16:00 ` George Dunlap
2014-01-26  8:29   ` Zhang, Yang Z
2014-01-27  9:33     ` Tim Deegan
2014-01-27 15:34       ` Zhang, Yang Z

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=52DEB961.40506@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.