Bug 502777
Summary: | virt-manager does not recalculate free disk space on new VM creation | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stefan Assmann <sassmann> |
Component: | virt-manager | Assignee: | Daniel Berrangé <berrange> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | berrange, crobinso, hbrock, markmc, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-24 16:11:40 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: | |||
Bug Depends On: | |||
Bug Blocks: | 498969 |
Description
Stefan Assmann
2009-05-27 07:46:07 UTC
Ah, this is the "XXXGb available on the host" thing I guess to fix this we'd just need to poll every five seconds or something Adding to F12VirtTarget Why would we need to poll for the remaining disk space every so often? We could just update the value whenever necessary. Polling should be considered the last of all options because you constantly need to get out of idle state. I'm not sure if there are any other places where you need the free disk space value. As of now I've only seen it during VM creation. What's your opinion Mark? Btw, thanks for considering all my RFEs! (In reply to comment #2) > We could just update the value whenever necessary. Define "whenever necessary" IMHO, when the label is visible we'll need to poll to keep it up to date By "whenever necessary" I mean whenever a window shows up that interacts with the remaining disk space value. The value is unlikely to significantly change during the creation of a VM but I don't know where else it might be used. The value could be updated every-time _before_ it is actually read, which would avoid polling. Fixed in virt-manager-0.8.0-5. While the 'New VM' wizard is up, we poll every 3 seconds to make sure the value is current. Updating it only at access time doesn't fly, since the value is used to limit the storage size spin box, and has to be deliberately adjusted. |