Bug 192549
| Summary: | xend can't find dom0 when I update to 2.6.16-1.2111_FC5 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gary Shi <garyshi> |
| Component: | kernel-xen | Assignee: | Xen Maintainance List <xen-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
| Severity: | urgent | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | bstein |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-05-20 14:03:57 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: | |||
sorry I found it's a dupe... *** This bug has been marked as a duplicate of 190899 *** |
Description of problem: xend can't work after update to kernel-xen0-2.6.16-1.2111_FC5, kernel-xen0-2.6.16-1.2096_FC5 works fine. Version-Release number of selected component (if applicable): kernel-xen0-2.6.16-1.2111_FC5 How reproducible: always Steps to Reproduce: 1.update to that version 2.type "service xend start" 3.run xenstored manually on command line prompt Actual results: /var/log/xend.log complains ERROR (SrvDaemon:299) Exception starting xend ((111,'Connection refused')) with stack trace, and it won't bind to unix socket at /var/lib/xend/xend-socket. xenstored complains FATAL: Failed to initialize dom0 state: No such device full talloc report on 'null_context' (total 56 bytes in 3 blocks) struct domain contains 56 bytes in 2 blocks (ref 0) /local/domain/0 contains 16 bytes in 1 blocks (ref 0) Expected results: it should work... Additional info: kernel-xen0-2.6.16-1.2096_FC5 works fine.