From: Jan Beulich <jbeulich@suse.com>
To: Steven Haigh <netwiz@crc.id.au>
Cc: Paul Durrant <pdurrant@gmail.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Debugging Windows HVM crashes on Ryzen 3xxx series CPUs.
Date: Fri, 25 Oct 2019 10:28:36 +0200 [thread overview]
Message-ID: <8fdbc94b-a333-a4ba-146e-e1b853655a79@suse.com> (raw)
In-Reply-To: <82cb0edff0fb69d470a8374f5595e052@crc.id.au>
On 25.10.2019 09:00, Steven Haigh wrote:
> Further to my last, I downloaded the latest Windows Server 2016 ISO from
> Microsoft.
>
> Filename: Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO
>
> Have attached as much of the log as I could get attempting to boot from
> the ISO and having a blank LV as the install target.
>
> The Windows error message (shown via VNC) is HAL MEMORY ALLOCATION.
Hmm, that's as if there was still (again?) an issue with CPUID
handling - iirc the same was observable on maximum-size Rome
systems prior to df29d03f1d (and its fixup). Below the debugging
patch I did use at the time, maybe it turns out helpful here too
(and perhaps you'd really only need the first hunk, I had put in
the other one just in case anyway).
However this looks to be different from your earlier report,
where you said you've got some
(XEN) d1v0 VIRIDIAN CRASH: ac 0 a0a0 fffff8065c06bf88 bf8
So I wonder whether there's a new issue masking the old one.
Jan
--- unstable.orig/xen/arch/x86/hvm/hvm.c
+++ unstable/xen/arch/x86/hvm/hvm.c
@@ -3372,6 +3372,9 @@ int hvm_vmexit_cpuid(struct cpu_user_reg
}
guest_cpuid(curr, leaf, subleaf, &res);
+if(regs->ax && (regs->eax >> 16) != 0x4000 && (long)regs->rip < 0) {//temp
+ printk("%pv[%08lx]: %08x:%08x=%08x:%08x:%08x:%08x\n", curr, regs->rip, leaf, subleaf, res.a, res.b, res.c, res.d);
+}
HVMTRACE_6D(CPUID, leaf, subleaf, res.a, res.b, res.c, res.d);
regs->rax = res.a;
--- unstable.orig/xen/arch/x86/hvm/svm/svm.c
+++ unstable/xen/arch/x86/hvm/svm/svm.c
@@ -2223,7 +2223,13 @@ static void svm_do_msr_access(struct cpu
rc = hvm_msr_read_intercept(regs->ecx, &msr_content);
if ( rc == X86EMUL_OKAY )
+{//temp
msr_split(regs, msr_content);
+ if(regs->ecx == 0xc001100c || regs->ecx == 0xc0011005)
+ printk("%pv[%08lx]: %08x -> %08x:%08x\n", curr, regs->rip, regs->ecx, regs->edx, regs->eax);
+} else if(regs->ecx == 0xc001100c || regs->ecx == 0xc0011005) {
+ printk("%pv[%08lx]: %08x -> #GP\n", curr, regs->rip, regs->ecx);
+}
}
else
rc = hvm_msr_write_intercept(regs->ecx, msr_fold(regs), true);
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-25 8:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:57 [Xen-devel] Debugging Windows HVM crashes on Ryzen 3xxx series CPUs Steven Haigh
2019-10-24 14:45 ` Paul Durrant
2019-10-25 5:26 ` Steven Haigh
2019-10-25 7:00 ` Steven Haigh
2019-10-25 8:28 ` Jan Beulich [this message]
2019-10-25 10:10 ` Steven Haigh
2019-10-25 17:01 ` Andrew Cooper
2019-10-26 5:22 ` Jürgen Groß
2019-10-28 9:22 ` Jan Beulich
2019-10-28 9:21 ` Jan Beulich
2019-10-28 10:42 ` Paul Durrant
2019-10-28 11:18 ` Andrew Cooper
2019-10-28 11:46 ` Jan Beulich
2019-10-28 11:03 ` Andreas Kinzler
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=8fdbc94b-a333-a4ba-146e-e1b853655a79@suse.com \
--to=jbeulich@suse.com \
--cc=netwiz@crc.id.au \
--cc=pdurrant@gmail.com \
--cc=xen-devel@lists.xenproject.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.