As far as I know, it's possible to run Windows 10 in qemu-system-aarch64 with hardware acceleration on Rockchip RK3399 SoC.
Including any particular devices you'd want to make sure are supportedĪs it was said above by probably the easiest and cheapest way would be testing drivers in QEMU with KVM acceleration. And since the emulation layer works only for user-mode apps, we need ARM64 versions of Npcap drivers and services. Latest insider build of Windows 10 ARM64 allows to run programs compiled for x86 and 圆4 architectures via emulation, so it potentially enables to use a wide variety of security auditing and penetration testing tools such as Nmap, Wireshark, Cain & Abel, Intercepter-NG, Router Scan, and much more.Īll the tools outlined above heavily relies on Packet Capture API which Npcap implements. We're wondering how much Nmap/Npcap user interest there is in supporting Windows 10 ARM64? If it is something you want for a specific reason, please comment and describe your use case
In fact, I do have the NpCap driver installed on a Windows 10 ARM64 VM running under KVM on an AMD Seattle engineering system, with Linux 4.19 as VM host – I can attest the driver works well also in this setup. In case you already have ARM64 hardware with KVM capability, you may be able to reuse it for development and validation of Windows 10 ARM64 as well. That said, Windows 10 ARM64 unofficially works well under QEMU/KVM. We’d certainly like to make sure software works goon on these. * any particular devices you'd want to make sure are supportedĮven though Windows 10 works in many devices, as long as they obey ARMH, UEFI and ACPI specs, officially is it only supported on Qualcomm 835 and 850.
Long story short: we do have people asking for this, both individual power users as well as enterprises. Unfortunately Win10Pcap is not feature-par with the original WinpCap, so I was about to tackle the original old code this time round, when I became aware of nmap’s team recent work on NpCap (thank you for that!). I initially ported Win10Pcap (another fork of WinPcap to NDIS6x) to ARM64 and also published that. Myself, personally, would like the TP-Link home network solution tools to work as well. One of these customers was actually Cisco Systems to whom ARM64 devices are attractive, especially when considering a lot of their engineers work out all day and much appreciate the all-day battery life.
The issue was first reported to out team (Win10 ARM64) by request from real customers that wanted WireShark to work on these devices. * We're wondering how much Nmap/Npcap user interest there is in supporting Windows 10 ARM64?