From: Sean Christopherson <seanjc@google.com>
To: bugzilla-daemon@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 219085] kvm_spurious_fault in L1 when running a nested kvm instance on AMD Opteron_G5_qemu L0
Date: Mon, 22 Jul 2024 16:21:02 -0700 [thread overview]
Message-ID: <Zp7pXnf2baQWJHcN@google.com> (raw)
In-Reply-To: <bug-219085-28872-KtqhT84gS6@https.bugzilla.kernel.org/>
On Mon, Jul 22, 2024, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219085
>
> --- Comment #1 from ununpta@mailto.plus ---
> Command I used on L0 AMD Ryzen:
> qemu-system-x86_64.exe -m 4096 -machine q35 -accel whpx -smp 1 -cpu
This is likely an issue in the L0 hypervisor, which in this case is Hyper-V. KVM
(L1) hits a #GP when trying to enable EFER.SVME, which leads to the #UD on VMSAVE
(SVM isn't enabled).
[ 355.714362] unchecked MSR access error: WRMSR to 0xc0000080 (tried to write 0x0000000000001d01) at rIP: 0xffffffff9228a274 (native_write_msr+0x4/0x20)
Do you you see the same behavior on other kernel (L1) version? Have you changed
any other components (especially in L0)?
> Opteron_G5,check,+svm -hda c:\debian.qcow2
>
> It's reproducible in 100% cases
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-07-22 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 18:50 [Bug 219085] New: kvm_spurious_fault in L1 when running a nested kvm instance on AMD Opteron_G5_qemu L0 bugzilla-daemon
2024-07-22 18:51 ` [Bug 219085] " bugzilla-daemon
2024-07-22 19:13 ` bugzilla-daemon
2024-07-22 23:21 ` Sean Christopherson [this message]
2024-07-22 23:21 ` bugzilla-daemon
2024-07-23 18:53 ` bugzilla-daemon
2024-07-23 19:13 ` Sean Christopherson
2024-07-23 19:13 ` bugzilla-daemon
2024-07-24 19:15 ` bugzilla-daemon
2024-08-12 7:44 ` bugzilla-daemon
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=Zp7pXnf2baQWJHcN@google.com \
--to=seanjc@google.com \
--cc=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox