From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: zhangxiang <zhangxiang@ncic.ac.cn>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Booting Failures when using linux-2.6.33.2 asDomUwith paravirt-ops support
Date: Tue, 20 Apr 2010 14:46:48 -0400 [thread overview]
Message-ID: <20100420184648.GC32720@phenom.dumpdata.com> (raw)
In-Reply-To: <201004201615103595854@ncic.ac.cn>
> I do not use any logical volumes, so I do not need to use LVM name when writing the guest
> configuration file. In linux-2.6.33.2, CONFIG_DM_LINEAR does not exist. Thus I select the
> corresponding one as "y", which named CONFIG_BLK_DEV_DM. However, it also does not work,
> and the output is the same.
>
> It is really a difficult problem for me. Thank you again for your help!
I believe you are hitting in the problem that your initrd was created
with older tools (say RHEL5 ones) which expect a certain SysFS layout. The new kernels
have a different one and require this options to be turned on:
CONFIG_SYSFS_DEPRECATED_V2=y
next prev parent reply other threads:[~2010-04-20 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 8:58 Booting Failures when using linux-2.6.33.2 as DomU with paravirt-ops support zhangxiang
2010-04-19 13:48 ` Konrad Rzeszutek Wilk
2010-04-19 14:29 ` Booting Failures when using linux-2.6.33.2 as DomUwith " zhangxiang
2010-04-19 15:50 ` Konrad Rzeszutek Wilk
2010-04-20 8:15 ` Booting Failures when using linux-2.6.33.2 asDomUwith " zhangxiang
2010-04-20 18:46 ` Konrad Rzeszutek Wilk [this message]
2010-04-21 7:41 ` Booting Failures when using linux-2.6.33.2asDomUwith " zhangxiang
2010-04-21 13:09 ` Konrad Rzeszutek Wilk
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=20100420184648.GC32720@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=zhangxiang@ncic.ac.cn \
/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).