blob: 69bd177819d4e4a26de1911cbd0a85a5148959ee (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
boot: 0.918
device: 0.886
files: 0.871
hypervisor: 0.841
graphic: 0.777
semantic: 0.724
performance: 0.711
architecture: 0.574
mistranslation: 0.514
register: 0.485
socket: 0.477
permissions: 0.446
PID: 0.420
vnc: 0.420
kernel: 0.399
network: 0.385
risc-v: 0.380
debug: 0.362
virtual: 0.333
ppc: 0.314
arm: 0.290
assembly: 0.272
user-level: 0.264
VMM: 0.252
TCG: 0.244
peripherals: 0.244
x86: 0.230
i386: 0.220
KVM: 0.154
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:
|