Bug 1732306
| Summary: | libvirt metadata function is broken | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | Jules <jules> |
| Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | berrange, libvirt-maint, mprivozn, tburke |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-5.7.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-05 19:21:53 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: | |||
|
Description
Jules
2019-07-23 07:08:15 UTC
What hypervisor driver are you using? Not every driver implements that function currently. Look for virDomainGetMetadata in https://libvirt.org/hvsupport.html Ahh. Now that makes sense. I use libxl driver. But whats the trouble in allowing this for all drivers. Since its just metadata? There's no reason why it can't be implemented, it is simply a matter of someone having the time to write the code & submit it. Till then, is there any workaround to use your console-proxy? Thanks in advance! In general you probably shouldn't use the console proxy as while the idea is great, I can't claim the impl is finished / production ready It was however designed to have a pluggable backend - the backend that uses the metadata was just a simple example one. It is easy to come up with other backends Patch proposed upstream: https://www.redhat.com/archives/libvir-list/2019-August/msg00094.html You are awesome. Thanks! Is there any fund e.g. to send tip to the dev team? Pushed upstream as v5.6.0-4-g0f68e1c9ba. (In reply to Jules from comment #7) > You are awesome. Thanks! > > Is there any fund e.g. to send tip to the dev team? No, but don't worry about it. |