Bug 1259116
Summary: | qemu can not read disk size of libiscsi and it shows 'disk size: unavailable' | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Pei Zhang <pezhang> |
Component: | qemu-kvm-rhev | Assignee: | Fam Zheng <famz> |
Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | chayang, famz, juzhang, knoel, kwolf, michen, pbonzini, virt-maint, xfu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-20 04:52:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pei Zhang
2015-09-02 01:45:57 UTC
Actually I think unavailable is more accurate than "0". The allocation status can be retrieved by QEMU scanning each block in the target but that can take unnecessarily long time just to display the summary for the image. So I'm not sure this issue is worth fixing. I agree with Fam. Alternatively, qcow2 could store a high-water mark into the header, and qemu-img info could use it. CCing Kevin for ideas, but I'm okay with CLOSED/NOTABUG. You don't actually have to store another value in the qcow2 header. Scanning the last refcount block should be quick enough. However, I'm still not convinced whether that's useful enough to actually do it on every qcow2_open(). |