Bug 238833
| Summary: | Error: Device 0 not connected | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Jan Pazdziora <jpazdziora> | ||||||
| Component: | xen | Assignee: | Daniel Berrangé <berrange> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 5.0 | CC: | agriffis, clalance, gozen, kajtzu, xen-maint | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-01-20 21:15:12 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 449772 | ||||||||
| Attachments: |
|
||||||||
|
Description
Jan Pazdziora
2007-05-03 08:54:54 UTC
Created attachment 154013 [details]
xend-debug.log
Here's the xend-debug.log. However, I cannot say for sure what (if any) parts
of that content are related to this problem and what was there already before I
got the error message.
I have seen similar. In my case I used RHEL5 GA dom0/guest, LVM dom0, one logical volume/guest system. "xm list" gave the same error which I managed to circumvent by doing /sbin/service xend restart (resulting "xm list" would work for a while again). What was more worrying was that the shutdowned guests did not show up anymore but from a LVM perspective were still holding the volumes (lvdisplay VG01, etc. showed that # open was 1 instead of zero). There was nothing in the xend.log or xend-debug.log at that time. After doing service xend restart xm destroy also refuses to destroy things not shown with xm list so there is really nothing else to do except restart dom0. I am not sure if these are one and the same issue or if they just happen to coincide at the same time. :) Please test with current 5.1 beta. I've tested now with Xen host running 2.6.18-38.el5xen and xen-3.0.3-35.el5. The problem persists: # xm shutdown rhel5 ; while true ; do xm list ; done Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 167.2 rhel5 1 299 1 -b---- 21.6 Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 167.5 rhel5 1 299 1 -b---- 21.6 Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 167.8 rhel5 1 299 1 -b---- 21.6 Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 168.1 rhel5 1 299 1 -b---- 21.6 [...] Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 191.8 rhel5 1 299 1 r----- 28.4 Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 192.4 rhel5 1 299 1 r----- 29.1 Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 192.8 rhel5 1 299 1 r----- 29.4 Error: Device 0 not connected Usage: xm list [options] [Domain, ...] List information about all/some domains. -l, --long Output all VM details in SXP --label Include security labels Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 194.1 Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 195.1 Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1721 2 r----- 195.7 The (paravirtual guest) guest was running 2.6.18-8.el5xen but I assume guest's kernel should not matter? 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 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. Created attachment 311563 [details]
Ignore errors fetching SXPR from individual domains which are shutting down
*** Bug 435332 has been marked as a duplicate of this bug. *** *** Bug 288301 has been marked as a duplicate of this bug. *** Built into xen-3.0.3-67.el5 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0118.html |