diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
| commit | dee4dcba78baf712cab403d47d9db319ab7f95d6 (patch) | |
| tree | 418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/deepseek-r1:14b/output/files/1101 | |
| parent | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff) | |
| download | qemu-analysis-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz qemu-analysis-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip | |
restructure results
Diffstat (limited to 'results/classifier/deepseek-r1:14b/output/files/1101')
| -rw-r--r-- | results/classifier/deepseek-r1:14b/output/files/1101 | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/results/classifier/deepseek-r1:14b/output/files/1101 b/results/classifier/deepseek-r1:14b/output/files/1101 new file mode 100644 index 000000000..0cd9c18c9 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/files/1101 @@ -0,0 +1,13 @@ + +QEMU 7.0.0 corrupts VHDX and VHD (VPC) files on write. +Description of problem: +QEMU writes to VHDX and VHD (VPC) files produce a corrupt/non-compliant image. +QEMU appears to be able to read VHDX and VHD images correctly. + +This problem manifests in at least two cases +1. When attaching a VHDX/VHD file to a QEMU machine. A previously working OS image created using the Hyper-V and imaging tools boots properly, but writes that normally occur in the running VM are not written out correctly. The image will fail to boot the next time due to corruption. +2. Image conversion operations *TO* VHDX/VHD fail. (note that QEMU correctly converts *FROM* VHDX/VHD assuming a well formed input image). This implies that reads to VHDX/VHD are OK, but writes to VHDX/VHD are NOT OK. +Steps to reproduce: +1. See Above. +Additional information: + |