Hi, I received an email yesterday (content below) - and it worked! Not sure why it's not here also (and why only via email), but let me share, hope this helps! And BTW, when I say worked ... I applied this to the latest master (locally), addreses the issue. So add this in to the master (formally)?
Thanks! ================================ at the moment you need this patch at https://lists.nongnu.org/archive/html/qemu-devel/2020-03/msg06831.html But I can't see why v4.2.0 doesn't work on your system. The bug was introduced later. > Basically, just get a window to open, with acceleration enabled ... I > get, Open the vm device error:/dev/hax_vm/vm00, ec:3 Failed to open vm > 0 Failed to create HAX VM No accelerator found. > ec:3 is ERROR_PATH_NOT_FOUND -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1871250 Title: Failed to create HAX VM Status in QEMU: New Bug description: Hi, I'm running the latest (master) of QEMU, though the version doesn't seem to matter - I also checked back to v4.2.0, exactly the same issue. And this isn't about the VM (guest), if I even just try to run, > "c:\Program Files\qemu\qemu-system-x86_64.exe" -accel hax Basically, just get a window to open, with acceleration enabled ... I get, Open the vm device error:/dev/hax_vm/vm00, ec:3 Failed to open vm 0 Failed to create HAX VM No accelerator found. But I checked - I have installed Intel HAXM, and verified it's running, > sc query intelhaxm SERVICE_NAME: intelhaxm TYPE : 1 KERNEL_DRIVER STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 Just remove the accelerator (-accel hax), and I get a window - so this is related to QEMU being able to contact / use the accelerator. Help!?!? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1871250/+subscriptions
