From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 217799] New: kvm: Windows Server 2003 VM fails to work on 6.1.44 (works fine on 6.1.43)
Date: Wed, 16 Aug 2023 08:52:59 +0000 [thread overview]
Message-ID: <bug-217799-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217799
Bug ID: 217799
Summary: kvm: Windows Server 2003 VM fails to work on 6.1.44
(works fine on 6.1.43)
Product: Virtualization
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: rm+bko@romanrm.net
Regression: No
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?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-08-16 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 8:52 bugzilla-daemon [this message]
2023-08-16 9:04 ` [Bug 217799] kvm: Windows Server 2003 VM fails to work on 6.1.44 (works fine on 6.1.43) bugzilla-daemon
2023-08-16 9:22 ` bugzilla-daemon
2023-08-16 10:58 ` bugzilla-daemon
2023-08-16 11:17 ` [Bug 217799] kvm: Speculative RAS Overflow mitigation breaks old Windows guest VMs bugzilla-daemon
2023-08-16 13:50 ` bugzilla-daemon
2023-08-16 17:23 ` bugzilla-daemon
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=bug-217799-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.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