Eric Jansen
2008-Nov-19 12:42 UTC
[Xen-users] Unable to open a connection to the Xen hypervisor/daemon 3
(continued from Unable to open a connection to Xen hypervisor/daemon and Unable to open a connection to Xen hypervisor/daemon 2) There are several awkward results as followings: 1) As root : /usr/sbin/xm info Result: Error: (13, ''Permission denied'') Usage: xm info Get information about Xen host. 2) Service Configuration: xend : running xendomains is running but : Checking for xendomains:[FAILED] libvirtd : running I am trying to give the detail information. Thank you, Best regards, -- Eric Jansen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ross Walker
2008-Nov-19 14:45 UTC
Re: [Xen-users] Unable to open a connection to the Xen hypervisor/daemon 3
On Nov 19, 2008, at 7:42 AM, "Eric Jansen" <janseneric@gmail.com> wrote:> (continued from Unable to open a connection to Xen hypervisor/daemon > and Unable to open a connection to Xen hypervisor/daemon 2) > > There are several awkward results as followings: > > 1) As root : > /usr/sbin/xm info > > Result: > Error: (13, ''Permission denied'') > Usage: xm info > > Get information about Xen host. > > 2) Service Configuration: > xend : running > xendomains is running but : Checking for xendomains:[FAILED] > libvirtd : running > > I am trying to give the detail information.The Xen hypervisor that booted doesn''t match the API installed. Check your grub.conf -Ross _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Eric Jansen
2008-Nov-19 18:11 UTC
Re: [Xen-users] Unable to open a connection to the Xen hypervisor/daemon 3
Thanks for quick reply Ross, please see the followings: Please suggest me on how should I redo? 1. This is the result of /boot/grub/grub.conf: default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Xen-3.3 CentOS 5.2 x86_32 (2.6.18.8-xen) root (hd0,0) kernel /boot/xen-3.3.gz module /boot/vmlinuz-2.6.18.8-xen ro root=LABEL=/1 rhgb quiet module /boot/initrd-2.6.18.8-xen.img title CentOS (2.6.18-92.el5xen) root (hd0,0) kernel /boot/xen.gz-2.6.18-92.el5 module /boot/vmlinuz-2.6.18-92.el5xen ro root=LABEL=/1 rhgb quiet module /boot/initrd-2.6.18-92.el5xen.img title CentOS-base (2.6.18-92.el5) root (hd0,0) kernel /boot/vmlinuz-2.6.18-92.el5 ro root=LABEL=/1 rhgb quiet initrd /boot/initrd-2.6.18-92.el5.img 2. This is the lists of /boot : [root@wing godwing]# ls /boot -alt total 23144 drwxr-xr-x 2 root root 4096 Nov 19 19:16 grub drwxr-xr-x 27 root root 4096 Nov 19 19:04 .. -rw------- 1 root root 2472698 Nov 19 18:45 initrd-2.6.18.8-xen.img drwxr-xr-x 3 root root 4096 Nov 19 18:45 . -rw-r--r-- 1 root root 66216 Nov 19 18:42 config-2.6.18.8-xen -rw-r--r-- 1 root root 750836 Nov 19 18:42 System.map-2.6.18.8-xen -rw-r--r-- 1 root root 1518593 Nov 19 18:42 vmlinuz-2.6.18.8-xen -rw-r--r-- 1 root root 424399 Nov 19 18:37 xen-3.3.1-rc1-pre.gz lrwxrwxrwx 1 root root 20 Nov 19 18:37 xen-3.3.gz -> xen-3.3.1-rc1-pre.gz lrwxrwxrwx 1 root root 20 Nov 19 18:37 xen-3.gz -> xen-3.3.1-rc1-pre.gz lrwxrwxrwx 1 root root 20 Nov 19 18:37 xen.gz -> xen-3.3.1-rc1-pre.gz -rw-r--r-- 1 root root 6190578 Nov 19 18:37 xen-syms-3.3.1-rc1-pre -rw------- 1 root root 2407672 Nov 19 16:57 initrd-2.6.18-92.el5xen.img -rw------- 1 root root 2407266 Nov 19 16:57 initrd-2.6.18-92.el5.img -rwxr-xr-x 1 root root 714716 Jun 11 03:07 xen-syms-2.6.18-92.el5 -rw-r--r-- 1 root root 93281 Jun 11 02:21 symvers-2.6.18-92.el5xen.gz -rw-r--r-- 1 root root 65287 Jun 11 02:21 config-2.6.18-92.el5xen -rw-r--r-- 1 root root 908390 Jun 11 02:21 System.map-2.6.18-92.el5xen -rw-r--r-- 1 root root 2161376 Jun 11 02:21 vmlinuz-2.6.18-92.el5xen -rw-r--r-- 1 root root 91734 Jun 11 01:14 symvers-2.6.18-92.el5.gz -rw-r--r-- 1 root root 65406 Jun 11 01:14 config-2.6.18-92.el5 -rw-r--r-- 1 root root 912686 Jun 11 01:14 System.map-2.6.18-92.el5 -rw-r--r-- 1 root root 1806388 Jun 11 01:14 vmlinuz-2.6.18-92.el5 -rw-r--r-- 1 root root 328755 Jun 11 00:42 xen.gz-2.6.18-92.el5 -rw-r--r-- 1 root root 80032 Nov 23 2007 message I''ll be expecting for your reply Thanks Best Regards, Eric Jansen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ross Walker
2008-Nov-19 23:35 UTC
Re: [Xen-users] Unable to open a connection to the Xen hypervisor/daemon 3
On Nov 19, 2008, at 1:11 PM, "Eric Jansen" <janseneric@gmail.com> wrote:> Thanks for quick reply Ross, please see the followings: > Please suggest me on how should I redo? > > 1. This is the result of /boot/grub/grub.conf: > > default=0 > timeout=5 > splashimage=(hd0,0)/boot/grub/splash.xpm.gz > hiddenmenu > title Xen-3.3 CentOS 5.2 x86_32 (2.6.18.8-xen) > root (hd0,0) > kernel /boot/xen-3.3.gz > module /boot/vmlinuz-2.6.18.8-xen ro root=LABEL=/1 rhgb quiet > module /boot/initrd-2.6.18.8-xen.imgIs this the xenlinux kernel from Xen.org? Why not stick with stock?> > title CentOS (2.6.18-92.el5xen) > root (hd0,0) > kernel /boot/xen.gz-2.6.18-92.el5 > module /boot/vmlinuz-2.6.18-92.el5xen ro root=LABEL=/1 rhgb > quiet > module /boot/initrd-2.6.18-92.el5xen.imgIf this kernel boots you will see the issue you described.> > title CentOS-base (2.6.18-92.el5) > root (hd0,0) > kernel /boot/vmlinuz-2.6.18-92.el5 ro root=LABEL=/1 rhgb quiet > initrd /boot/initrd-2.6.18-92.el5.img >Can you give the output of rpm -qa "*xen*" I guess with the appearence of xenlinux you downloaded the tarball and did a make install which makes reinstallation of Xen extremely difficult. Next time use the src.rpm from 3.2 to build an rpm package which makes reinstalls a lot easier. It is wholly possible that the Xen-libs package from CentOS was still installed when you did the make install and then was upgraded which wrote over your 3.3 libs with 3.1 libs. I hope not but an rpm -qa will show us. -Ross _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Eric Jansen
2008-Nov-20 00:33 UTC
Re: [Xen-users] Unable to open a connection to the Xen hypervisor/daemon 3
Ross, you are right. I did wrongly the installation of Xen 3.3. On installing the Xen 3.3.0, I forgot that I was on Xen world. It must be some crashes of both xens, thus, the virt-manager and xm doesn''t connect to the hypervisor. So let me reinstall CentOS without xen kernel on it. I will be trying to reinstall xen 3.3 again. Thank you Best Regards -- Eric Jansen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users