Make sure to leave a ⭐ :)
This is Hangover, a project started by André Zwing and Stefan Dösinger in 2016 that currently can run x86_32 Windows applications on aarch64 Wine.
Hangover uses various emulators as DLLs (pick one that suits your needs, e.g. works for you) to only emulate the application you want to run instead of emulating a complete Wine installation.
As soon as the application does a Windows/Wine system call, say NtUserCreateWindowEx, it's executed outside the emulator (read non-emulated, fast, native). Even better, everything Unix related is never emulated.
In short, we break out of emulation at the win32 syscall or wine unix call level for performance reasons, which is enabled by the WoW64 support in Wine.
While the overall stability was improved, expect issues.
For Benchmarks see here. They show that the Hangover approach works as expected, as only emulating the application instead of a complete Wine installation has benefits. It's especially visible with box64cpu vs. Wine running under Box64.
Current main focus is to run i386 Windows applications on ARM64 Linux, but it's also possible to run ARM32 Windows applications on x86_64 Linux. I also started working on RISC-V Linux support.
PPC64le isn't supported anymore and won't be added back in the near future. Same for running x86_64 applications, though it might be added back as soon as the ARM64EC support in Wine is ready. If you need those features, have a look at older releases before 0.8.x.
Emulator integrations:
- QEMU: Has the most issues and is by far the slowest option
- FEX: Available as Unix and PE
- Box64: Mostly done, but depends on the early 32-bit emulation of Box64
- Blink: started, not part of this repository yet
A paid preview is available with currently the following features coming soon:
- Updated Wine
- Updated FEX
- Updated Box64
- Updated Packages
A Discord Server is available for contributors and financial supporters (see point 8 below). It provides advanced user support, development discussions and more.
Debian 11 and Debian 12 (also usable for Raspbian, Armbian, Ubuntu, ...) can now be built with Github Actions and Gitlab CI.
For build instructions see here.
You can add the following environment variables:
- HODLL to select the emulator dll:
- wow64cpu.dll for "native" i386 mode on x86_64
- wowarmhw.dll for ARM emulation (Qemu)
- xtajit.dll for i386 emulation (Qemu)
- fexcore.dll for i386 emulation (FEX, Unix)
- libwow64fex.dll for i386 emulation (FEX, PE)
- box64cpu.dll for i386 emulation (Box64)
- HOLIB to set full path of the library, e.g. HOLIB=/path/to/libqemu-i386.so
- QEMU_LOG to set QEMU log channels, find some options here.
box64cpu.dll currently is the default for i386 emulation, so it's simply:
$ wine your_x86_application.exe
You might have better results with FEX for the moment.
Until the critical section issue is solved it is highly recomended to limit execution to 1 core with "taskset -c 1" for Qemu emulation:
$ HODLL=xtajit.dll taskset -c 1 wine your_x86_application.exe
$ HODLL=wowarmhw.dll taskset -c 1 wine your_arm_application.exe
$ HODLL=fexcore.dll wine your_x86_application.exe
$ HODLL=libwow64fex.dll wine your_x86_application.exe
- Get more applications running
- QEMU: Investigate CriticalSection issues (just timing?)
Become a financial contributor and help me sustain this project:
https://www.patreon.com/andre_opensource
https://liberapay.com/andre_opensource
https://ko-fi.com/andre_opensource
Become a hardware contributor and help me sustain this project: