WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Fedora 12 xen 4.0.0

To: Pasi Kärkkäinen <pasik@xxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Fedora 12 xen 4.0.0
From: Shai Maskit <sjmaskit@xxxxxxxxx>
Date: Wed, 14 Apr 2010 17:13:29 +0300
Cc:
Delivery-date: Wed, 14 Apr 2010 07:39:26 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type :content-transfer-encoding; bh=HDiWrssd1uLyxFICs9vFzpJeG4XC/eUxoYLNVfpAY0M=; b=gZVK6fuMhQ5Ir/o7wY1V9kODLzHu1oV2hMgD6PRuYPQLY1ZICODDP/C55SLosM+l9h sOWBMkFHv7wirkmIx3iL7OXeuZmxR5ZDlb9It1PnYb+/u25QSmVyHXz/brQ7I4KRll0t p0AbHsLW14KJVAW7hr5S3T6rqsNSW5nhyK0rs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=EEdYCCpp11cE9UhWAOmpuUbMEEcul115rX26y0pqu2OUfl3dP72zHrrWhzD3vOd9y8 uv32Mp2hnEgtqO06m527cCIXxhfCqJAVzzE7GPRMHwVgsxe7VT2c/4e77s9hwwz9yL0O 3PnxfI7lhLIRN7xFtpVTdiXhOcRWQ9jWT5ci4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100414133757.GT1878@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <y2t4b37069f1004140528y2a753ca8i2ab7a022ba19351d@xxxxxxxxxxxxxx> <20100414130257.GP1878@xxxxxxxxxxx> <x2q4b37069f1004140633ma28e1649g129ffd8f7c91be29@xxxxxxxxxxxxxx> <20100414133757.GT1878@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[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@xxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>