xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jia Rao <rickenrao@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Problems with xen and linux 2.26.32 kernels for dom0
Date: Wed, 16 Jun 2010 15:00:03 -0400	[thread overview]
Message-ID: <AANLkTilUPKPuECSWT_ySDkKfdLs5OPwlzFnW5Op6_SSd@mail.gmail.com> (raw)


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

Hi all,

I used to use xen 3.4.2 and linux 2.6.18-xen kernels for both dom0 and domU,
without any problems.

Recently, I need to try io bandwidth control like dm-ioband in the new
kernel 2.6.32 (dm-ioband has patches for this kernel). It gave me a lot of
problems if I want to upgrade the dom0 to 2.6.32. The following is what I
tried and the errors.


Xen: 3.4.3 (I need to stick with 3.4.x. 3.4.3 is the one that can run pvops)

*First approach:*
I tried to download pvops from the git repository xen/stable-2.6.32.x. The
compilation was OK, but the initrd has a lot missing dependencies. I tried
to use --builtin to claim those missing modules in kernel. However, with the
generated initrd, dom0 can not boot. I got the error: *unable to locate
IOAPIC for GSIx and mount: could not find filesystem: /dev/root*.
I enabled : CONFIG_SYSFS_DEPRECATED=y,  CONFIG_SYSFS_DEPRECATED_V2=y and
tried to use root=/dev/sdax or root=LABEL=/. No luck.

*Second approach:*
Then I switched to the forward ported 2.6.32.13 kernel generated from the
gentoo xen kernel patches.

Still xen 3.4.3. After compilation, dom0 booted successfully. However I
previous domU which has 2.6.18-xen kernels can not boot. It has the same
error: *mount: could not find filesystem: /dev/root
*Do I need to create a initrd for the domU? I didnt need one when dom0 is
2.6.18-xen kernel.
*
*BTW. I dont see a PARAVIRT_GUEST config option in the forward ported 2.6.32
kernel*.

*Any ideas?
Thanks in advance!*
*

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

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

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

             reply	other threads:[~2010-06-16 19:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 19:00 Jia Rao [this message]
2010-06-16 19:43 ` Problems with xen and linux 2.26.32 kernels for dom0 Konrad Rzeszutek Wilk
2010-06-16 21:06   ` Jia Rao
2010-06-17 13:08     ` Konrad Rzeszutek Wilk
2010-06-18 15:24       ` Jia Rao

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=AANLkTilUPKPuECSWT_ySDkKfdLs5OPwlzFnW5Op6_SSd@mail.gmail.com \
    --to=rickenrao@gmail.com \
    --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).