From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Steven Haigh' <netwiz@crc.id.au>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
Andreas Kinzler <hfp@posteo.de>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Windows HVM no longer boots with AMD Ryzen 3700X (and 3900X)
Date: Mon, 2 Sep 2019 08:20:11 +0000 [thread overview]
Message-ID: <b3b0c2de1e364adea566eb961ba3d727@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <2d859d487c294b8d98749dccaf735c96@crc.id.au>
> -----Original Message-----
> From: Steven Haigh <netwiz@crc.id.au>
> Sent: 02 September 2019 09:09
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Andreas Kinzler <hfp@posteo.de>; Andrew Cooper <Andrew.Cooper3@citrix.com>; xen-
> devel@lists.xenproject.org
> Subject: Re: Windows HVM no longer boots with AMD Ryzen 3700X (and 3900X)
>
> On 2019-09-02 18:04, Paul Durrant wrote:
> >> -----Original Message-----
> >> Further to the above, I did some experimentation. The following is a
> >> list of attempted boot configurations and their outcomes:
> >>
> >> viridian=1
> >> vcpus=4
> >> STOPCODE: HAL MEMORY ALLOCATION
> >>
> >> viridian=0
> >> vcpus=4
> >> STOPCODE: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
> >>
> >> viridian=0
> >> vcpus=1
> >> Boot OK - get to Windows Server 2016 login etc
> >>
> >
> > And to complete the set, how about viridian=1 vcpus=1?
>
> Any vcpus value where viridian=1 is used creates a HAL MEMORY ALLOCATION
> stopcode when trying to boot Windows.
Ok, so I guess that issue hits first and, only if you get beyond that do you hit the multiprocessor problem.
The viridian option is not actually a boolean any more (that interpretation is just for compat) so it would be a good datapoint to know which of the enlightenments causes the change in behaviour. Could you try viridian=['base'] to see if that's sufficient to cause the problem? (I'm guessing it probably is but it would be good to know).
Paul
>
> --
> 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
next prev parent reply other threads:[~2019-09-02 8:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 18:03 [Xen-devel] Windows HVM no longer boots with AMD Ryzen 3700X Andreas Kinzler
2019-08-20 18:10 ` Andrew Cooper
2019-08-20 18:12 ` Andrew Cooper
2019-08-20 20:36 ` Andreas Kinzler
2019-08-20 20:38 ` Andrew Cooper
2019-08-20 20:57 ` Andreas Kinzler
2019-09-02 1:42 ` [Xen-devel] Windows HVM no longer boots with AMD Ryzen 3700X (and 3900X) Steven Haigh
2019-09-02 1:53 ` Steven Haigh
2019-09-02 8:04 ` Paul Durrant
2019-09-02 8:08 ` Steven Haigh
2019-09-02 8:20 ` Paul Durrant [this message]
2019-09-02 8:25 ` Steven Haigh
2019-09-02 8:31 ` Steven Haigh
2019-09-02 8:34 ` Paul Durrant
2019-09-02 10:01 ` Steven Haigh
2019-10-02 10:04 ` [Xen-devel] Windows HVM no longer boots with AMD Ryzen 3700X Andreas Kinzler
2020-01-31 12:43 ` Joost Heijne
2020-01-31 13:05 ` Andrew Cooper
2020-01-31 13:13 ` Joost Heijne
2019-09-23 8:17 ` Jan Beulich
2019-09-24 9:56 ` Andreas Kinzler
2019-09-24 14:39 ` Steven Haigh
2019-09-24 16:58 ` Andreas Kinzler
2019-09-26 8:41 ` Jan Beulich
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=b3b0c2de1e364adea566eb961ba3d727@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=hfp@posteo.de \
--cc=netwiz@crc.id.au \
--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.