Bug 1451113
| Summary: | virt-manager shows incorrect CPU list for aarch64 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jeremy Linton <jeremy.linton> | ||||
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 26 | CC: | berrange, crobinso, jeremy.linton, virt-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | aarch64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-07-17 16:15:03 UTC | Type: | Bug | ||||
| 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: | 245418 | ||||||
| Attachments: |
|
||||||
|
Description
Jeremy Linton
2017-05-15 20:08:01 UTC
Can you provide a VM XML config that shows this behavior on the CPU page? sudo virsh dumpxml $vmname Created attachment 1299884 [details]
Dump of running guest
Thanks, I reproduced. Showing x86 models was a virt-manager error, fixed now:
commit ca56f74ed7314487ce286ac5d00cd1bbaedb66f6
Author: Cole Robinson <crobinso>
Date: Mon Jul 17 11:29:54 2017 -0400
capabilities: Fix model list caching for different archs (bz 1451113)
That said, libvirt's virConnectGetCPUModelNames doesn't support aarch64, so you won't get any model names listed in virt-manager now either. That's a separate issue though. (note, you can still manually type a model name cortex-a57 or whatever, we just don't show a list)
Since that fix is just a UI tweak I'm closing as 'upstream', not really important enough to track explicitly backporting IMO
|