diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:34:26 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-06-30 12:35:44 +0000 |
| commit | 25f8033d556aa17afaea4a5196ea7a69fe248320 (patch) | |
| tree | 0f056db167683be54ea1e5e72d29d6069af55e7d /results/classifier/deepseek-2-tmp/output/hypervisor/1887 | |
| parent | 8e6da29e4ee5fc14bc1cc816a24f21271f14090d (diff) | |
| download | emulator-bug-study-25f8033d556aa17afaea4a5196ea7a69fe248320.tar.gz emulator-bug-study-25f8033d556aa17afaea4a5196ea7a69fe248320.zip | |
add new temporary deepseek-r1:14b results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/1887')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/output/hypervisor/1887 | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/1887 b/results/classifier/deepseek-2-tmp/output/hypervisor/1887 new file mode 100644 index 00000000..01dfec3d --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/hypervisor/1887 @@ -0,0 +1,10 @@ + +Window VM failed to resume when using GPU passthrough(GVT-d) on Intel platform if add 'hv-stimer' option, seems like it happened after V6.2.0 +Description of problem: +Windows VM failed to be resumed if adding 'hv-stimer' after Qemu v6.2.0. +Steps to reproduce: +1.Set up GVTd env and launch Windows 10 VM as guest; +2. Sleep the Windows VM with Sleep button; +3. Resume Windows VM via telnet to qemu ,e.g.,'telnet 127.0.0.1 2222', then input 'system_wakeup' to resume Windows VM. +Additional information: + |