@Pan we need to document this as a known issue The bottom line is that size allocated for PVC must be at least double the image size in upload flow (at least we think it should be double but on some occasions we see that even that is not enough)
Hey Adam, is the following text correct? Let me know if you think of any improvements. Are there other types of operations that need to be included in the release note (beyond upload)? When uploading a disk image to a PVC, the space allocated for the PVC must be at least `2 * actual image size + virtual image size`. Otherwise, the virtual machine does not boot successfully. https://bugzilla.redhat.com/show_bug.cgi?id=1676824[(BZ#1676824)]
Hi Pan, This requirement/limitation is not exclusive to upload, I've also seen it when using import. See: https://bugzilla.redhat.com/show_bug.cgi?id=1670993#c14 and https://bugzilla.redhat.com/show_bug.cgi?id=1670993#c15
I think we should explain actual size and virtual size. Actual size means the actual amount of disk space consumed by the file. Virtual size means the size of the disk as the VM would see it. The command 'ls -sh <image file>' will report the actual size. For uncompressed raw images the command 'ls -lh <image file>' will report the virtual size. For qcow2 images you can use 'qemu-img info <image file>' to get both values.
Good call! I have added that to the Known Issue in the form of a note. I think I can probably move this to ON_QA but let me know if you have any other thoughts. Here's the preview build: http://file.bos.redhat.com/pousley/022019/knownissues/cnv_release_notes/cnv_release_notes.html
Even if it's not exclusive (per comment #4), the issue is documented in Known Issues, and there is a link to the original BZ, where one can check for the updates. Moving to Verified.
The requested changes were published here: https://docs.openshift.com/container-platform/3.11/cnv_release_notes/cnv_release_notes.html#RN_known_issues