archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <>
To: Paolo Bonzini <>,
	Sean Christopherson <>,
	Vitaly Kuznetsov <>,
	Roman Mamedov <>
Cc: Linux Kernel Mailing List <>,
	Linux Regressions <>,
	Linux KVM <>
Subject: Fwd: kvm: Windows Server 2003 VM fails to work on 6.1.44 (works fine on 6.1.43)
Date: Wed, 16 Aug 2023 16:29:32 +0700	[thread overview]
Message-ID: <> (raw)


I notice a regression report on Bugzilla [1]. Quoting from it:

> Hello,
> I have a virtual machine running the old Windows Server 2003. On kernels 6.1.44 and 6.1.45, the QEMU VNC window stays dark, not switching to any of the guest's video modes and the VM process uses only ~64 MB of RAM of the assigned 2 GB, indefinitely. It's like the VM is paused/halted/stuck before even starting. The process can be killed successfully and then restarted again (with the same result), so it is not deadlocked in kernel or the like.
> Kernel 6.1.43 works fine.
> I have also tried downgrading CPU microcode from 20230808 to 20230719, but that did not help.
> The CPU is AMD Ryzen 5900. I suspect some of the newly added mitigations may be the culprit?

See Bugzilla for the full thread.

Anyway, I'm adding it to regzbot as stable-specific regression:

#regzbot introduced: v6.1.43..v6.1.44
#regzbot title: Windows Server 2003 VM boot hang (only 64MB RAM allocated)


An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-08-16  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  9:29 Bagas Sanjaya [this message]
2023-08-16 12:27 ` Fwd: kvm: Windows Server 2003 VM fails to work on 6.1.44 (works fine on 6.1.43) Vitaly Kuznetsov
2023-08-16 13:01   ` Vitaly Kuznetsov
2023-08-16 13:41     ` Vitaly Kuznetsov
2023-08-16 16:53       ` Maxim Levitsky
2023-08-16 17:22       ` Roman Mamedov
2023-08-17  3:05 ` Fwd: " Bagas Sanjaya
2023-08-31  9:42   ` Linux regression tracking #update (Thorsten Leemhuis)

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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).