1 files changed, 23 insertions, 0 deletions
diff --git a/gitlab/issues_toml/target_missing/host_missing/accel_missing/813.toml b/gitlab/issues_toml/target_missing/host_missing/accel_missing/813.toml
new file mode 100644
index 000000000..824442b07
--- /dev/null
+++ b/gitlab/issues_toml/target_missing/host_missing/accel_missing/813.toml
@@ -0,0 +1,23 @@
+id = 813
+title = "On windows, preallocation=full qcow2 not creatable, qcow2 not resizable"
+state = "opened"
+created_at = "2022-01-12T15:42:28.228Z"
+closed_at = "n/a"
+labels = ["Storage"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/813"
+host-os = "Windows 10 21H2"
+host-arch = "x86_64"
+qemu-version = "`"
+guest-os = "n/a"
+guest-arch = "n/a"
+description = """Not possible to create a fixed-virtual-disk qcow as one may do on linux.
+One sometimes may want to create a fixed size qcow2, as can be done with the fixed variants of VHDX, VMDK, VDI, 
+
+The advantage of a fixed virtual-disk format, such as fixed-VHDX, fixed-VMDK, fixed-VDI is that it keeps the disk-meta-data as a header bundled along with that is essentially a raw image, allowing for seamless tooling and management of virtual-disks
+
+Workaround use a raw file as diskimage. (see workaround given below)
+
+To be very general, the implementation of this may need to factor in what underlying operations (fallocate, fallocate_punchhole, truncate, sparse) are supported by what filesystems (NTFS, ExFAT, ext4), choice of filesystem-driver (sometimes the driver may not have yet implemented an underlying operation), and operating systems (Linux/Win), and possible workarounds to achieve the same effect in the absence of underlying-operation."""
+reproduce = """1. open command shell
+2. run the qemu-img command. In my case, qcow2 file is attempted to be created on a drive with ExFAT filesystem."""
+additional = """"""