github-actions[bot] commented on issue #13192: URL: https://github.com/apache/cloudstack/issues/13192#issuecomment-5346147535
## ๐ฏ Triage report Changing a disk offering (IOPS limits) on a running KVM VM is accepted by the API and the DB/UI reflect the new values, but the live libvirt domain XML is not updated โ the new limits only take effect after a stop/start. A collaborator confirmed this is expected behavior with the current implementation, not user error, and pointed out `virsh blkdeviotune ... --live` (or `domiftune` for network) could be used to apply IO throttling changes live. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:bug | Documented/expected user action (change disk offering while VM running) does not produce the expected effect, and the UI gives no warning. | | **Component** | component:kvm | Confirmed specific to the libvirt/KVM live domain update path. | | **Severity** | Severity:Minor | Workaround exists (reboot VM); no data loss or crash, just delayed enforcement of a limit. | | **Labels** | type:bug, component:kvm, Severity:Minor | See above | | **Coding agent** | Needs more info | The underlying libvirt command (`blkdeviotune --live`) is known, but the scope (which offering changes should update live vs. require reboot, UI messaging changes) needs to be defined by a maintainer before implementation. | <details><summary>๐ก Notes and suggestions</summary> - Consider using `virsh blkdeviotune <domain> <disk> --total-iops-sec X --live` (or per read/write) to apply the new IOPS limits to the running domain instead of only updating the persistent XML. - At minimum, the UI/API response should warn the admin that the running VM was not updated and a restart is required, to avoid confusion. - No similar existing issues were found in a quick search. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/32259459580) ยท sonnet50 262K ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues) > <details> <summary>Add this agentic workflows to your repo</summary> To install this agentic workflow, run ``` gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9 ``` </details> <!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-5, id: 32259459580, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/32259459580 --> <!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
