From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Raslan, KarimAllah" <karahmed@amazon.de>,
"jmattson@google.com" <jmattson@google.com>,
"liran.alon@oracle.com" <liran.alon@oracle.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Cc: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
Subject: Re: KVM_SET_NESTED_STATE not yet stable
Date: Wed, 10 Jul 2019 23:14:49 +0200 [thread overview]
Message-ID: <9803d517-f52b-66b8-cefc-d5b89e55de75@siemens.com> (raw)
In-Reply-To: <cfd86643-dbac-3a69-9faf-03eaa8aee6a1@siemens.com>
On 10.07.19 22:31, Jan Kiszka wrote:
> And on a Xeon D-1540, I'm not seeing a crash but a kvm entry failure when
> resetting L1 while running Jailhouse:
>
> KVM: entry failed, hardware error 0x7
> EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000f61
> ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000
> EIP=0000fff0 EFL=00000246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
> ES =0000 00000000 0000ffff 00009300
> CS =f000 ffff0000 0000ffff 00a09b00
> SS =0000 00000000 0000ffff 00c09300
> DS =0000 00000000 0000ffff 00009300
> FS =0000 00000000 0000ffff 00009300
> GS =0000 00000000 0000ffff 00009300
> LDT=0000 00000000 0000ffff 00008200
> TR =0000 00000000 0000ffff 00008b00
> GDT= 00000000 0000ffff
> IDT= 00000000 0000ffff
> CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000680
> DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
> DR6=00000000ffff0ff0 DR7=0000000000000400
> EFER=0000000000000000
> Code=00 66 89 d8 66 e8 af a1 ff ff 66 83 c4 0c 66 5b 66 5e 66 c3 <ea> 5b e0 00
> f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
OK, looks like the feature diff was a red herring: Ralf found a server with even
more features and without a crash, and I found familiar error messages in the
kernel log of that Xeon D:
kvm: vmptrld (null)/778000000000 failed
kvm: vmclear fail: (null)/778000000000
Only difference: No crash, just that more graceful entry failure.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-07-10 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 20:39 KVM_SET_NESTED_STATE not yet stable Jan Kiszka
2019-07-10 15:24 ` Raslan, KarimAllah
2019-07-10 16:05 ` Jan Kiszka
2019-07-10 20:31 ` Jan Kiszka
2019-07-10 21:14 ` Jan Kiszka [this message]
2019-07-11 11:37 ` Ralf Ramsauer
2019-07-11 17:30 ` Paolo Bonzini
2019-07-19 16:38 ` Paolo Bonzini
2019-07-21 9:05 ` Jan Kiszka
2019-07-22 15:10 ` Ralf Ramsauer
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=9803d517-f52b-66b8-cefc-d5b89e55de75@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=jmattson@google.com \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=ralf.ramsauer@oth-regensburg.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).