All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reinoud Zandijk <reinoud@NetBSD.org>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Windows 10 won't run on default x86_64 machine anymore
Date: Mon, 15 Mar 2021 23:27:29 +0100	[thread overview]
Message-ID: <YE/fUQRiFBfrWi5W@dropje.13thmonkey.org> (raw)
In-Reply-To: <20210315185302.29b0d90d@redhat.com>

On Mon, Mar 15, 2021 at 06:53:02PM +0100, Igor Mammedov wrote:
> Windows 10 1607x64 boots fine when I test it with default machine.
> 
> So
>   1) can you provide full QEMU command line used
>   2) What Windows build do you use
>   3) is it existing guest image (i.e. installed in older QEMU version)

I've used:

qemu-system-x86_64 -m 4G -smp cores=2 -accel nvmm \
	-snapshot \
	-drive file=/home/reinoud/Downloads/Win10-demo.raw,format=raw \
	-rtc base=localtime,clock=host \
	-spice port=5924,disable-ticketing=on \
	-vga qxl \
	-usb -device usb-tablet \
	-net nic -net tap,ifname=tap0,script=no &

If I add in '-M pc-i440fx-5.2' it works again with the accelerator. If I add
in '-M q35' it does work fine with or without the accelerator.

Surprisingly without accelerator ie with tcg the default machine does seem to
get to the login prompt. Is the ACPI data tailored to indicate an
accelerator/VM or is it static? Could it be that the CPU reported by my
machine is causing the issue? With the NVMM accelerator it passes on the hosts
CPU:

cpu0: "Intel(R) Celeron(R) 2957U @ 1.40GHz"
cpu0: Intel 4th gen Core, Xeon E3-12xx v3 (Haswell) (686-class), 1396.77 MHz
cpu0: family 0x6 model 0x45 stepping 0x1 (id 0x40651)

Running with NVMM gives the following warnings that might be relevant though
doesn't seem to bother the BSDs nor Linux last time I tried and Google tells
me they are power saving related MSRs:

qemu-system-x86_64: NVMM: Unexpected RDMSR 0x611, ignored
qemu-system-x86_64: NVMM: Unexpected RDMSR 0x641, ignored
qemu-system-x86_64: NVMM: Unexpected RDMSR 0x606, ignored
qemu-system-x86_64: NVMM: Unexpected RDMSR 0x606, ignored
qemu-system-x86_64: NVMM: Unexpected RDMSR 0x641, ignored
qemu-system-x86_64: NVMM: Unexpected RDMSR 0x611, ignored

I am not sure if that makes ACPI take a different route or not.

The Windows used is
	Windows 10 Enterprise Evaluation
	Build 17763.rs5_release.180914-1434
	version 1809

The image file was downloaded pre-installed from Microsoft for Edge browser
evaluation. I used it first on Qemu 5.1 IIRC and it kept working in Qemu 5.2.

The NVMM accelerator was presented here before but is not yet committed. Its
API/construction is similar to WHPX.

As for the cause, I don't know; q35-6.0 works so why isn't pc-i440fx-6.0 ?

With regards,
Reinoud



  reply	other threads:[~2021-03-15 22:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 16:58 Windows 10 won't run on default x86_64 machine anymore Reinoud Zandijk
2021-03-15 17:19 ` Daniel P. Berrangé
2021-03-15 21:32   ` Isaku Yamahata
2021-03-15 17:53 ` Igor Mammedov
2021-03-15 22:27   ` Reinoud Zandijk [this message]
2021-03-16  1:55     ` Isaku Yamahata
2021-03-16 12:13       ` Igor Mammedov
2021-03-16 12:49         ` Paolo Bonzini
2021-03-16 13:10           ` Igor Mammedov
2021-03-16 16:49             ` Igor Mammedov
2021-03-16 17:33               ` Paolo Bonzini
2021-03-16 18:49                 ` Igor Mammedov
2021-03-16 16:27           ` Reinoud Zandijk
2021-03-16 17:38             ` Paolo Bonzini
2021-03-16 16:20       ` Reinoud Zandijk
2021-03-16 16:41       ` Reinoud Zandijk
2021-03-16 12:53     ` Igor Mammedov
2021-03-16 16:28       ` Reinoud Zandijk
2021-03-16 17:17         ` Igor Mammedov
2021-03-16 20:34           ` Igor Mammedov
2021-03-17  8:58             ` Reinoud Zandijk
2021-03-17  9:54               ` Igor Mammedov
2021-03-17 15:10               ` Reinoud Zandijk
2021-03-17 15:13             ` Reinoud Zandijk
2021-03-15 21:59 ` Michael S. Tsirkin
2021-03-15 22:05 ` Isaku Yamahata
2021-03-16 12:33   ` Igor Mammedov
2021-03-16 12:40     ` Daniel P. Berrangé
2021-03-16 13:04       ` Igor Mammedov

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=YE/fUQRiFBfrWi5W@dropje.13thmonkey.org \
    --to=reinoud@netbsd.org \
    --cc=imammedo@redhat.com \
    --cc=qemu-devel@nongnu.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.