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/728 | |
| 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/728')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/output/hypervisor/728 | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/728 b/results/classifier/deepseek-2-tmp/output/hypervisor/728 deleted file mode 100644 index df8a39ce2..000000000 --- a/results/classifier/deepseek-2-tmp/output/hypervisor/728 +++ /dev/null @@ -1,17 +0,0 @@ - -Catch up to latest VHDX v2(=0x01) rev-7.0 specification -Additional information: -Below issues need to be addressed before or during the tackling of this issue. -- ~#727 VHDX is corrupted on expansion.~ -- #136 windows qemu-img create vpc/vhdx error due to sparse files -- #1605 On windows, 2nd kind vhdx-dyn bug, crash on Unexpected error in bdrv_check_qiov_request() in io.c -- #806 Fixed VHDX inflates beyond its fixed size when data is copied onto it and also corrupts -- -This VHDX support applies to qemu build on any architecture, not just the windows-build. - -It is very likely, that the native hypervisor on windows WHPX will be the main hypervisor displacing haxm/vbox etc. VHDX, if it works, seems to be the virtual-disk format that is ideal -- for Linux/windows dual-boot machines, -- for clusters with Linux/windows servers sharing images from a network-storage -- for WSL2/Hyper-V - -Following a similar line of thought, NTFS/ExFat may be ideal for sharing data/images between Linux and Windows. So the storing, modification and drive attachment of VHDX files on these filesystems need to be just as well-tested as native Linux filesystems. As their driver are internal-kernel-drivers and not fuse/dokan-drivers, on both operating-systems, they are also performant. |