I''m trying to get xen4 to work, and i''m still stuck.
i''ve used michael young''s fedora12 dom0 and xen 4 rpms,
but i''m not doing something right, since i cannot get xend working
properly:
[root@kpc35 ~]# uname -r
2.6.32.10-1.2.92.xendom0.fc12.i686.PAE
[root@kpc35 ~]# cat /etc/grub.conf
.
.
.
.
title Fedora-xen (2.6.32.10-1.2.92.xendom0.fc12.i686.PAE)
root (hd0,0)
kernel /xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all
module /vmlinuz-2.6.32.10-1.2.92.xendom0.fc12.i686.PAE ro
root=/dev/mapper/vg_kpc35-lv_root noiswmd LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
nomodeset
module /initramfs-2.6.32.10-1.2.92.xendom0.fc12.i686.PAE.img
.
.
[root@kpc35 ~]# service xend status
xend dead but pid file exists
[FAILED]
[root@kpc35 ~]# xm list
Error: Unable to connect to xend: No such file or directory. Is xend running?
I''m obviously getting an error when trying to run virt-manager, but
that''s expected when the xend isn''t working....
any help will be greatly appreciated
SM
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Wed, Apr 14, 2010 at 03:28:01PM +0300, Shai Maskit wrote:> I''m trying to get xen4 to work, and i''m still stuck. > i''ve used michael young''s fedora12 dom0 and xen 4 rpms, > but i''m not doing something right, since i cannot get xend working properly: > > [root@kpc35 ~]# uname -r > 2.6.32.10-1.2.92.xendom0.fc12.i686.PAE > [root@kpc35 ~]# cat /etc/grub.conf > . > . > . > . > title Fedora-xen (2.6.32.10-1.2.92.xendom0.fc12.i686.PAE) > root (hd0,0) > kernel /xen-4.0.gz dom0_mem=1024M loglvl=all guest_loglvl=all > module /vmlinuz-2.6.32.10-1.2.92.xendom0.fc12.i686.PAE ro > root=/dev/mapper/vg_kpc35-lv_root noiswmd LANG=en_US.UTF-8 > SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet > nomodeset > module /initramfs-2.6.32.10-1.2.92.xendom0.fc12.i686.PAE.img > . > . > [root@kpc35 ~]# service xend status > xend dead but pid file exists > [FAILED] > > [root@kpc35 ~]# xm list > Error: Unable to connect to xend: No such file or directory. Is xend running? > > I''m obviously getting an error when trying to run virt-manager, but > that''s expected when the xend isn''t working.... > > any help will be greatly appreciated >Do you have xenfs mounted to /proc/xen ? Do you have xen-evtchn.ko driver loaded? Do have files under /proc/xen/ ? See this wiki page for more information about the new pvops dom0 kernel: http://wiki.xensource.com/xenwiki/XenParavirtOps -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
[root@kpc35 ~]# ls -ltr /var/run/
.
.
.
-rw-r--r--. 1 root root 5 2010-04-14 16:58 xend.pid
[root@kpc35 ~]# rm /var/run/xend.pid
rm: remove regular file `/var/run/xend.pid''?
[root@kpc35 ~]# bash -x /etc/init.d/xend start
+ . /etc/rc.d/init.d/functions
++ TEXTDOMAIN=initscripts
++ umask 022
++ PATH=/sbin:/usr/sbin:/bin:/usr/bin
++ export PATH
++ ''['' -z '''' '']''
++ COLUMNS=80
++ ''['' -z '''' '']''
+++ /sbin/consoletype
++ CONSOLETYPE=pty
++ ''['' -f /etc/sysconfig/i18n -a -z '''' -a -z
'''' '']''
++ . /etc/profile.d/lang.sh
++ unset LANGSH_SOURCED
++ ''['' -z '''' '']''
++ ''['' -f /etc/sysconfig/init '']''
++ . /etc/sysconfig/init
+++ BOOTUP=color
+++ RES_COL=60
+++ MOVE_TO_COL=''echo -en \033[60G''
+++ SETCOLOR_SUCCESS=''echo -en \033[0;32m''
+++ SETCOLOR_FAILURE=''echo -en \033[0;31m''
+++ SETCOLOR_WARNING=''echo -en \033[0;33m''
+++ SETCOLOR_NORMAL=''echo -en \033[0;39m''
+++ LOGLEVEL=3
+++ PROMPT=yes
+++ AUTOSWAP=no
++ ''['' pty = serial '']''
++
__sed_discard_ignored_files=''/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d''
+ ''['' ''!'' -d /proc/xen '']''
+ grep -q control_d /proc/xen/capabilities
+ RETVAL=0
+ case "$1" in
+ start
+ echo -n ''Starting xend daemon: ''
Starting xend daemon: + /usr/sbin/xend
+ RETVAL=1
+ test 1 = 0
+ echo_failure
+ ''['' color = color '']''
+ echo -en ''\033[60G''
+ echo -n
''[''
[+ ''['' color = color '']''
+ echo -en ''\033[0;31m''
+ echo -n FAILED
FAILED+ ''['' color = color '']''
+ echo -en ''\033[0;39m''
+ echo -n '']''
]+ echo -ne ''\r''
+ return 1
+ echo
+ ''['' 1 -eq 0 '']''
+ exit 1
[root@kpc35 ~]#
from what i see, "/usr/sbin/xend" returns 1.
i''m running Python 2.6.2,
thanks! (again ;)
On Wed, Apr 14, 2010 at 4:37 PM, Pasi Kärkkäinen <pasik@iki.fi>
wrote:> On Wed, Apr 14, 2010 at 04:33:49PM +0300, Shai Maskit wrote:
>> my /etc/fstab doesn''t contain any mount information concerning
xenfs,
>> however:
>>
>> [root@kpc35 ~]# ls -l /proc/xen/
>> total 0
>> -r--r--r--. 1 root root 0 2010-04-13 13:19 capabilities
>> -rw-------. 1 root root 0 2010-04-13 13:19 privcmd
>> -rw-------. 1 root root 0 2010-04-13 13:19 xenbus
>> -rw-------. 1 root root 0 2010-04-13 13:19 xsd_kva
>> -rw-------. 1 root root 0 2010-04-13 13:19 xsd_port
>>
>> so when i tried to add:
>> none /proc/xen xenfs defaults
0 0
>>
>
> You don''t need that since the fedora init script will try to
> mount the xenfs automatically, and seemingly it has already done that.
>
>
>> i got:
>> [root@kpc35 ~]# mount -a
>> mount: none already mounted or /proc/xen busy
>>
>
> Yes, it''s already mounted.
>
>> as far as modules:
>>
>> [root@kpc35 ~]# lsmod | grep xen
>> xen_evtchn 3729 1
>> xenfs 7726 1
>>
>
> So that''s all OK.
>
>> >> .
>> >> [root@kpc35 ~]# service xend status
>> >> xend dead but pid file exists
>> >>
[FAILED]
>> >>
>
> Did you try removing the pid file and then restarting xend?
>
> -- Pasi
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
i''ve done some debugging to /usr/sbin/xend and this is what i came up
with:
from /var/log/xen/xend.log:
[2010-04-15 10:50:16 32442] ERROR (SrvDaemon:356) Exception starting
xend (no element found: line 1, column 0)
Traceback (most recent call last):
File
"/usr/lib/python2.6/site-packages/xen/xend/server/SrvDaemon.py",
line 348, in run
servers = SrvServer.create()
File
"/usr/lib/python2.6/site-packages/xen/xend/server/SrvServer.py",
line 251, in create
root.putChild(''xend'', SrvRoot())
File "/usr/lib/python2.6/site-packages/xen/xend/server/SrvRoot.py",
line 40, in __init__
self.get(name)
File "/usr/lib/python2.6/site-packages/xen/web/SrvDir.py", line 84,
in get
val = val.getobj()
File "/usr/lib/python2.6/site-packages/xen/web/SrvDir.py", line 52,
in getobj
self.obj = klassobj()
File "/usr/lib/python2.6/site-packages/xen/xend/server/SrvNode.py",
line 30, in __init__
self.xn = XendNode.instance()
File "/usr/lib/python2.6/site-packages/xen/xend/XendNode.py", line
1140, in instance
inst = XendNode()
File "/usr/lib/python2.6/site-packages/xen/xend/XendNode.py", line
70, in __init__
saved_host = self.state_store.load_state(''host'')
File "/usr/lib/python2.6/site-packages/xen/xend/XendStateStore.py",
line 105, in load_state
dom = minidom.parse(xml_path)
File "/usr/lib/python2.6/site-packages/_xmlplus/dom/minidom.py",
line 1915, in parse
return expatbuilder.parse(file)
File
"/usr/lib/python2.6/site-packages/_xmlplus/dom/expatbuilder.py",
line 926, in parse
result = builder.parseFile(fp)
File
"/usr/lib/python2.6/site-packages/_xmlplus/dom/expatbuilder.py",
line 211, in parseFile
parser.Parse("", True)
ExpatError: no element found: line 1, column 0
the file which it''s trying to parse is /var/lib/xend/state/host.xml,
which is empty.
which service/module creates this xml file? do i need to edit it?
thanks!
On Wed, Apr 14, 2010 at 5:13 PM, Shai Maskit <sjmaskit@gmail.com>
wrote:> [root@kpc35 ~]# ls -ltr /var/run/
> .
> .
> .
> -rw-r--r--. 1 root root 5 2010-04-14 16:58 xend.pid
> [root@kpc35 ~]# rm /var/run/xend.pid
> rm: remove regular file `/var/run/xend.pid''?
> [root@kpc35 ~]# bash -x /etc/init.d/xend start
> + . /etc/rc.d/init.d/functions
> ++ TEXTDOMAIN=initscripts
> ++ umask 022
> ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin
> ++ export PATH
> ++ ''['' -z '''' '']''
> ++ COLUMNS=80
> ++ ''['' -z '''' '']''
> +++ /sbin/consoletype
> ++ CONSOLETYPE=pty
> ++ ''['' -f /etc/sysconfig/i18n -a -z ''''
-a -z '''' '']''
> ++ . /etc/profile.d/lang.sh
> ++ unset LANGSH_SOURCED
> ++ ''['' -z '''' '']''
> ++ ''['' -f /etc/sysconfig/init '']''
> ++ . /etc/sysconfig/init
> +++ BOOTUP=color
> +++ RES_COL=60
> +++ MOVE_TO_COL=''echo -en \033[60G''
> +++ SETCOLOR_SUCCESS=''echo -en \033[0;32m''
> +++ SETCOLOR_FAILURE=''echo -en \033[0;31m''
> +++ SETCOLOR_WARNING=''echo -en \033[0;33m''
> +++ SETCOLOR_NORMAL=''echo -en \033[0;39m''
> +++ LOGLEVEL=3
> +++ PROMPT=yes
> +++ AUTOSWAP=no
> ++ ''['' pty = serial '']''
> ++
__sed_discard_ignored_files=''/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d''
> + ''['' ''!'' -d /proc/xen
'']''
> + grep -q control_d /proc/xen/capabilities
> + RETVAL=0
> + case "$1" in
> + start
> + echo -n ''Starting xend daemon: ''
> Starting xend daemon: + /usr/sbin/xend
> + RETVAL=1
> + test 1 = 0
> + echo_failure
> + ''['' color = color '']''
> + echo -en ''\033[60G''
> + echo -n
''[''
> [+ ''['' color = color '']''
> + echo -en ''\033[0;31m''
> + echo -n FAILED
> FAILED+ ''['' color = color '']''
> + echo -en ''\033[0;39m''
> + echo -n '']''
> ]+ echo -ne ''\r''
> + return 1
> + echo
>
> + ''['' 1 -eq 0 '']''
> + exit 1
> [root@kpc35 ~]#
>
> from what i see, "/usr/sbin/xend" returns 1.
> i''m running Python 2.6.2,
>
> thanks! (again ;)
>
> On Wed, Apr 14, 2010 at 4:37 PM, Pasi Kärkkäinen <pasik@iki.fi>
wrote:
>> On Wed, Apr 14, 2010 at 04:33:49PM +0300, Shai Maskit wrote:
>>> my /etc/fstab doesn''t contain any mount information
concerning xenfs,
>>> however:
>>>
>>> [root@kpc35 ~]# ls -l /proc/xen/
>>> total 0
>>> -r--r--r--. 1 root root 0 2010-04-13 13:19 capabilities
>>> -rw-------. 1 root root 0 2010-04-13 13:19 privcmd
>>> -rw-------. 1 root root 0 2010-04-13 13:19 xenbus
>>> -rw-------. 1 root root 0 2010-04-13 13:19 xsd_kva
>>> -rw-------. 1 root root 0 2010-04-13 13:19 xsd_port
>>>
>>> so when i tried to add:
>>> none /proc/xen xenfs defaults
0 0
>>>
>>
>> You don''t need that since the fedora init script will try to
>> mount the xenfs automatically, and seemingly it has already done that.
>>
>>
>>> i got:
>>> [root@kpc35 ~]# mount -a
>>> mount: none already mounted or /proc/xen busy
>>>
>>
>> Yes, it''s already mounted.
>>
>>> as far as modules:
>>>
>>> [root@kpc35 ~]# lsmod | grep xen
>>> xen_evtchn 3729 1
>>> xenfs 7726 1
>>>
>>
>> So that''s all OK.
>>
>>> >> .
>>> >> [root@kpc35 ~]# service xend status
>>> >> xend dead but pid file exists
>>> >>
[FAILED]
>>> >>
>>
>> Did you try removing the pid file and then restarting xend?
>>
>> -- Pasi
>>
>>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users