[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1399191
Title:
Large VHDX
Triaging old bug tickets... can you still reproduce this issue with the
latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Sorry.
Please ignore above change. I just find that I change the status of this bug
https://bugs.launchpad.net/qemu/+bug/1490611
I really don't know I have privilege to modify that.
Sorry again.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Hi Jan,
ls -l returns the length of the file; qemu-img info prints the size of
the file (just like du does). Those are not necessarily the same, as you
can see. On modern filesystems, files can have holes in them which do
contribute to the file length, but which do not use any space on disk
and
If your image contains an ext4 partition it may be worth viewing the
advice MS gives about Dynamic VHDX blocksizes:
https://technet.microsoft.com/en-GB/library/dn720239.aspx .
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
We have encountered the same problem.
We have a 1.4 GB size vmdk image and after converting it to vhdx, its size is
62GB. But qemu-img info show the size is 2.9 G.
===
$ qemu-img info dd_test.vmdk
image: dd_test.vmdk
file format: vmdk
virtual size: 250G (268435456000 bytes)
disk size:
qemu-img version is 1.5.3. I also use newer version to do the
conversion, it has the same result.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1399191
Title:
Large VHDX image size
Status in
