You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2023. It is now read-only.
I am trying to run qemu with intel haxm as accelerator, but the problem it is cannot boot up as soon i start the emulator with a "VCPU shutdown request" as exit message...
Host Environment
HAXM version:
v7.5.6 Windows using the signed driver.
Host OS version:
x64 Windows 1909 18363.535
Host OS architecture: x64
Host CPU model:
i7 8700k
Host RAM size:
16GB
(Optional) Host computer model: (custom, gigabyte... does even matter?)
Guest Environment
QEMU version:
4.2.0
Guest OS version:
Windows 10 Professional x64
Guest OS architecture: x64
(tried first): "Icelake-Client-v1"
(so i downgraded the qemu version to 3.0.0 using "core2duo" )
Hi @ripeip , so far window 10 guest is not supported well with HAXM and we are still working on this feature now. You can refer to the progress from the known issue #204 .
I am trying to run qemu with intel haxm as accelerator, but the problem it is cannot boot up as soon i start the emulator with a "VCPU shutdown request" as exit message...
Host Environment
v7.5.6 Windows using the signed driver.
x64 Windows 1909 18363.535
i7 8700k
16GB
Guest Environment
4.2.0
Windows 10 Professional x64
(tried first): "Icelake-Client-v1"
(so i downgraded the qemu version to 3.0.0 using "core2duo" )
Command line
qemu-system-x86_64 -d guest_errors,out_asm,in_asm,op,op_opt,op_ind,int,exec,cpu,fpu,mmu,pcall,cpu_reset,unimp,page,nochain -cpu core2duo -smp 4 -accel hax -drive file=w10.img,index=0,media=disk,format=raw -cdrom "E:\test\W10x64ProEn-UK.iso" -m 4G -L Bios -usbdevice mouse -usbdevice keyboard -boot menu=on -rtc base=localtime,clock=host -name windows
Steps to reproduce the behavior:
Expected Behavior
able to initialize with the os installation.
Diagnostic Information
Host crash dump:
HAXM log (driver output):
Screenshots:
The text was updated successfully, but these errors were encountered: