[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Pasi K?kk?nen" <pasik@xxxxxx>
  • From: "ruozeng.w" <ruozeng.w@xxxxxxxxx>
  • Date: Mon, 18 Apr 2011 23:48:19 +0800
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 18 Apr 2011 08:49:03 -0700
  • 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=VgvoqVicHCjfDpOlv0aOPfEJU/toGUIvkSl6OWulfB6l83VTS+mXqe/NfsKEJTKJkG HOJknTomWRRrSVJS8iY4aCoBZIZI1VR/j54SO56VXTAyTaH5vZ7PbA9wizPnpo7GgZS1 Da+3GZE/NSrpjkgNZinThBhzCt2TeSQTc98y0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I also  found that when "make modules_install" executed, it didn't install any module under /drivers/xen/, but I don't know why.
 
In the kernel .config file, I can't find some item the Pv_ops direction mentioned, such as CONFIG_XEN_PCI, CONFIG_XEN_KBDDEV_FRONTEND, CONFIG_XEN_BLKDEV_BACKEND, and can't find the definition of these options(grep returns nothing), so I think they might be cancelled in new 2.6.39 kernel.
 
 
 
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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.