summary refs log tree commit diff stats
path: root/gitlab/issues/target_missing/host_missing/accel_missing/1236.toml
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/1236.toml')
-rw-r--r--gitlab/issues/target_missing/host_missing/accel_missing/1236.toml54
1 files changed, 54 insertions, 0 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1236.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1236.toml
new file mode 100644
index 00000000..82e3f83c
--- /dev/null
+++ b/gitlab/issues/target_missing/host_missing/accel_missing/1236.toml
@@ -0,0 +1,54 @@
+id = 1236
+title = "blockdev fixed vhdx trying to reserve space, also misleading error, Could not open file: Invalid argument"
+state = "opened"
+created_at = "2022-09-30T08:52:49.967Z"
+closed_at = "n/a"
+labels = ["Storage", "hostos: Windows"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1236"
+host-os = "Microsoft Windows 10 22H1 (Its possible this is not windows-only and also happens on Linux)"
+host-arch = "x86_64"
+qemu-version = "``qemu-storage-daemon version 7.1.0 (v7.1.0-11925-g4ec481870e-dirty)``"
+guest-os = "NA"
+guest-arch = "x86_64"
+description = """The qemu-storage-daemon/other qemu commands will not start and will choke on requiring vhdx driver for the blockdev layer.
+Opening a fixed-virtual-disk like fixed-vhdx should not reserve extra space, and should only overwrite as all blocks are already allocated."""
+reproduce = """1. Ensure that a partition size is such that after deciding a fixed-vhdx size, the remainder space after creation of fixed-vhdx is less than the fixed-vhdx.
+2. Create a fixed-vhdx file 
+3. Try to start an nbd server with it
+the qemu-storage-daemon will not start"""
+additional = """I want to mention that I am testing qemu-storage-daemon under windows/hyperv
+
+So far, I want to report that it has **worked** for rawimg and qcow2-fixed.  
+See comment of 20220926 https://github.com/cloudbase/wnbd/issues/63#issuecomment-1257148849 
+
+The driver parameter ```vhdx``` to the blockdev argument seems to struggle with it.
+
+I wanted to check if the vhdx blockdev driver has the same VHDX-related-bugs as qemu-nbd 
+- #727 VHDX is corrupted on expansion.
+- #806 Fixed VHDX inflates beyond its fixed size when data is copied onto it and also corrupts 
+
+Even the the blockdev reference entries seem to have VHDX all over the place
+- pg 318 https://readthedocs.org/projects/qemu/downloads/pdf/latest/
+- https://www.qemu.org/docs/master/system/qemu-block-drivers.html
+- except conspicuously here !! https://www.qemu.org/docs/master/interop/qemu-storage-daemon-qmp-ref.html?highlight=blockdev#qapidoc-265
+
+
+```
+C:\\Windows\\System32>qemu-storage-daemon --version
+qemu-storage-daemon version 7.1.0 (v7.1.0-11925-g4ec481870e-dirty)
+
+C:\\Windows\\System32>qemu-storage-daemon --blockdev driver=file,node-name=file,filename=H:\\gkpics01.vhdx --blockdev driver=vhdx,node-name=vhdx,file=file --nbd-server addr.type=inet,addr.host=127.0.0.1,addr.port=10809 --export type=nbd,id=export,node-name=vhdx,name=gkpics01,writable=on
+qemu-storage-daemon: --blockdev driver=vhdx,node-name=vhdx,file=file: Could not open 'H:\\gkpics01.vhdx': Invalid argument
+
+C:\\Windows\\System32>qemu-storage-daemon --blockdev driver=file,node-name=file,filename=H:\\gkpics01.vhdx --blockdev driver=vhdx,node-name=vhdx,file=file,subformat=fixed --nbd-server addr.type=inet,addr.host=127.0.0.1,addr.port=10809 --export type=nbd,id=export,node-name=vhdx,name=gkpics01,writable=on
+qemu-storage-daemon: --blockdev driver=vhdx,node-name=vhdx,file=file,subformat=fixed: Parameter 'subformat' is unexpected
+
+C:\\Windows\\System32>dir H:\\gkpics01.vhdx
+ Volume in drive H is CPERF0
+ Volume Serial Number is F196-DB9E
+ Directory of H:\\
+09/29/2022  08:55 PM    99,727,966,208 gkpics01.vhdx
+               1 File(s) 99,727,966,208 bytes
+               0 Dir(s)   4,312,399,872 bytes free
+```
+##"""