All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeroen Groenewegen van der Weyden <groen692@grosc.com>
To: xen-devel@lists.xen.org
Subject: Crash of guest with nested vmx with Unknown nested vmexit reason 80000021.
Date: Tue, 30 Sep 2014 17:55:18 +0200	[thread overview]
Message-ID: <542AD266.5030803@grosc.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4318 bytes --]

Hi,

Recently I updated my openSuse box from 12.3 to 13.1. On this box I run 
xen with several guests. One of these guests is an appliance that has 4 
kvm guests running.
When I start this appliance with the nested vmx feature the appliance 
crashes either immediately or after a few minutes.

This same guest was running without a problem on opensuse releases 11.4 
until 12.3

( remark that about 3 year ago some patches were written by tim degan to make this appliance work )

dom0
opensuse 13.1 x86
kernel 3.11.10-21-xen
xen: 4.3..2_01-21.1

- domu (HVM)
- sles11sp2
- mem: 8 GB
- vcpu: 4
- kvm with 4 guest

any body any thought on this?

BR,
Jeroen


==== outup xl demsg
(XEN) vvmx.c:2459:d5 Unknown nested vmexit reason 80000021.
(XEN) Failed vm entry (exit reason 0x80000021) caused by invalid guest 
state (0).
(XEN) ************* VMCS Area **************
(XEN) *** Guest State ***
(XEN) CR0: actual=0x0000000080000033, shadow=0x0000000000000011, 
gh_mask=ffffffffffffffff
(XEN) CR4: actual=0x0000000000002050, shadow=0x0000000000000000, 
gh_mask=ffffffffffffffff
(XEN) CR3: actual=0x00000000feffc000, target_count=0
(XEN)      target0=0000000000000000, target1=0000000000000000
(XEN)      target2=0000000000000000, target3=0000000000000000
(XEN) RSP = 0x0000000000000398 (0x0000000000000398)  RIP = 
0x000000000000045f (0x000000000000045f)
(XEN) RFLAGS=0x0000000000000006 (0x0000000000000006)  DR7 = 
0x0000000000000400
(XEN) Sysenter RSP=0000000000000000 CS:RIP=0000:0000000000000000
(XEN) CS: sel=0x9dcc, attr=0x0009b, limit=0x00000ecb, 
base=0x0000000000689920
(XEN) DS: sel=0x9db4, attr=0x00093, limit=0x000038b9, 
base=0x00000000006778b0
(XEN) SS: sel=0x9e7c, attr=0x00093, limit=0x00000401, 
base=0x00000000006ba960
(XEN) ES: sel=0x3ec8, attr=0x00093, limit=0x00000099, 
base=0x000000000073c608
(XEN) FS: sel=0x0000, attr=0x1c000, limit=0xffffffff, 
base=0x0000000000000000
(XEN) GS: sel=0x0000, attr=0x1c000, limit=0xffffffff, 
base=0x0000000000000000
(XEN) GDTR:                           limit=0x0000ffff, 
base=0x0000000001000000
(XEN) LDTR: sel=0x0820, attr=0x00082, limit=0x0000ffff, 
base=0x0000000001010400
(XEN) IDTR:                           limit=0x000003ff, 
base=0x0000000001010000
(XEN) TR: sel=0x0690, attr=0x00083, limit=0x0000002b, 
base=0x0000000001213a30
(XEN) Guest PAT = 0x0000050100070406
(XEN) TSC Offset = fffd869460e8dc28
(XEN) DebugCtl=0000000000000000 DebugExceptions=0000000000000000
(XEN) Interruptibility=0008 ActivityState=0000
(XEN) *** Host State ***
(XEN) RSP = 0xffff83083ff27f90  RIP = 0xffff82c4c01d9330
(XEN) CS=e008 DS=0000 ES=0000 FS=0000 GS=0000 SS=0000 TR=e040
(XEN) FSBase=0000000000000000 GSBase=0000000000000000 
TRBase=ffff83083ff2dc80
(XEN) GDTBase=ffff8318035ee000 IDTBase=ffff8318035fa000
(XEN) CR0=0000000080050033 CR3=0000000eefcc0000 CR4=00000000000026f0
(XEN) Sysenter RSP=ffff83083ff27fc0 CS:RIP=e008:ffff82c4c0216c60
(XEN) Host PAT = 0x0000050100070406
(XEN) *** Control State ***
(XEN) PinBased=0000003f CPUBased=b6b9e5fa SecondaryExec=000004eb
(XEN) EntryControls=000011ff ExitControls=000fefff
(XEN) ExceptionBitmap=00040042
(XEN) VMEntry: intr_info=80000202 errcode=5d021101 ilen=00000003
(XEN) VMExit: intr_info=00000000 errcode=00000000 ilen=00000003
(XEN)         reason=80000021 qualification=00000000
(XEN) IDTVectoring: info=80000202 errcode=00000000
(XEN) TPR Threshold = 0x00
(XEN) EPT pointer = 0x0000000ef022501e
(XEN) Virtual processor ID = 0xc0d0
(XEN) **************************************
(XEN) domain_crash called from vmx.c:2342
(XEN) Domain 5 (vcpu#3) crashed on cpu#20:
(XEN) ----[ Xen-4.3.2_01-21.1  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    20
(XEN) RIP:    9dcc:[<000000000000045f>]
(XEN) RFLAGS: 0000000000000006   CONTEXT: hvm guest
(XEN) rax: 0000000000000001   rbx: 00000000000026db   rcx: 000000009dd40003
(XEN) rdx: 00000000248816a0   rsi: 0000000000000000   rdi: 0000000026b010e4
(XEN) rbp: 00000000000003ae   rsp: 0000000000000398   r8: 0000000000000000
(XEN) r9:  0000000000000000   r10: 0000000000000000   r11: 0000000000000000
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 0000000080000033   cr4: 0000000000002010
(XEN) cr3: 00000000feffc000   cr2: 0000000000000000
(XEN) ds: 9db4   es: 3ec8   fs: 0000   gs: 0000   ss: 9e7c   cs: 9dcc


[-- Attachment #1.2: Type: text/html, Size: 5620 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2014-09-30 15:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 15:55 Jeroen Groenewegen van der Weyden [this message]
2014-10-01 13:20 ` Crash of guest with nested vmx with Unknown nested vmexit reason 80000021 Jan Beulich
2014-10-07  7:58 ` Jan Beulich
2014-10-07 15:16   ` Jeroen Groenewegen van der Weyden
2014-10-07 19:56   ` Tian, Kevin
2014-10-10 10:31     ` Jeroen Groenewegen van der Weyden
2014-10-16  6:18       ` Zhang, Yang Z
2014-10-16  6:41         ` Jan Beulich
2014-10-29 14:17           ` Jeroen Groenewegen van der Weyden
2014-10-29 16:42             ` Jan Beulich
2014-11-03 11:16               ` George Dunlap
2014-12-09  9:09                 ` Jeroen Groenewegen van der Weyden
2014-12-09  9:17                   ` Jan Beulich
2015-02-26 18:56                     ` Jeroen Groenewegen van der Weyden
2015-02-27  8:08                       ` Jan Beulich
2015-03-04 10:24                         ` Jeroen Groenewegen van der Weyden
2015-04-07  7:18                           ` Li, Liang Z
2014-10-16  6:27       ` 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=542AD266.5030803@grosc.com \
    --to=groen692@grosc.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.