xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: 신용진 <akayong@gmail.com>
To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Xen causes hang when reboot or shutdown.
Date: Mon, 15 Mar 2010 15:32:00 +0900	[thread overview]
Message-ID: <004201cac409$39e10b40$ada321c0$@com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2532 bytes --]

I am trying to make xen-virtualization system

 

My machine is

CPU : Intel Xeon E5520 * 2
RAM : DDR3 1333 2GB * 6
HDD : 500GB SATA * 4 (RAID 10)

 

CentOS5.3 Kernel - 2.6.27.29-0.1.1 (original was 2.6.18-128 and I upgraded)

Xen - 3.4.2  (http://www.gitco.de/repo/GITCO-XEN3.4.2_x86_64.repo)

 

 

When I boot my computer, it shows some messages like below;

 

Starting xend: Nothing to flush

FATAL : Module netloop not found

FATAL : Module netlbk not found,

FATAL : Module blkbk not found,

FATAL : Module blktap not found,

 

And when I reboot It starts to hang.

 

As I surveyed, from Xen 3.3 and later, we should install above modules in
Xen-kernel, not separate modules.

So I set those modules install in xen-kernel. 

(I mean, when we set menuconfig (make menuconfig), it should be [*], not
[M])

 

However, when I look through the /etc/init.d/xend source, they have
“modprobe” sentence.

 

So I changed all those modules as ‘<M>’ in menuconfig.

After this, netloop and netbk was installed, however, blkbk and blktap was
not installed.

 

So, I installed netloop and net bk as Module, and blkbk and blktap in xen-
kernel.

The, I boot my computer, it shows some messages like below;

 

Starting xend: Nothing to flush

FATAL : Module blkbk not found,

FATAL : Module blktap not found,

 

And when I reboot, it starts to hang again!

 

After that, I commented out “modprobe blkbk” and “modprobe blktap” in
/etc/init.d/xend file., then it doesn’t show those messages,

However, it hangs again.

 

When I boot my machine without xend, then it does not show hang.

 

And I did googling and I found that other people have same problem like me,
and it is caused by blktap.

And some people give some solutions and patch for blktap, however, those
kernel version or xen version is different from mine, So I could not apply
them to my computer.

Follows are links that I referenced

http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00146.html

http://lists.xensource.com/archives/html/xen-devel/2010-01/msg01152.html

http://wiki.xensource.com/xenwiki/XenDom0Kernels

http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/ma
ster;pg=0

http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/ma
ster;pg=4

http://permalink.gmane.org/gmane.comp.emulators.xen.devel/78670

 

Is there any solution or patch files for this problem?

 


[-- Attachment #1.2: Type: text/html, Size: 8750 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

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

                 reply	other threads:[~2010-03-15  6:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='004201cac409$39e10b40$ada321c0$@com' \
    --to=akayong@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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).