[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
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 180
** Bug watch removed: Red Hat Bugzilla #1592276
https://bugzilla.redhat.com/show_bug.cgi?id=1592276
** Bug watch removed: 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
The QEMU project is currently considering to move its bug tracking to another
system. For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the
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 rece
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
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
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 subscr
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
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_bu
** 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 Window
10 matches
Mail list logo
