From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Anyone successful in paravirtualizing Gentoo on XenServer?
Date: Thu, 24 Mar 2011 13:57:52 +0100 [thread overview]
Message-ID: <71f4cdc6bb8c910ba00e496f024d2f53.squirrel@www.antarean.org> (raw)
In-Reply-To: <AANLkTikcCmO5sSON954zCkRpc=yLxPXaTJik3AfSbZAz@mail.gmail.com>
On Thu, March 24, 2011 1:19 pm, Pandu Poluan wrote:
> On Thu, Mar 24, 2011 at 18:21, J. Roeleveld <joost@antarean.org> wrote:
>> On Thu, March 24, 2011 10:36 am, Pandu Poluan wrote:
>>> On Thu, Mar 24, 2011 at 15:32, J. Roeleveld <joost@antarean.org> wrote:
>
> -- snip --
>
>>>> Hmm... I don't use kernel-modules in my Xen domu's (All are PV). I
>>>> wonder
>>>> if compiling them into the kernel might help.
>>>> Or, try loading the modules listed above and see if that helps. (Not
>>>> sure
>>>> if you can see an immediate change though)
>>>>
>>>
>>> Can't hurt to try, now that I've gotten a bootable kernel. Can always
>>> fallback to the previous one.
>>
>> Let me know how that goes.
>>
>
> Compiling all the <M> into <*> still results the same *sigh*
Ok, then we'll need to look into things that are not added at all.
The following might be the one you're missing:
CONFIG_XEN_KEYBOARD=y
It is in my config, but not in yours.
> I also tried your .config ( make oldconfig && make menuconfig &&
> genkernel --oldconfig bzImage && genkernel --oldconfig initramfs ),
> and something strange happened:
>
> The VM seems to be starting... then ended immediately. But no error
> message at all.
Could have a few reasons:
- I have the "compatibility" for xen reduced to 3.4 or higher. Not sure
which xen-version is included in yours.
- I do not have support for an initramfs or similar in there
- I specified the CPU-type in the kernel (It's not a generic one)
Did you check the logs for xend, system (messages) and others?
>>>> Please note, I do use the following kernel:
>>>> sys-kernel/xen-sources-2.6.34-r4
>>>>
>>>> Which kernel are you using?
>>>>
>>>
>>> hardened-sources-2.6.36-r9 IIRC
>>>
>>> Hmmmm... there are *lots* of options in your config that I don't see in
>>> mine.
>>
>> Can you add a list of the ones you are missing?
>>
>
> Um... lots. I'll attach the last config I've tried.
>
>>> Could it be because of the "hardened" sources?
>>
>> My guess is, because you're not having the xen-patchset in the kernel.
>> Can you try the xen-sources to see if that helps?
>> Then we can work our way through the missing options.
>>
>
> Okay, emerging xen-sources now... this will take some time. I'll post
> after testing again.
Looking forward to the result.
--
Joost
next prev parent reply other threads:[~2011-03-24 12:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 17:03 [gentoo-user] Anyone successful in paravirtualizing Gentoo on XenServer? Pandu Poluan
2011-03-24 5:30 ` [gentoo-user] " Pandu Poluan
2011-03-24 6:37 ` Pandu Poluan
2011-03-24 7:47 ` J. Roeleveld
2011-03-24 8:20 ` Pandu Poluan
2011-03-24 8:32 ` J. Roeleveld
2011-03-24 9:36 ` Pandu Poluan
2011-03-24 11:21 ` J. Roeleveld
2011-03-24 12:19 ` Pandu Poluan
2011-03-24 12:57 ` J. Roeleveld [this message]
2011-03-24 13:02 ` J. Roeleveld
2011-03-24 13:10 ` Pandu Poluan
2011-03-24 14:28 ` J. Roeleveld
2011-03-29 8:28 ` Pandu Poluan
2011-03-29 9:22 ` Joost Roeleveld
2011-03-29 10:44 ` Pandu Poluan
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=71f4cdc6bb8c910ba00e496f024d2f53.squirrel@www.antarean.org \
--to=joost@antarean.org \
--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