Bug 215413
Summary: | Incorrect Xen vm disk size brings the system to its knees | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Qarras <dqarras> |
Component: | virt-manager | Assignee: | Daniel Berrangé <berrange> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Jenner <mjenner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | xen-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 0.5.3-1.f8 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-22 21:39:56 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
Daniel Qarras
2006-11-13 20:52:15 UTC
To add confustion, virt-manager wants file size in megabytes, virt-install in gigabytes. virt-manager should probably some sanity checking here and at least get confirmation; virt-install allows things like this somewhat intentionally (makes it easier to do testing of large disks, etc) Just to save me some testing, was the absurdly large storage file sparse or non-sparse? I assume non-sparse, but can you say for sure? I can say for sure only that I was using default values and not doing any sparse settings by hand. change QA contact F6 is end of life, but this certainly should not be an issue in F7 or F8, as there is sanity checking in virt-install and virt-manager to ensure we do not attempt to create a disk that is larger than available space on the host. Closing this as CURRENTRELEASE. |