github-actions[bot] commented on issue #12889:
URL: https://github.com/apache/cloudstack/issues/12889#issuecomment-5294167334

   ## ๐ŸŽฏ Triage report
   
   Windows guest VMs on KVM have no audio hardware by default, requiring a 
manual `extraconfig` (`sound`) to be allowlisted via the 
`allow.additional.vm.configuration.list.kvm` global setting before it can be 
applied per-VM. The reporter and a maintainer agree this is more of a 
default-configuration/UX gap than a true bug โ€” sound works once configured, but 
the setup process is not user-friendly (CLI/CloudMonkey required).
   
   ### ๐Ÿ“Š Assessment
   
   | Dimension | Value | Reasoning |
   |---|---|---|
   | **Type** | type:enhancement | Confirmed by reporter and maintainer to be a 
UX/default-settings gap, not a functional defect โ€” workaround exists and works |
   | **Component** | component:kvm, component:UI | KVM `extraconfig` handling 
and instance-settings UI (similar to existing TPM toggle) |
   | **Severity** | n/a | Not a bug โ€” enhancement request |
   | **Labels** | type:enhancement, component:kvm, component:UI | |
   | **Coding agent** | Needs more info | Two concrete implementation ideas 
were proposed (add `sound` to default allow-list; add a UI toggle similar to 
TPM) but no maintainer has committed to a specific approach yet |
   
   ### ๐Ÿ”— Similar issues
   
   - https://github.com/apache/cloudstack/issues/9460 (related) โ€” 
"RootDiskController setting not Honored throughout Instance lifecycle" โ€” 
referenced in this issue's discussion regarding instance-level KVM 
configuration settings.
   
   <details><summary>๐Ÿ’ก Notes and suggestions</summary>
   
   - Two incremental options discussed in the thread:
     1. Add `sound` to the default values of 
`allow.additional.vm.configuration.list.kvm` (low effort).
     2. Add a dedicated UI toggle for enabling a virtual sound device, modeled 
after the existing TPM toggle, possibly auto-surfaced for Windows-family OS 
types.
   - Reporter (davift) volunteered to update documentation once an approach is 
decided โ€” worth looping them in when implementation starts.
   
   </details>
   
   
   
   > Generated by [Daily Issue 
Triage](https://github.com/apache/cloudstack/actions/runs/31806898936) ยท 
sonnet50 357.5K ยท 
[โ—ท](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: 31806898936, workflow_id: 
daily-issue-triage, run: 
https://github.com/apache/cloudstack/actions/runs/31806898936 -->
   <!-- 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]

Reply via email to