RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
qemu-img refused to create 0-sized vmdk image, but qcow2 format will not be refused. I don't know whether VMware tools can allow us to create 0-sized image and operate on them.

Version-Release number of selected component (if applicable):
# uname -r && rpm -q qemu-kvm-rhev
2.6.32-492.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.430.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.use qemu-img to create 0-sized vmdk image.
# qemu-img create -f vmdk test.vmdk 0k
2.
3.

Actual results:
# qemu-img create -f vmdk test.vmdk 0k
Formatting 'test.vmdk', fmt=vmdk size=0 compat6=off zeroed_grain=off 
test.vmdk: error while creating vmdk: No such file or directory

Expected results:
It should work well if use qemu-img to create 0-sized vmdk image.

Additional info:
# qemu-img create -f qcow2 test.qcow2 0k
Formatting 'test.qcow2', fmt=qcow2 size=0 encryption=off cluster_size=65536 
# qemu-img info test.qcow2 
image: test.qcow2
file format: qcow2
virtual size: 0 (0 bytes)
disk size: 132K
cluster_size: 65536

(In reply to Sibiao Luo from comment #0)
> I don't know whether VMware tools can allow us to create 0-sized
> image and operate on them.
> 
I use the VMware vSphere Client(Version 5.1.0) to create new virtual disk with 0-sized specified, it will give a warning prompt message "The disk capacity entered was not a properly formed number or was out of range. It has been replaced with the nearest acceptable value." and replace into 1MB for recommending.

Best Regards,
sluo

(In reply to Sibiao Luo from comment #1)
> (In reply to Sibiao Luo from comment #0)
> > I don't know whether VMware tools can allow us to create 0-sized
> > image and operate on them.
> > 
> I use the VMware vSphere Client(Version 5.1.0) to create new virtual disk
> with 0-sized specified, it will give a warning prompt message "The disk
> capacity entered was not a properly formed number or was out of range. It
> has been replaced with the nearest acceptable value." and replace into 1MB
> for recommending.
> 

Yes, we conform to the behavior of VMware tools. Intended.

Fam