public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Konstantinos Agouros <elwood@agouros.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Xen-4.1 + Gentoo-Sources 3.0.6 in Dom0 = no blktap
Date: Sun, 13 Nov 2011 12:42:15 +0000 (UTC)	[thread overview]
Message-ID: <1321188134.988354@rumba> (raw)

Hi,

I am using Xen 3.4.2 with xensources for Dom0 and DomU at the moment.
Now I tried to upgrade on a testsystem to 4.1.1 and a 3.0.6 Kernel
for Dom0. The problem is, since there is no blktap driver in the 
3.0.6 Kernel I have to fall back to file:// instead of tap:aio for the
disks for the guests. Anybody knows a way around this?

Also I tried a 3.0.6 as a DomU kernel but this panics during boot time
with:

[    0.335389] Hangcheck: starting hangcheck timer 0.9.1 (tick is 180 seconds,
margin is 60 seconds).
[    0.335411] Hangcheck: Using getrawmonotonic().
[    0.336220] ------------[ cut here ]------------
[    0.336236] WARNING: at arch/x86/xen/mmu.c:486
xen_make_pte_debug+0xa0/0xfa()
[    0.336248] 0xfed40000 is using VM_IO, but it is 0xfffffffffffff000!
[    0.336259] Modules linked in:
[    0.336278] Pid: 1, comm: swapper Not tainted 3.0.6-gentoodomU #1
[    0.336289] Call Trace:
[    0.336309]  [<ffffffff8103bc74>] warn_slowpath_common+0x80/0x98
[    0.336327]  [<ffffffff8103bd20>] warn_slowpath_fmt+0x41/0x43
[    0.336344]  [<ffffffff81005999>] xen_make_pte_debug+0xa0/0xfa

Somebody can hint me, what in the Kernel-Config of the DomU kernel
might be wrong here? Xen-Sources 2.6.38 boots in this setup.

Regards,

Konstantin
-- 
Dipl-Inf. Konstantin Agouros aka Elwood Blues. Internet: elwood@agouros.de
Altersheimerstr. 1, 81545 Muenchen, Germany. Tel +49 89 69370185
----------------------------------------------------------------------------
"Captain, this ship will not survive the forming of the cosmos." B'Elana Torres



                 reply	other threads:[~2011-11-13 12:43 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=1321188134.988354@rumba \
    --to=elwood@agouros.de \
    --cc=gentoo-user@lists.gentoo.org \
    /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