github-actions[bot] commented on issue #13484: URL: https://github.com/apache/cloudstack/issues/13484#issuecomment-5356774983
## ๐ฏ Triage report Attaching a 4th volume (3rd data disk) to a running VM with the Q35 machine type fails with a libvirt "target duplicated for disk sources" error, though it succeeds when the VM is stopped. This points to a disk target/slot allocation bug specific to Q35's PCIe topology in the KVM live-attach path. ### ๐ Assessment | Dimension | Value | Reasoning | |---|---|---| | **Type** | type:bug | Reproducible failure in live volume attach for a specific machine type | | **Component** | component:kvm | Issue is in the libvirt/KVM disk-attach XML generation logic | | **Severity** | Severity:Minor | Workaround exists (attach while VM is stopped); affects only Q35 machine type and specific disk-count threshold | | **Labels** | type:bug, component:kvm, Severity:Minor | See above | | **Coding agent** | Needs more info | Reproduction steps are clear, but pinpointing the exact target/slot allocation logic in the KVM disk-attach code (likely `LibvirtComputingResource`/disk def builder) requires investigation into how device targets are assigned for Q35 vs i440fx topologies | ### ๐ Similar issues No closely matching open duplicate issues were found; a maintainer referenced #12535 (also Q35-related) as a possibly connected but distinct problem in the existing comment thread. <details><summary>๐ก Notes and suggestions</summary> Worth checking whether the live-attach code path computes disk target device names (e.g. `sda`, `sdb`, ...) differently than the path used when building the full domain XML at VM start, since the failure only manifests on hot-attach and not on VM start with the same number of disks. The maintainer's question about #12535 (a separate Q35 startup issue) is still unanswered by the reporter and may be worth following up on. </details> > Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/32375697891) ยท sonnet50 224.8K ยท [โท](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: 32375697891, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/32375697891 --> <!-- 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]
