Description of problem: After upgrading to 2.6.16-1.2111_FC5xen0 I can no longer issue xm commands or start guest machines. Version-Release number of selected component (if applicable): kernel 2.6.16-1.2111_FC5xen0 How reproducible: Upgrade to kernel 2.6.16-1.2111_FC5xen0 and reboot. OS comes up, but xm does not work and no guests will start. Steps to Reproduce: 1. 2. 3. Actual results: xm commands return: Error: Error connecting to xend: No such file or directory. Is xend running? xend.log shows: [2006-05-05 17:52:11 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-05-05 17:52:11 xend] INFO (SrvDaemon:289) Xend changeset: unavailable . [2006-05-05 17:52:11 xend] ERROR (SrvDaemon:299) Exception starting xend ((111, 'Connection refused')) Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 293, in run servers = SrvServer.create() File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvServer.py", line 106, in create root.putChild('xend', SrvRoot()) File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvRoot.py", line 40, in __init__ self.get(name) File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line 82, in get val = val.getobj() File "/usr/lib64/python2.4/site-packages/xen/web/SrvDir.py", line 52, in getobj self.obj = klassobj() File "/usr/lib64/python2.4/site-packages/xen/xend/server/SrvDomainDir.py", line 39, in __init__ self.xd = XendDomain.instance() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 550, in instance inst.init() File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 70, in init xstransact.Mkdir(VMROOT) File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 317, in Mkdir complete(path, lambda t: t.mkdir(*args)) File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 323, in complete t = xstransact(path) File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 20, in __init__ self.transaction = xshandle().transaction_start() File "/usr/lib64/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle xs_handle = xen.lowlevel.xs.xs() RuntimeError: (111, 'Connection refused') Expected results: xm works and guest machines run. Additional info: If I boot the 2096 kernel the problem goes away. I can boot guest machines that have been upgraded to 2111 under the 2096 kernel.
are you also running the xen 3.0.2 rpm from updates-testing by any chance ? If so, try dropping back to 3.0.1
I am using the 3.0.1-4 version of xen and it does not work at this level.
Just installed fc5 and followed the quick start at http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 with the exact same result when I tried the '/usr/sbin/xm list' command. I'll try using the 2096 kernel.
*** Bug 190944 has been marked as a duplicate of this bug. ***
I just updated my FC5 and get the same results - same errormsgs. [root@adm1-28 ~]# uname -r 2.6.16-1.2111_FC5xen0 [root@adm1-28 ~]# rpm -q xen xen-3.0.1-4 [root@adm1-28 ~]# Cheers, Kenneth
Problem seemed to be introduced as of 2107. Xen version makes little difference (3.0.1-4 vs 3.0.2-x). Reverting back to 2096 seems to alleviate issue. 2.6.16-1.2111_FC5xenU kernels on unprivelaged domains seem to operate okay (expected).
*** Bug 191037 has been marked as a duplicate of this bug. ***
*** Bug 191038 has been marked as a duplicate of this bug. ***
*** Bug 190912 has been marked as a duplicate of this bug. ***
I've been getting the same result. I've downgraded my kernel to 2.6.16-1.2096_FC5xen0 and get the same failures. I've also tried the 2.6.15-1.2054_FC5xen0 with the same failure.
I retried 2.6.16-1.2096_FC5xen0 and it worked...odd :-/
I don't agree with the problem being introduced in 2107. I used 2096 and 2107 without problems before trying 2111, and going back to 2107 still works fine for me.
(In reply to comment #12) > I don't agree with the problem being introduced in 2107. I used 2096 and 2107 > without problems before trying 2111, and going back to 2107 still works fine for me. You are correct, I just rebooted into 2107, and xend seemed to start correctly. I am using xen 3.0.2-x from testing. First time I tested this was not the case - unsure why.
2111 works on SMP and breaks on UP. I have two XEN Boxes, one is Dual Processor PIII, the other single CPU PIV (no HT). The SMP box works, the UP box fails. See also Bug # 191237
In my case it is not so. I have a Dell PE 6650 with 4 cpus. 2111 fails with both HT enabled (8 cpus) and disabled from bios (4) with the same error as Pat Murphy's one. I upgraded from 2054 to 2111 so that I have not the 2107 one to test. Where can I pick it? Gianluca BTW: can I disable HT at runtime in dom0 boot string?
My test case is x86_64 on dual opterons, and 2111 does *not* work for me. Was the PE 6650 test x86 or x86_64?
the PE 6650 is x86 and does *not* work for me too
My test case is a dual Xeon HP DL380G4 (hyperthreading makes it smell like 4 processors). Booting 2111 breaks xend. Booting 2096 xend works. So I don't think the problem is architecture specific.
Same problem with a dual athlon MP server. Also with xen 3.0.2 rpm from testing. The system is configured with yum update run right today. kernel 2111 (and devel one 2113) don't work, while 2096 is ok, in the sense that xend starts. So my working config is: [root@fedora ~]# uname -r 2.6.16-1.2096_FC5xen0 [root@fedora ~]# rpm -q xen xen-3.0.2-0.FC5.1 cat /proc/cpuinfo give 2 x: vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) MP 2200+ stepping : 1 cpu MHz : 1800.111 cache size : 256 KB and [root@fedora ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 256 2 r----- 352.1 I have no domains configured at this moment..... Let me know if I can help debugging things...
2.6.16-1.2116_FC5xen0 from the kernel repository of davej on a dual PIII works fine for me.
kernel 2.6.16-1.2116_FC5 on updates-candidate fixes this (and other xen) problems. Will appear on updates RSN.
Someone mentioned using a newer kernel from davej helped. For details, add http://people.redhat.com/ davej/kernels/Fedora/FC5/kernels.repo to /etc/yum.repos.d/ and update.
I think we should wait the next official FC5 kernel. 2116 is not there any more and now there is 2118. I thought davej kernels were for rawhide, more than fc5 final... Probably xen is yet a low priority technology for rh, until rh el 5 is out... But the less deeply we will test it, the less it will be enterprise ready for rh el 5 too. just my opinion. YMMV.
*** Bug 192039 has been marked as a duplicate of this bug. ***
*** Bug 192174 has been marked as a duplicate of this bug. ***
2118 is available for testing in updates-testing and should resolve this issue.
*** Bug 191417 has been marked as a duplicate of this bug. ***
2118 resolves the issue for me.
*** Bug 192549 has been marked as a duplicate of this bug. ***
Thanks to everyone who reported / tested the newer kernels. Keep it up!
Hi, I've the same issue with 2.6.18-1.2200.fc5xen0. ==> /var/log/xen/xend.log <== [2006-10-22 00:04:06 xend 12249] INFO (SrvDaemon:283) Xend Daemon started [2006-10-22 00:04:06 xend 12249] INFO (SrvDaemon:287) Xend changeset: unavailable . [2006-10-22 00:04:06 xend 12249] ERROR (SrvDaemon:297) Exception starting xend ((111, 'Connection refused')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 291, in run servers = SrvServer.create() File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvServer.py", line 108, in create root.putChild('xend', SrvRoot()) File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvRoot.py", line 40, in __init__ self.get(name) File "/usr/lib/python2.4/site-packages/xen/web/SrvDir.py", line 82, in get val = val.getobj() File "/usr/lib/python2.4/site-packages/xen/web/SrvDir.py", line 52, in getobj self.obj = klassobj() File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomainDir.py", line 39, in __init__ self.xd = XendDomain.instance() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 636, in instance inst.init() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 71, in init xstransact.Mkdir(VMROOT) File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 345, in Mkdir complete(path, lambda t: t.mkdir(*args)) File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 351, in complete t = xstransact(path) File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xstransact.py", line 20, in __init__ self.transaction = xshandle().transaction_start() File "/usr/lib/python2.4/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle xs_handle = xen.lowlevel.xs.xs() Error: (111, 'Connection refused')
(In reply to comment #32) > Hi, > I've the same issue with 2.6.18-1.2200.fc5xen0. This post seem to confirm the issue with this kernel: http://article.gmane.org/gmane.linux.redhat.fedora.xen/1339 Regards
Yesterday (10/20) attempted an upgrade to 2.6.18-1.2200.fc5xen0 on x86_64 and experienced the same problem. Had to roll back to xen-3.0.2-0, kernel-xen0-2.6.16-1.2133_FC5 and libvirt-0.1.1-1.FC5 before xend would properly start. SELinux is disabled on this platform.
(In reply to comment #34) > Yesterday (10/20) attempted an upgrade to 2.6.18-1.2200.fc5xen0 on x86_64 and > experienced the same problem. Had to roll back to xen-3.0.2-0, > kernel-xen0-2.6.16-1.2133_FC5 and libvirt-0.1.1-1.FC5 before xend would properly > start. SELinux is disabled on this platform. I had the same issue with 2.6.18-1.2200.fc5xen0 too and it was enough to be rolled back to kernel-xen0-2.6.17-1.2187_FC5 via yum on 2006/10/23. # yum remove xen # yum install xen-3.0.2-3.FC5 kernel-xen0-2.6.17-1.2187_FC5 libvirt-0.1.1-1.FC5 libvirt-python-0.1.1-1.FC5
same problem on x86. See #189112 comment.