From: "ruozeng.w" <ruozeng.w@gmail.com>
To: "Pasi K�rkk�inen" <pasik@iki.fi>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: Xend cannot start
Date: Mon, 18 Apr 2011 23:48:19 +0800 [thread overview]
Message-ID: <201104182348168544695@gmail.com> (raw)
In-Reply-To: 201104181625201517258@gmail.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset="gb2312", Size: 4780 bytes --]
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ärkkäinen
·¢ËÍʱ¼ä£º 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 11454 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-04-18 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 8:25 Xend cannot start ruozeng.w
2011-04-18 11:00 ` Pasi Kärkkäinen
2011-04-18 15:12 ` ruozeng.w
2011-04-18 15:48 ` ruozeng.w [this message]
2011-04-18 16:40 ` Konrad Rzeszutek Wilk
2011-04-19 2:56 ` ruozeng.w
2011-04-19 13:32 ` Konrad Rzeszutek Wilk
2011-04-21 8:49 ` ruozeng.w
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201104182348168544695@gmail.com \
--to=ruozeng.w@gmail.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).