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-devel

Re: Re: [Xen-devel] Xend cannot start

To: "Pasi K?kk?nen" <pasik@xxxxxx>
Subject: Re: Re: [Xen-devel] Xend cannot start
From: "ruozeng.w" <ruozeng.w@xxxxxxxxx>
Date: Mon, 18 Apr 2011 23:12:22 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 18 Apr 2011 08:12:54 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:date:from:to:cc:references:subject:message-id :x-mailer:mime-version:content-type; bh=Z4gtMrmuMx9StYWFR2XqK9QIVjxIg6JTBrbGDXT5vb4=; b=gpmW5uwM1zsj2VFi2FwwLU2YOAtzpWw5CFf+XcpCFqRWb4IhPiGE6PQ2fJw6DnRGvv +k48lJPyqigdHY6gnKH++nOwTUPBdFTglPeqIpkQYNlO63ZyaE9sfJupKXDs8CbOVAtG TLm0gnI5wf/5COzs/2Pi71JW+2LPtMq0dnaHU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:references:subject:message-id:x-mailer:mime-version :content-type; b=QC77WaA791qJOELDO6Tnk2fQPHchFWIYh/D4C2OZGOWLXQAYeO5maLnjb1ylUQAeF1 FqYst5IqhjLP+jkmDk2PBX1ZEnIqq6lUpshrrb/jyvyQiHXuymnru/w28N3HlC+6F92I P8XWzEYgtBD5tWd9ktPu/VTYetappfQA/O9xA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <201104181625201517258@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,
Yes, I've did this
echo "none /proc/xen xenfs defaults 0 0">>/etc/fstab
to add xenfs mount entry just after I installed xen。
 
Actually I was following this XenParavirtOps direction here:
http://wiki.xensource.com/xenwiki/XenParavirtOps to install and configure xen 4.1.0 with kernel 2.6.39

I did all of those checks:
 
# cat /proc/misc
……
60 xen/gntalloc
61 xen/gntdev
62 xen/evtchn
……
 
#ls -la /dev/xen
total 0
drwxr-xr-x  2 root root    100 2011-04-18 20:36 .
drwxr-xr-x 12 root root  13780 2011-04-18 20:36 ..
crw-rw----  1 root root 10, 62 2011-04-18 20:36 evtchn
crw-rw----  1 root root 10, 60 2011-04-18 20:36 gntalloc
crw-rw----  1 root root 10, 61 2011-04-18 20:36 gntdev
 
But "lsmod | grep -i xen" shows nothing, and I was told that "module xen_gntdev/xen_evtchn not found" when I try to load these modules by "modprobe xen-gntdev/xen-evtchn".
 
 
2011-04-18

Wishes
Ruozeng W 

发件人: Pasi K?kk?nen
发送时间: 2011-04-18  19:00:03
收件人: ruozeng.w
抄送: xen-devel
主题: Re: [Xen-devel] Xend cannot start
On Mon, Apr 18, 2011 at 04:25:23PM +0800, ruozeng.w wrote:
>    Host OS: Ubuntu 8.04 server
>    XEN: 4.1.0
>    Kernel: 2.6.39-rc3
>    When xend is starting, it logged this:
Hello,
Did you check: http://wiki.xen.org/xenwiki/XenCommonProblems#head-26434581604cc8357d9762aaaf040e8d87b37752
-- Pasi
>    /var/log/xen/xend-debug.log:
>    Xend started at Thu Apr 14 17:39:00 2011.
>    cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory
>    cat: /sys/bus/scsi/devices/host0/model: No such file or directory
>    cat: /sys/bus/scsi/devices/host0/type: No such file or directory
>    cat: /sys/bus/scsi/devices/host0/rev: No such file or directory
>    cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory
>    cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory
>    cat: /sys/bus/scsi/devices/host1/model: No such file or directory
>    cat: /sys/bus/scsi/devices/host1/type: No such file or directory
>    cat: /sys/bus/scsi/devices/host1/rev: No such file or directory
>    cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory
>    cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory
>    cat: /sys/bus/scsi/devices/host2/model: No such file or directory
>    cat: /sys/bus/scsi/devices/host2/type: No such file or directory
>    cat: /sys/bus/scsi/devices/host2/rev: No such file or directory
>    cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory
>    cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory
>    cat: /sys/bus/scsi/devices/host3/model: No such file or directory
>    cat: /sys/bus/scsi/devices/host3/type: No such file or directory
>    cat: /sys/bus/scsi/devices/host3/rev: No such file or directory
>    cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory
>    cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory
>    cat: /sys/bus/scsi/devices/host4/model: No such file or directory
>    cat: /sys/bus/scsi/devices/host4/type: No such file or directory
>    cat: /sys/bus/scsi/devices/host4/rev: No such file or directory
>    cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory
>    cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory
>    cat: /sys/bus/scsi/devices/host5/model: No such file or directory
>    cat: /sys/bus/scsi/devices/host5/type: No such file or directory
>    cat: /sys/bus/scsi/devices/host5/rev: No such file or directory
>    cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory
>    cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory
>    cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory
>    cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory
>    cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory
>    cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory
>    cat: /sys/bus/scsi/devices/target3:0:0/vendor: No such file or directory
>    cat: /sys/bus/scsi/devices/target3:0:0/model: No such file or directory
>    cat: /sys/bus/scsi/devices/target3:0:0/type: No such file or directory
>    cat: /sys/bus/scsi/devices/target3:0:0/rev: No such file or directory
>    cat: /sys/bus/scsi/devices/target3:0:0/scsi_level: No such file or directory
>    Someone said that it is because the kernel option CONFIG_XEN_DEV_EVTCHN
>    should be set as 'y' but not 'm', so I checked my linux kernel
>    configuration, and found it is set as 'y'.
>    I can find /sys/bus/scsi/devices/host0/target0:0:0:0/0:0:0:0/vendor, or
>    /sys/bus/scsi/devices/host0/target0:0:0:0/0:0:0:0/scsi_device/0:0:0:0/device/vendor,
>    but definitely no  /sys/bus/scsi/devices/host0/vendor
>    Why this happen? And how can I fix this?
>    Thanks.
>    2011-04-18
>    --------------------------------------------------------------------------
>    Wishes
>    Ruozeng W
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel