QEMU-Devel Archive on lore.kernel.org
 help / color / Atom feed
* [Qemu-devel] [Bug 1778966] [NEW] Windows 1803 and later crashes on KVM
@ 2018-06-27 17:54 Bruce Campbell
  2018-06-27 18:16 ` [Qemu-devel] [Bug 1778966] " Bruce Campbell
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: Bruce Campbell @ 2018-06-27 17:54 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

For a bionic host, using the current public kvm modules, KVM is not
capable of booting a WindowsInsider or msdn Windows 1803 iso. In
stallign 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.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
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 iso. In
  stallign 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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Qemu-devel] [Bug 1778966] Re: Windows 1803 and later crashes on KVM
  2018-06-27 17:54 [Qemu-devel] [Bug 1778966] [NEW] Windows 1803 and later crashes on KVM Bruce Campbell
@ 2018-06-27 18:16 ` " Bruce Campbell
  2018-06-27 22:14 ` Daniel Berrange
                   ` (5 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: Bruce Campbell @ 2018-06-27 18:16 UTC (permalink / raw)
  To: qemu-devel

** Description changed:

  For a bionic host, using the current public kvm modules, KVM is not
- capable of booting a WindowsInsider or msdn Windows 1803 iso. In
- stallign from an ISO from a started windows 2016 guest results in an
- unbootable and unrepairable guest.
+ 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.

-- 
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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Qemu-devel] [Bug 1778966] Re: Windows 1803 and later crashes on KVM
  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
                   ` (4 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: Daniel Berrange @ 2018-06-27 22:14 UTC (permalink / raw)
  To: qemu-devel

This sounds like the same problem we're investigating in Fedora/RHEL
land affecting guests with EPYC CPU, or host-passthrough from an EPYC
family 17h host.  Workaround should be to use "-cpu Opteron_G5" for now

https://bugzilla.redhat.com/show_bug.cgi?id=1592276
https://bugzilla.redhat.com/show_bug.cgi?id=1593190

Looks like windows is tickling an undocumented MSR and we're trying to
find out what this MSR is supposed todo and thus how to handle it in
KVM/QEMU

** Bug watch added: Red Hat Bugzilla #1592276
   https://bugzilla.redhat.com/show_bug.cgi?id=1592276

** Bug watch added: Red Hat Bugzilla #1593190
   https://bugzilla.redhat.com/show_bug.cgi?id=1593190

-- 
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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Qemu-devel] [Bug 1778966] Re: Windows 1803 and later crashes on KVM
  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
                   ` (3 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: Bruce Campbell @ 2018-06-28 14:59 UTC (permalink / raw)
  To: qemu-devel

That is very helpful. I'll try it.

I standby to try a fix as soon as someone has one.

-- 
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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Qemu-devel] [Bug 1778966] Re: Windows 1803 and later crashes on KVM
  2018-06-27 17:54 [Qemu-devel] [Bug 1778966] [NEW] Windows 1803 and later crashes on KVM Bruce Campbell
                   ` (2 preceding siblings ...)
  2018-06-28 14:59 ` Bruce Campbell
@ 2018-06-29  2:06 ` Bruce Campbell
  2018-06-29  2:13 ` Bruce Campbell
                   ` (2 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: Bruce Campbell @ 2018-06-29  2:06 UTC (permalink / raw)
  To: qemu-devel

Regrettably opteron_g5 is not a workaround. I get a complaint that my
cpu doesn't provide xop, fma4, tbm.

I've tried a number of other cpus including nehalem, phenom and athlon
with similar results.

-- 
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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Qemu-devel] [Bug 1778966] Re: Windows 1803 and later crashes on KVM
  2018-06-27 17:54 [Qemu-devel] [Bug 1778966] [NEW] Windows 1803 and later crashes on KVM Bruce Campbell
                   ` (3 preceding siblings ...)
  2018-06-29  2:06 ` Bruce Campbell
@ 2018-06-29  2:13 ` Bruce Campbell
  2018-06-29  2:15 ` Bruce Campbell
  2019-10-12 14:05 ` Emanuele Faranda
  6 siblings, 0 replies; 8+ messages in thread
From: Bruce Campbell @ 2018-06-29  2:13 UTC (permalink / raw)
  To: qemu-devel

Opteron didn't work do to some missing features. I was able to get
nehalem to come up but that looks like the closest.

-- 
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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Qemu-devel] [Bug 1778966] Re: Windows 1803 and later crashes on KVM
  2018-06-27 17:54 [Qemu-devel] [Bug 1778966] [NEW] Windows 1803 and later crashes on KVM Bruce Campbell
                   ` (4 preceding siblings ...)
  2018-06-29  2:13 ` Bruce Campbell
@ 2018-06-29  2:15 ` Bruce Campbell
  2019-10-12 14:05 ` Emanuele Faranda
  6 siblings, 0 replies; 8+ messages in thread
From: Bruce Campbell @ 2018-06-29  2:15 UTC (permalink / raw)
  To: qemu-devel

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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [Bug 1778966] Re: Windows 1803 and later crashes on KVM
  2018-06-27 17:54 [Qemu-devel] [Bug 1778966] [NEW] Windows 1803 and later crashes on KVM Bruce Campbell
                   ` (5 preceding siblings ...)
  2018-06-29  2:15 ` Bruce Campbell
@ 2019-10-12 14:05 ` Emanuele Faranda
  6 siblings, 0 replies; 8+ messages in thread
From: Emanuele Faranda @ 2019-10-12 14:05 UTC (permalink / raw)
  To: qemu-devel

I ran into the same problem on threadripper 1900X. I was using cpu type
"host-passthough" and it crashed. I fixed the crash by disabling the MSR
with

kvm.ignore_msrs=1

as describe in https://forum.level1techs.com/t/windows-10-1803-as-guest-
with-qemu-kvm-bsod-under-install/127425/10

-- 
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


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, back to index

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2019-10-12 14:05 ` Emanuele Faranda

QEMU-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/qemu-devel/0 qemu-devel/git/0.git
	git clone --mirror https://lore.kernel.org/qemu-devel/1 qemu-devel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 qemu-devel qemu-devel/ https://lore.kernel.org/qemu-devel \
		qemu-devel@nongnu.org
	public-inbox-index qemu-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.nongnu.qemu-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git