diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/output/hypervisor/1887 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma 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, 0 insertions, 10 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/1887 b/results/classifier/deepseek-2-tmp/output/hypervisor/1887 deleted file mode 100644 index 01dfec3df..000000000 --- a/results/classifier/deepseek-2-tmp/output/hypervisor/1887 +++ /dev/null @@ -1,10 +0,0 @@ - -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: - |