You are not logged in.
Hello,
I was using Archlinux as host virtualisation for a Windows 7 32bits guest using QEMU with KVM acceleration.
After upgrading my ArchLinux system to 4.18.10-arch1-1-ARCH, launching the guest Windows 7 display a blue screen (BSOD) with error 0x0000007b.
In order to make things working I must suppress this command line arguments:
-enable-kvm -cpu host
But of course, without KVM acceleration, Windows 7 become too slow to be usable.
Is anyone have an explanation and/or a solution ?
Offline
Can you try latest kernel available in Arch Linux (4.18.11.arch1-1 or better 4.18.12.arch1-1)? What is the latest kernel release and or Qemu version that works?
Offline
Here are my investigations:
- upgrading from 4.18.10-arch1-1 to 4.18.11.arch1-1 doesn't solved the problem
- downgrading to Linux kernel 4.18.3-arch1-1 with qemu 2.12.1-1 SOLVE the problem
So it may be a problem into QEMU from version 2.12.1 to 3.0.0 or into Linux kernel kvm_intel module or something between QEMU and KVM kernel module.
As I would like to be up to date with my ArchLinux version, have you any suggestion ?
Offline
I have a 32bit Win7 install that still works with kernel 4.18.12 and qemu 3.0.0-2.
It might be useful know to know the model and of your cpu and the microcode revision you are using.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Hello R00KIE,
Your remark is interesting and here are my investigations:
Working config A
- intel-ucode 20180807-1
microcode: microcode updated early to revision 0xa0b, date = 2010-09-28
microcode: sig=0x1067a, pf=0x1, revision=0xa0b
microcode: Microcode Update Driver: v2.2.
Not working config B
- intel-ucode 20180807.a-1
Using intel-ucode 20180807.a-1 with config A still work perfectly. So it seems that microcode is not the problem.
By the way, the host CPU is:
intel(R) Core(TM)2 Duo CPU E8400
Any other tracks ? Should I make a report bug ?
Offline