xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Kinzler <hfp@posteo.de>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Paul.Durrant@citrix.com, Steven Haigh <netwiz@crc.id.au>,
	xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] Windows HVM no longer boots with AMD Ryzen 3700X
Date: Tue, 24 Sep 2019 18:58:54 +0200	[thread overview]
Message-ID: <b5df65da-38a6-f7ce-b7ec-3ab6af5e4c44@posteo.de> (raw)
In-Reply-To: <5d406fbf-d057-a515-5364-6f0e2f6955c7@suse.com>

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

On 23.09.2019 10:17, Jan Beulich wrote:
>>> Does booting with a single vCPU work?
>> Number of vCPUs make no difference
> Well, according to Steven it does, with viridian=0. Could you
> re-check this?

I can confirm that viridian=0 AND vcpus=1 makes the system bootable 
(with long delay though)

> at least the viridian=0 case? As to Linux, did you check that PVH
> (or HVM, which you don't mention) guests actually start all their vCPU-s
> successfully?

I just tried PVH and HVM with 8 vcpus. Everything works, tested with 
make -j9 on a kernel tree.

 > 8-core chip, I wonder whether
 > 
https://lists.xenproject.org/archives/html/xen-devel/2019-09/msg01954.html
 > still affects this configuration as well. Could you give this a try in

Does it still make sense to try the patch given the cpuid I posted?
Also I have an AMD 7302P in my lab (cpuid dump attached). No change in 
behavior from 3700X - cpuid is nearly the same.

Regards Andreas

[-- Attachment #2: cpuid-amd7302p.tar.xz --]
[-- Type: application/octet-stream, Size: 8176 bytes --]

[-- Attachment #3: Type: text/plain, Size: 157 bytes --]

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

  parent reply	other threads:[~2019-09-24 16:59 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
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 [this message]
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=b5df65da-38a6-f7ce-b7ec-3ab6af5e4c44@posteo.de \
    --to=hfp@posteo.de \
    --cc=Paul.Durrant@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --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 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).