From: Bruce Campbell <yakman2020@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1778966] Re: Windows 1803 and later crashes on KVM
Date: Fri, 29 Jun 2018 02:15:43 -0000 [thread overview]
Message-ID: <153023854361.18330.4923638668881963383.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 153012207304.7182.2374266143525192096.malonedeb@soybean.canonical.com
Is there any way to define a new CPU model that isn't EPYC (maybe
ryzen?) but is feature compatible with the threadripper?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1778966
Title:
Windows 1803 and later crashes on KVM
Status in QEMU:
New
Bug description:
For a bionic host, using the current public kvm modules, KVM is not
capable of booting a WindowsInsider or msdn Windows 1803 Windows
Server iso. In snstalling from an ISO from a started windows 2016
guest results in an unbootable and unrepairable guest.
The hardware is a threadripper 1920x with 32GB of main memory, disk
mydigital BPX SSD and WD based 4 column RAID 5 via mdadm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1778966/+subscriptions
next prev parent reply other threads:[~2018-06-29 2:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 17:54 [Qemu-devel] [Bug 1778966] [NEW] Windows 1803 and later crashes on KVM Bruce Campbell
2018-06-27 18:16 ` [Qemu-devel] [Bug 1778966] " Bruce Campbell
2018-06-27 22:14 ` Daniel Berrange
2018-06-28 14:59 ` Bruce Campbell
2018-06-29 2:06 ` Bruce Campbell
2018-06-29 2:13 ` Bruce Campbell
2018-06-29 2:15 ` Bruce Campbell [this message]
2019-10-12 14:05 ` Emanuele Faranda
2020-11-12 14:14 ` Thomas Huth
2021-04-22 17:29 ` Thomas Huth
2021-04-23 4:17 ` Launchpad Bug Tracker
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=153023854361.18330.4923638668881963383.malone@chaenomeles.canonical.com \
--to=yakman2020@gmail.com \
--cc=1778966@bugs.launchpad.net \
--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 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).