Re: [Xen-devel] Windows HVM no longer boots with AMD Ryzen 3700X (and 3900X)

From: Steven Haigh <netwiz@crc.id.au>
To: Andreas Kinzler <hfp@posteo.de>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Paul.Durrant@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] Windows HVM no longer boots with AMD Ryzen 3700X (and 3900X)
Date: Mon, 02 Sep 2019 11:42:46 +1000	[thread overview]
Message-ID: <71fad1413643be2df5f2291270b60448@crc.id.au> (raw)
In-Reply-To: <1dfc79fa-acde-40af-704d-be3289fdd133@posteo.de>

On 2019-08-21 06:57, Andreas Kinzler wrote:
> On 20.08.2019 22:38, Andrew Cooper wrote:
>> On 20/08/2019 21:36, Andreas Kinzler wrote:
>>> On 20.08.2019 20:12, Andrew Cooper wrote:
>>>>> Xen version 4.10.2. dom0 kernel 4.13.16. The BIOS version is 
>>>>> unchanged
>>>>> from 2700X (working) to 3700X (crashing).
>>>> So you've done a Zen v1 => Zen v2 CPU upgrade and an existing 
>>>> system?
>>> With "existing system" you mean the Windows installation?
>> I meant same computer, not same VM.
> 
> Tried with 2 mainboards: Asrock X370 Pro4 and AsrockRack X470D4U.
> You need to flash the BIOS for Zen2. X470D4U BIOS 3.1 works with 2700X
> but not with 3700X. X370 Pro4 with somewhat older BIOS worked for
> 2700X and does not work with current (6.00) BIOS and 3700X.
> 
>>> Yes, but it is not relevant. The same BSODs happen if you boot the 
>>> HVM
>>> with just the iso installation medium and no disks.
>> That's a useful datapoint.  I wouldn't expect this to be relevant, 
>> given
>> how Window's HAL works.
> 
> It should make debugging for you quite "simple" because it can be
> reproduced very easily.

Just to add a data point to this - I also see this problem on a Ryzen 9 
3900x.

xl dmesg shows:
(XEN) d2v0 VIRIDIAN CRASH: ac 0 a0a0 fffff80293254750 aea
(XEN) d3v0 VIRIDIAN CRASH: ac 0 a0a0 fffff80093a40750 aea
(XEN) d5v0 VIRIDIAN CRASH: ac 0 a0a0 fffff8028e422350 aea
(XEN) d6v0 VIRIDIAN CRASH: ac 0 a0a0 fffff80309431750 aea
(XEN) d10v0 VIRIDIAN CRASH: ac 0 a0a0 fffff8012823e750 aea
(XEN) d11v0 VIRIDIAN CRASH: ac 0 a0a0 fffff8032e657350 aea

Windows usually has a stopcode of "HAL MEMORY ALLOCATION" when it blue 
screens.

 From xl info:
hw_caps                : 
178bf3ff:f6d8320b:2e500800:244037ff:0000000f:219c91a9:00400004:00000500
virt_caps              : hvm hvm_directio
xen_version            : 4.11.2
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
hvm-3.0-x86_32p hvm-3.0-x86_64

Is there any further info that can be provided? Not being able to 
virtualise Windows is a bit of a PITA...

-- 
Steven Haigh

? netwiz@crc.id.au     ? http://www.crc.id.au
? +61 (3) 9001 6090    ? 0412 935 897

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel