[20250411] ZenEMU - QEMU启动测试器

wintoflash · 发表于 2025-3-15 09:56:59

本帖最后由 wintoflash 于 2025-4-11 20:34 编辑

给 QEMU 写了个简单图形界面以方便启动测试。首个支持直接测试WIM的启动测试器。

支持 x86 BIOS、IA32 UEFI、x64 UEFI、ARM32 UEFI、ARM64 UEFI。
支持测试虚拟磁盘/光盘/软盘镜像、物理磁盘/光盘、Linux内核、WIM镜像、TFTP/HTTP网启等。
预览

启动 arm64 winpe：

源码
https://github.com/a1ive/ZenEmu
下载
[说明] zemu.zip 为不包含 QEMU 的版本，zemu_qemu.zip 为包含了 QEMU 开箱即用的版本。
[GitHub] https://github.com/a1ive/ZenEmu/releases 可使用 kkgithub 加速
[百度云] https://pan.baidu.com/s/1X1DWe42uuFL00zDuWu5E9g?pwd=zemu 提取码: zemu

注意事项
此应用仅支持64位 (兼容性 >= Vista，未测试)。
QEMU 不支持带逗号(,)和非 ASCII 字符的路径。
无管理员权限时不能测试物理磁盘/光盘。

目前问题
音频(Intel HDA)输出不可用。
x86 不支持 Hyper-V 虚拟化。

skyrusher · 发表于 2 小时前

我现在还在用古老的Qemu Manager7.0+haxm-7.7.1组合，haxm最后一个版本会报错，Intel宣布停止维护后没人改。

肉仔 · 发表于 3 小时前

这个是pe吗

2011yaya2007777 · 发表于 3 小时前

经测试，HTTP服务完美支持断点续传！感谢wintoflash大。

就如以前反馈的，第一次网起（新打开主界面），仍然存在问题，不过这次提示超时。
如果关闭副界面（主界面不关闭），重启，则没有这个问题。
不知是QEMU的问题，还是HTTP的问题。不要管他了。

AYE-阿业 · 发表于 7 小时前

谢谢分享

mygamexxx · 发表于 7 小时前

感谢wintoflash大，新版本PXE-HTTP网启，使用G4E以naboot和map两种方式均能顺利启动至PE桌面。

hu2036646 · 发表于 11 小时前

感谢分享

2011yaya2007777 · 发表于 11 小时前

是的，我已经知道了。

wintoflash · 发表于 11 小时前

2011yaya2007777 发表于 2025-8-28 08:18
是个好消息。
网起时提示：createprocess failed

你没放qemu本体吧

2011yaya2007777 · 发表于 12 小时前

本帖最后由 2011yaya2007777 于 2025-8-28 09:16 编辑

是个好消息。

wintoflash · 发表于昨天 22:13

2011yaya2007777 发表于 2025-7-2 17:47
报告一个诡异的事。
使用ZenEmu-0.2.0自带的http功能网起，首次使用（点桌面快捷图标加载主程序，需设置“ ...

https://github.com/a1ive/ZenEmu/releases/tag/latest
在AI的帮助下添加了断点续传的支持。
现在测试虽然会有http->poll的报错，但是能成功wimboot/ntboot启动到桌面。

--- HTTP Range Request Tester ---
Server: 127.0.0.1:80
Server Root: pxe\
Setup: Test file 'pxe\\http_test_file.bin' created successfully (256 bytes).
---------------------------------
--> Running Test: [Full file (no range)]
[PASS] Status Code: 200
[PASS] Content-Length: 256
[PASS] Body Content: Data verified successfully.
--> Test Result: PASS
--> Running Test: [bytes=64-83]
[PASS] Status Code: 206
[PASS] Content-Length: 20
[PASS] Body Content: Data verified successfully.
--> Test Result: PASS
--> Running Test: [bytes=64-]
[PASS] Status Code: 206
[PASS] Content-Length: 192
[PASS] Body Content: Data verified successfully.
--> Test Result: PASS
--> Running Test: [bytes=-8]
[PASS] Status Code: 206
[PASS] Content-Length: 8
[PASS] Body Content: Data verified successfully.
--> Test Result: PASS
--> Running Test: [bytes=0-]
[PASS] Status Code: 206
[PASS] Content-Length: 256
[PASS] Body Content: Data verified successfully.
--> Test Result: PASS
--> Running Test: [bytes=0-255]
[PASS] Status Code: 206
[PASS] Content-Length: 256
[PASS] Body Content: Data verified successfully.
--> Test Result: PASS
--> Running Test: [bytes=0-0]
[PASS] Status Code: 206
[PASS] Content-Length: 1
[PASS] Body Content: Data verified successfully.
--> Test Result: PASS
--> Running Test: [bytes=0-1]
[PASS] Status Code: 206
[PASS] Content-Length: 2
[PASS] Body Content: Data verified successfully.
--> Test Result: PASS
--> Running Test: [bytes=1-1]
[PASS] Status Code: 206
[PASS] Content-Length: 1
[PASS] Body Content: Data verified successfully.
--> Test Result: PASS
---------------------------------
Teardown: Test file 'pxe\\http_test_file.bin' deleted.
--- Test Summary ---
Tests Passed: 9
Tests Failed: 0
--------------------

复制代码

这是单独的ews http server，和zemu内置的一样，但是能在cmd实时输出日志：

ews.zip (52.31 KB, 下载次数: 2)

ews.exe --root=pxe\
Try http://127.0.0.1:80 if you bound to all addresses or the localhost.
New connection from 127.0.0.1:61577...
Request from 127.0.0.1:61577: HEAD to /boot/wimboot HTTP version HTTP/1.1
Request: /boot/wimboot
Looking up file path 'pxe\/boot/wimboot' to serve request '/boot/wimboot' (originally encoded '/boot/wimboot'). We believe the path suffix is 'boot/wimboot'...
Detected MIME type 'application/binary' for file 'pxe\/boot/wimboot'
127.0.0.1:61577: Responded with HTTP 200 OK length 50963
Connection from 127.0.0.1:61577 closed
New connection from 127.0.0.1:61578...
Request from 127.0.0.1:61578: GET to /boot/wimboot HTTP version HTTP/1.1
Request: /boot/wimboot
Looking up file path 'pxe\/boot/wimboot' to serve request '/boot/wimboot' (originally encoded '/boot/wimboot'). We believe the path suffix is 'boot/wimboot'...
Detected MIME type 'application/binary' for file 'pxe\/boot/wimboot'
127.0.0.1:61578: Responded with HTTP 200 OK length 51012
Connection from 127.0.0.1:61578 closed
New connection from 127.0.0.1:61579...
Request from 127.0.0.1:61579: HEAD to /boot/wimboot HTTP version HTTP/1.1
Request: /boot/wimboot
Looking up file path 'pxe\/boot/wimboot' to serve request '/boot/wimboot' (originally encoded '/boot/wimboot'). We believe the path suffix is 'boot/wimboot'...
Detected MIME type 'application/binary' for file 'pxe\/boot/wimboot'
127.0.0.1:61579: Responded with HTTP 200 OK length 50963
Connection from 127.0.0.1:61579 closed
New connection from 127.0.0.1:61580...
Request from 127.0.0.1:61580: GET to /boot/wimboot HTTP version HTTP/1.1
Request: /boot/wimboot
Looking up file path 'pxe\/boot/wimboot' to serve request '/boot/wimboot' (originally encoded '/boot/wimboot'). We believe the path suffix is 'boot/wimboot'...
Detected MIME type 'application/binary' for file 'pxe\/boot/wimboot'
127.0.0.1:61580: Responded with HTTP 200 OK length 51012
Connection from 127.0.0.1:61580 closed
New connection from 127.0.0.1:61581...
Request from 127.0.0.1:61581: HEAD to /boot/bootmgfw.efi HTTP version HTTP/1.1
Request: /boot/bootmgfw.efi
Looking up file path 'pxe\/boot/bootmgfw.efi' to serve request '/boot/bootmgfw.efi' (originally encoded '/boot/bootmgfw.efi'). We believe the path suffix is 'boot/bootmgfw.efi'...
Detected MIME type 'application/binary' for file 'pxe\/boot/bootmgfw.efi'
Unable to satisfy request for '/boot/bootmgfw.efi' because there was an error sending bytes. 'pxe\/boot/bootmgfw.efi' No error = 0
Connection from 127.0.0.1:61581 closed
New connection from 127.0.0.1:61582...
Request from 127.0.0.1:61582: HEAD to /boot/bcd HTTP version HTTP/1.1
Request: /boot/bcd
Looking up file path 'pxe\/boot/bcd' to serve request '/boot/bcd' (originally encoded '/boot/bcd'). We believe the path suffix is 'boot/bcd'...
Detected MIME type 'application/binary' for file 'pxe\/boot/bcd'
127.0.0.1:61582: Responded with HTTP 200 OK length 28807
Connection from 127.0.0.1:61582 closed
New connection from 127.0.0.1:61583...
Request from 127.0.0.1:61583: HEAD to /boot/boot.sdi HTTP version HTTP/1.1
Request: /boot/boot.sdi
Looking up file path 'pxe\/boot/boot.sdi' to serve request '/boot/boot.sdi' (originally encoded '/boot/boot.sdi'). We believe the path suffix is 'boot/boot.sdi'...
Detected MIME type 'text/plain' for file 'pxe\/boot/boot.sdi'
Unable to satisfy request for '/boot/boot.sdi' because there was an error sending bytes. 'pxe\/boot/boot.sdi' No error = 0
Connection from 127.0.0.1:61583 closed
New connection from 127.0.0.1:61584...
Request from 127.0.0.1:61584: HEAD to /boot/10PE.WIM HTTP version HTTP/1.1
Request: /boot/10PE.WIM
Looking up file path 'pxe\/boot/10PE.WIM' to serve request '/boot/10PE.WIM' (originally encoded '/boot/10PE.WIM'). We believe the path suffix is 'boot/10PE.WIM'...
Detected MIME type 'application/binary' for file 'pxe\/boot/10PE.WIM'
Unable to satisfy request for '/boot/10PE.WIM' because there was an error sending bytes. 'pxe\/boot/10PE.WIM' No error = 0
Connection from 127.0.0.1:61584 closed
New connection from 127.0.0.1:61585...
Request from 127.0.0.1:61585: HEAD to /boot/bootmgfw.efi HTTP version HTTP/1.1
Request: /boot/bootmgfw.efi
Looking up file path 'pxe\/boot/bootmgfw.efi' to serve request '/boot/bootmgfw.efi' (originally encoded '/boot/bootmgfw.efi'). We believe the path suffix is 'boot/bootmgfw.efi'...
Detected MIME type 'application/binary' for file 'pxe\/boot/bootmgfw.efi'
Unable to satisfy request for '/boot/bootmgfw.efi' because there was an error sending bytes. 'pxe\/boot/bootmgfw.efi' No error = 0
Connection from 127.0.0.1:61585 closed
New connection from 127.0.0.1:61586...
Request from 127.0.0.1:61586: GET to /boot/bootmgfw.efi HTTP version HTTP/1.1
Request: /boot/bootmgfw.efi
Looking up file path 'pxe\/boot/bootmgfw.efi' to serve request '/boot/bootmgfw.efi' (originally encoded '/boot/bootmgfw.efi'). We believe the path suffix is 'boot/bootmgfw.efi'...
Detected MIME type 'application/binary' for file 'pxe\/boot/bootmgfw.efi'
127.0.0.1:61586: Responded with HTTP 200 OK length 1250526
Connection from 127.0.0.1:61586 closed
New connection from 127.0.0.1:61587...
Request from 127.0.0.1:61587: HEAD to /boot/bcd HTTP version HTTP/1.1
Request: /boot/bcd
Looking up file path 'pxe\/boot/bcd' to serve request '/boot/bcd' (originally encoded '/boot/bcd'). We believe the path suffix is 'boot/bcd'...
Detected MIME type 'application/binary' for file 'pxe\/boot/bcd'
127.0.0.1:61587: Responded with HTTP 200 OK length 28807
Connection from 127.0.0.1:61587 closed
New connection from 127.0.0.1:61588...
Request from 127.0.0.1:61588: GET to /boot/bcd HTTP version HTTP/1.1
Request: /boot/bcd
Looking up file path 'pxe\/boot/bcd' to serve request '/boot/bcd' (originally encoded '/boot/bcd'). We believe the path suffix is 'boot/bcd'...
Detected MIME type 'application/binary' for file 'pxe\/boot/bcd'
127.0.0.1:61588: Responded with HTTP 200 OK length 28856
Connection from 127.0.0.1:61588 closed
New connection from 127.0.0.1:61589...
Request from 127.0.0.1:61589: HEAD to /boot/boot.sdi HTTP version HTTP/1.1
Request: /boot/boot.sdi
Looking up file path 'pxe\/boot/boot.sdi' to serve request '/boot/boot.sdi' (originally encoded '/boot/boot.sdi'). We believe the path suffix is 'boot/boot.sdi'...
Detected MIME type 'text/plain' for file 'pxe\/boot/boot.sdi'
Unable to satisfy request for '/boot/boot.sdi' because there was an error sending bytes. 'pxe\/boot/boot.sdi' No error = 0
Connection from 127.0.0.1:61589 closed
New connection from 127.0.0.1:61590...
Request from 127.0.0.1:61590: GET to /boot/boot.sdi HTTP version HTTP/1.1
Request: /boot/boot.sdi
Looking up file path 'pxe\/boot/boot.sdi' to serve request '/boot/boot.sdi' (originally encoded '/boot/boot.sdi'). We believe the path suffix is 'boot/boot.sdi'...
Detected MIME type 'text/plain' for file 'pxe\/boot/boot.sdi'
127.0.0.1:61590: Responded with HTTP 200 OK length 983219
Connection from 127.0.0.1:61590 closed
New connection from 127.0.0.1:61591...
Request from 127.0.0.1:61591: HEAD to /boot/10PE.WIM HTTP version HTTP/1.1
Request: /boot/10PE.WIM
Looking up file path 'pxe\/boot/10PE.WIM' to serve request '/boot/10PE.WIM' (originally encoded '/boot/10PE.WIM'). We believe the path suffix is 'boot/10PE.WIM'...
Detected MIME type 'application/binary' for file 'pxe\/boot/10PE.WIM'
Unable to satisfy request for '/boot/10PE.WIM' because there was an error sending bytes. 'pxe\/boot/10PE.WIM' No error = 0
Connection from 127.0.0.1:61591 closed
New connection from 127.0.0.1:52457...
Request from 127.0.0.1:52457: GET to /boot/10PE.WIM HTTP version HTTP/1.1
Request: /boot/10PE.WIM
Looking up file path 'pxe\/boot/10PE.WIM' to serve request '/boot/10PE.WIM' (originally encoded '/boot/10PE.WIM'). We believe the path suffix is 'boot/10PE.WIM'...
Detected MIME type 'application/binary' for file 'pxe\/boot/10PE.WIM'
Unable to satisfy request for '/boot/10PE.WIM' because there was an error sending bytes. 'pxe\/boot/10PE.WIM' No error = 0
Connection from 127.0.0.1:52457 closed
New connection from 127.0.0.1:53877...
Request from 127.0.0.1:53877: GET to /boot/10PE.WIM HTTP version HTTP/1.1
Request: /boot/10PE.WIM
Looking up file path 'pxe\/boot/10PE.WIM' to serve request '/boot/10PE.WIM' (originally encoded '/boot/10PE.WIM'). We believe the path suffix is 'boot/10PE.WIM'...
Detected MIME type 'application/binary' for file 'pxe\/boot/10PE.WIM'
Unable to satisfy request for '/boot/10PE.WIM' because there was an error sending bytes. 'pxe\/boot/10PE.WIM' No error = 0
Connection from 127.0.0.1:53877 closed
New connection from 127.0.0.1:50673...
Request from 127.0.0.1:50673: GET to /boot/10PE.WIM HTTP version HTTP/1.1
Request: /boot/10PE.WIM
Looking up file path 'pxe\/boot/10PE.WIM' to serve request '/boot/10PE.WIM' (originally encoded '/boot/10PE.WIM'). We believe the path suffix is 'boot/10PE.WIM'...
Detected MIME type 'application/binary' for file 'pxe\/boot/10PE.WIM'
127.0.0.1:50673: Responded with HTTP 200 OK length 39506989
Connection from 127.0.0.1:50673 closed

复制代码

shuaile · 发表于 2025-8-16 06:56:18

我看看是什么

saiz · 发表于 2025-7-10 23:27:05

比VMWare還讚!!
我做出來的WIM在VM中測時常會出現XX檔問題 0xc000221
都搞不清為什麼...
現場用zenemu就能正常運作!

2011yaya2007777 · 发表于 2025-7-2 20:15:24

set http

wintoflash · 发表于 2025-7-2 20:09:23

2011yaya2007777 发表于 2025-7-2 17:53
附件-测试文件，不包含10pe.wim。在G4E环境测试。

怎么写菜单才能让g4e通过http读文件？如果不加(http)的话好像只从tftp读文件？

2011yaya2007777 · 发表于 2025-7-2 17:53:17

本帖最后由 2011yaya2007777 于 2025-7-2 18:38 编辑

附件-测试文件，不包含10pe.wim。在G4E环境测试。

2011yaya2007777 · 发表于 2025-7-2 17:47:14

报告一个诡异的事。
使用ZenEmu-0.2.0自带的http功能网起，首次使用（点桌面快捷图标加载主程序，需设置“文件夹”及“启动文件”），网起总是失败。点“终止”后再点“启动”，则成功。
起初是考虑g4e的ntboot的问题，后来测试了wimboot方案，也是失败。
如果不使用ZenEmu-0.2.0自带的http功能，而是使用EasyWebSvr，则没有这些问题。

反复测试（需点主程序ZenEMU右上角的×关闭主程序，再点桌面快捷图标加载主程序，重新设置“文件夹”及“启动文件”），均如此。

启动菜单：
title 使用 wimboot 启动服务端 10PE.WIM
kernel /boot/wimboot
initrd @bootx64.efi=/boot/bootmgfw.efi @bcd=/boot/bcd @boot.sdi=/boot/boot.sdi @boot.wim=/boot/10PE.WIM
boot

title 使用 ntboot 启动服务端 10PE.WIM
/efi/grub/ext/ntboot /boot/10PE.WIM
boot

失败截图：

liwei_show · 发表于 2025-6-9 20:44:25

感谢大佬分享

yxing365 · 发表于 2025-4-25 08:30:24

好家伙，又看到了黎明的曙光

qinghg2019 · 发表于 2025-4-21 17:50:59

这个得支持

wintoflash · 发表于 2025-4-21 16:48:57

mygamexxx 发表于 2025-4-19 15:05
将临时目录改加英文名后，运行正常了。
建议：qemu目录中保留qemu-img.exe，就一个文件，用于转换img为v ...

已经在考虑为qemu-img的主要功能写个gui了。

mygamexxx · 发表于 2025-4-19 15:05:52

本帖最后由 mygamexxx 于 2025-4-19 15:20 编辑

wintoflash 发表于 2025-4-19 14:40
X64和AA64不要改。。。

将临时目录改加英文名后，运行正常了。
建议：qemu目录中保留qemu-img.exe，就一个文件，用于转换img为vmdk磁盘，用于虚拟硬盘测试。

我用一个批处理zemu_IMG2VMDK.bat放在zenEMU目录中转换。可以在程序中增加这个小功能吗？
::防止中文乱码
chcp 65001
::进入当前目录
%~d0
cd %~dp0qemu
qemu-img.exe convert -O vmdk f:\imgs\ezpe66401.img f:\imgs\ezpe66401.vmdk
::运行后保持界面一直显示
cmd /k

wintoflash · 发表于 2025-4-19 14:40:20

mygamexxx 发表于 2025-4-19 13:47
这个软件原理是修改注册表。修改ini后出现错误如图

X64和AA64不要改。。。

mygamexxx · 发表于 2025-4-19 13:47:18

本帖最后由 mygamexxx 于 2025-4-19 14:07 编辑

wintoflash 发表于 2025-4-19 06:27
不知道这个软件是什么原理，不敢乱试。
点左下角按钮保存ini配置，然后把ini里面的qemu文件夹和X64_EFI. ...

这个软件原理是修改注册表。修改ini后出现错误如图

wintoflash · 发表于 2025-4-19 06:27:36

mygamexxx 发表于 2025-4-18 22:49
请教wintoflash大：下载zemu_qemu.zip解压至D:\zenEMU目录后，以管理员身份运行zenEMU，启动后不出QEMU窗 ...

不知道这个软件是什么原理，不敢乱试。
点左下角按钮保存ini配置，然后把ini里面的qemu文件夹和X64_EFI.qcow2之类的全改成绝对路径试试。

mygamexxx · 发表于 2025-4-18 22:49:33

本帖最后由 mygamexxx 于 2025-4-18 23:05 编辑

wintoflash 发表于 2025-4-18 07:41
这个是qemu的依赖啊，与zenemu无关。

请教wintoflash大：下载zemu_qemu.zip解压至D:\zenEMU目录后，以管理员身份运行zenEMU，启动后不出QEMU窗口。直接以管理员身份运行D:\zenEMU\qemu目录下的qemu-system-x86_64w.exe，能正常出QEMU窗口。

是什么原因？系统都重新安装了还是不行。试了0.1.0与0.2.0版都一样，原来运行都没问题的。
主要区别是用了下图的工具，移动了用户目录。

燕飞龙 · 发表于 2025-4-18 08:47:49

感谢分享

wy250405lt · 发表于 2025-4-18 08:03:33

谢谢分享

wintoflash · 发表于 2025-4-18 07:41:40

mygamexxx 发表于 2025-4-17 12:44
尝试在WIN10PE下运行，提示缺少OPENGL32.DLL和GLU32.DLL，从WINDOWS10系统目录中复制这两个文件到PE系统目 ...

这个是qemu的依赖啊，与zenemu无关。

mygamexxx · 发表于 2025-4-17 12:44:55

尝试在WIN10PE下运行，提示缺少OPENGL32.DLL和GLU32.DLL，从WINDOWS10系统目录中复制这两个文件到PE系统目录，再运行，提示下图中，无法定位程序输入点；点击屏幕截图，提示下图中Could not find QEMU window。

mygamexxx · 发表于 2025-4-17 12:23:57

本帖最后由 mygamexxx 于 2025-4-17 12:26 编辑

遇到一个莫名其妙的问题：WINDOWS10系统变化是更改了用户目录设置(目前为d:\Users，原来为d:\USER)，zenEMU就运行有问题了，现象是点击启动后，没有出现QEMU窗口。原来没问题的。程序以管理员身份运行。

日志："qemu\qemu-system-x86_64w.exe" -drive if=pflash,file="D:\ZenEMU\X64_EFI.qcow2",snapshot=on -cpu max -accel tcg,thread=multi -smp 4 -M q35,kernel-irqchip=on -m 4096 -device vmware-svga -device usb-ehci -device usb-kbd -device usb-tablet -nic user,model=rtl8139,mac=52:01:8D:95:24:6C -drive file="F:\VM-MBR.vmdk",snapshot=on,index=0,media=disk -boot c,splash-time=1,strict=on

		自动登录	找回密码
密码			注册

[原创] [20250411] ZenEMU - QEMU启动测试器

点评

评分

点评

点评

点评

点评

点评

点评

点评

点评

点评

点评

浏览过的版块