Bug 433074
Summary: | libvir: Xen Daemon error : internal error domain information incomplete, missing id Error | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | L. M. <needwork> |
Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | sputhenp, tao, xen-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-18 20:51:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
L. M.
2008-02-15 22:45:17 UTC
I should add that this is a paravirt install. -- L.M. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This request was previously evaluated by Red Hat Product Management for inclusion in the current Red Hat Enterprise Linux release, but Red Hat was unable to resolve it in time. This request will be reviewed for a future Red Hat Enterprise Linux release. This error message is symptomatic of something screwy at the xend level. Can anyone reproduce this reliably on rhel 5.2 or 5.3? If so, please give the exact steps you used to reproduce it, as well as: ~/.virt-manager/virt-manager.log virsh list --all xm list --long /etc/xen/{vmname} file for each xm list/virsh list entry Thanks. Ping on this, any info with respect to comment #6? It's been almost 2 months, and since I can't reproduce, closing as WORKSFORME. Please reopen if anyone is still seeing this problem. |