Mailing List Archive: Xend cannot start

Xend cannot start

Apr 18, 2011, 1:25 AM

Post #1 of 8 (294 views)

Host OS: Ubuntu 8.04 server
XEN: 4.1.0
Kernel: 2.6.39-rc3

When xend is starting, it logged this:

/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

Re: Xend cannot start [ In reply to ]

pasik at iki

Apr 18, 2011, 4:00 AM

Post #2 of 8 (292 views)

Permalink

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: Xend cannot start [ In reply to ]

ruozeng.w at gmail

Apr 18, 2011, 8:12 AM

Post #3 of 8 (298 views)

Permalink

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

Re: Re: Xend cannot start [ In reply to ]

ruozeng.w at gmail

Apr 18, 2011, 8:48 AM

Post #4 of 8 (292 views)

Permalink

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

Re: Re: Xend cannot start [ In reply to ]

konrad.wilk at oracle

Apr 18, 2011, 9:40 AM

Post #5 of 8 (292 views)

Permalink

On Mon, Apr 18, 2011 at 11:48:19PM +0800, ruozeng.w wrote:
> 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.

Where did you get the 2.6.39 kernel from?

Did you turn on CONFIG_PARAVIRT=y

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: Re: Xend cannot start [ In reply to ]

ruozeng.w at gmail

Apr 18, 2011, 7:56 PM

Post #6 of 8 (291 views)

Permalink

I got the 2.6.39-rc3 kernel full source from http://www.kernel.org.
And CONFIG_PARAVIRT is turned on.

Here is the steps I configure the kernel:
1. Processor type and features
High Memory Support--->
64GB
(Then I can see PAE and some xen related options)

2. Processor type and features
--- Paravirtualized guest support--->
[*]Xen guest support

3. Device Drivers
Xen Driver Support--->
(All turned on by default)

4. Device Drivers
Metwork device support--->
<*> Xen network device frontend driver
<*> Xen backend network device

5. Bus options
<*>Xen PCI Frontend

011-04-19

Wishes
Ruozeng W

·¢¼þÈË£º Konrad Rzeszutek Wilk
·¢ËÍÊ±¼ä£º 2011-04-19 00:40:18
ÊÕ¼þÈË£º ruozeng.w
³ËÍ£º Pasi Kärkkäinen; xen-devel
Ö÷Ìâ£º Re: Re: [Xen-devel] Xend cannot start

On Mon, Apr 18, 2011 at 11:48:19PM +0800, ruozeng.w wrote:
> 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.
Where did you get the 2.6.39 kernel from?
Did you turn on CONFIG_PARAVIRT=y

Re: Re: Re: Xend cannot start [ In reply to ]

konrad.wilk at oracle

Apr 19, 2011, 6:32 AM

Post #7 of 8 (289 views)

Permalink

On Tue, Apr 19, 2011 at 10:56:25AM +0800, ruozeng.w wrote:
> I got the 2.6.39-rc3 kernel full source from http://www.kernel.org.

The 2.6.39-rc3 does not have the blkback driver in. There is a version

git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git #master

that has that one.
> And CONFIG_PARAVIRT is turned on.

Ok, so that is there.
>
> Here is the steps I configure the kernel:
> 1. Processor type and features
> High Memory Support--->
> 64GB
> (Then I can see PAE and some xen related options)

OK, so you have the right version of Dom0. What about the version of
Xen-unstable? Are you compiling it from scratch?

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: Re: Xend cannot start [ In reply to ]

ruozeng.w at gmail

Apr 21, 2011, 1:49 AM

Post #8 of 8 (281 views)

Permalink

I've found some mistakes in my configuration of the linux kernel, and I can load those modules(xen-gntdev, xen-gntalloc, xen-evtchn) now.
And I've fixed the problem of missing scsi devices under /sys/bus/scsi/devices/ directory. I learned that /etc/init.d/xencommons should be started before starting xend.

I'll try to create new pv guests next step.
Thank you for your help.

One more question:
Does missing block device backend driver cause any problem?

2011-04-21

Wishes
Ruozeng W

·¢¼þÈË£º Konrad Rzeszutek Wilk
·¢ËÍÊ±¼ä£º 2011-04-19 21:33:45
ÊÕ¼þÈË£º ruozeng.w
³ËÍ£º xen-devel
Ö÷Ìâ£º Re: Re: Re: [Xen-devel] Xend cannot start

On Tue, Apr 19, 2011 at 10:56:25AM +0800, ruozeng.w wrote:
> I got the 2.6.39-rc3 kernel full source from http://www.kernel.org.
The 2.6.39-rc3 does not have the blkback driver in. There is a version
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git #master
that has that one.
> And CONFIG_PARAVIRT is turned on.
Ok, so that is there.
>
> Here is the steps I configure the kernel:
> 1. Processor type and features
> High Memory Support--->
> 64GB
> (Then I can see PAE and some xen related options)
OK, so you have the right version of Dom0. What about the version of
Xen-unstable? Are you compiling it from scratch?