Bug 192549 - xend can't find dom0 when I update to 2.6.16-1.2111_FC5
Summary: xend can't find dom0 when I update to 2.6.16-1.2111_FC5
Keywords:
Status: CLOSED DUPLICATE of bug 190899
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-xen
Version: 5
Hardware: i386
OS: Linux
medium
urgent
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-20 13:51 UTC by Gary Shi
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-05-20 14:03:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gary Shi 2006-05-20 13:51:46 UTC
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.

Comment 1 Gary Shi 2006-05-20 14:03:57 UTC
sorry I found it's a dupe...

*** This bug has been marked as a duplicate of 190899 ***

Comment 2 Brian Stein 2006-05-22 12:21:53 UTC
Update to 2118_FC5.

*** This bug has been marked as a duplicate of 190899 ***


Note You need to log in before you can comment on or make changes to this bug.