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: [Xen-devel] Xend cannot start

To: "ruozeng.w" <ruozeng.w@xxxxxxxxx>
Subject: Re: [Xen-devel] Xend cannot start
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 18 Apr 2011 14:00:00 +0300
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 18 Apr 2011 04:01:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201104181625201517258@xxxxxxxxx>
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
User-agent: Mutt/1.5.18 (2008-05-17)
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