Bug 595643
Summary: | RHEVM Backned: Maximum disk size should be different for IDE,VirtIO disk interfaces. [RFE] | ||
---|---|---|---|
Product: | [Retired] oVirt | Reporter: | Oded Ramraz <oramraz> |
Component: | ovirt-engine-core | Assignee: | lpeer <lpeer> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | abaron, acathrow, amureini, iheim, kwolf, lpeer, oramraz, Rhev-m-bugs, sgrinber, tburke, yeylon, ykaul |
Target Milestone: | --- | Keywords: | EasyFix, FutureFeature, Reopened |
Target Release: | 3.3.4 | ||
Hardware: | All | ||
OS: | Windows | ||
Whiteboard: | storage | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-12 07:36:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Oded Ramraz
2010-05-25 09:26:40 UTC
ayal - what should be the numbers for each for 2.2/3.0/3.1 cluster levels? (In reply to comment #0) > Description of problem: > > Right now maximum size for newly created disk is 16TB ( which is ext3 limit ) > IDE disk interfaces has 8TB size limit. physical ide has no such limitation (http://www.48bitlba.com/) and to the best of my knowledge neither does qemu. > > When i run XP VM with disk larger than 8 TB its stuck in a loop: > Format disk -> copy files -> reboot ->.... What service pack? plain XP does not support lba48 and for XP w/sp1 you need to enable lba48 specifically. > > When i run XP guest with 8TB sparse cow disk it manage to finish its > installation but when i run it and look at the disk properties i can see only 2 > TB of free space. As far as the guest os is concerned there is no diff between sparse and preallocated so something here smells fishy. > > IMO Backend should have different size limits for IDE,Virtio disk interfaces. > Another influent parameter for determining maximum disk size might be OS type. > > > > > Version-Release number of selected component (if applicable): > > > How reproducible: > > > Steps to Reproduce: > 1. > 2. > 3. > > Actual results: > > > Expected results: > > > Additional info: Dor , Can you please update us with the current limitations of qemu disk sizes? (In reply to comment #3) > Dor , Can you please update us with the current limitations of qemu disk sizes? Kevin, do you know on any exact limitation? Oded, it's better to use Linux guests to test that, windows is a weird selection, especially XP and also you add another component to the equation (virtio driver) I'm not aware of any currently practically relevant limits. IDE should be the same as on physical hardware, virtio-blk 2^64 bytes. The qcow2 format can do up to 2^62 bytes in theory, but I'm not sure if we don't have some bugs with 32 bit truncation that make it something like cluster_size * sizeof(int) = 256 TB in practice. I don't think we have testing in place for such big images. (In reply to comment #5) > I'm not aware of any currently practically relevant limits. IDE should be the > same as on physical hardware, virtio-blk 2^64 bytes. The qcow2 format can do up > to 2^62 bytes in theory, but I'm not sure if we don't have some bugs with 32 > bit truncation that make it something like cluster_size * sizeof(int) = 256 TB > in practice. I don't think we have testing in place for such big images. i suspect some OSes may have limitations. For example, XP with IDE. It may be transparent to QEMU, but not to RHEVM. This is not a bug. If a you install an os that doesn't support a large disk, then don't expose it. We do not introspect into the guest to see which os is installed. This is not a bug. If a you install an os that doesn't support a large disk, then don't expose it. We do not introspect into the guest to see which os is installed. The OS type is a property of the VM . Engine stores this information in the DB. (In reply to comment #8) > This is not a bug. > If a you install an os that doesn't support a large disk, then don't expose > it. > We do not introspect into the guest to see which os is installed. Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug. |