Re: Toughts on Virtualization
Konstantin <[email protected]> Wed, 11 Apr 2012 17:38:25 +0300
| Newsgroups | gmane.linux.gentoo.server |
|---|---|
| Message-ID | <[email protected]> |
Greetings,
Tuesday, April 10, 2012, 03:13:36, Hacking Network Solutions - Gentoo List Subscriptions wrote:
> On Mon, 2012-04-09 at 19:32 +0300, Konstantin wrote:
>>
>> What kernel versions are you using for Dom0? Today I've tried to use
>> sys-kernel/gentoo-sources-3.2.12 and couldn't find any backend driver
>> support. Am I missed something? ;)
>>
> Hi Konstantin,
> I use Xen with Gentoo for both Dom0 and DomU.
> The back-end driver support is well hidden in the menus,
Device Drivers --->> Xen driver support ---> Backend driver support
> is required to show them.
> I have attached a working .config 3.2.12 for your convenience.
Thank you very much for your kernel configuration file. I've tried to
compile 3.3.1-gentoo with slightly modified your .config by changing
CPU to Intel Core2 and disabling Xen unnecessary for Dom0 frontend
drivers. And kernel seems working, but not with the app-emulation/xen.
It still crashes while booting with something like:
[ 1.391175] Code: 97 81 e8 5f ...
[ 1.394173] RIP [<ffffffff0141a9f5>] xen_irq_init+0x15/0xa0
[ 1.394173] RSP <ffff...>
[ 1.394173] CR2: 0000000000000040
[ 1.394173] ---[ end trace 4eaa2a86a8e2da22 ]---
[ 1.395470] swapper/0 used greatest stack depth: 4264 bytes left
[ 1.395580] Kernel panic - not syncing: Attempted to kill init
Right now I've tried to use latest xen ebuilds:
[I] app-emulation/xen
Available versions: 3.4.2-r4!t 4.1.1-r2!t (~)4.1.2!t {acm custom-cflags debug flask pae xsm}
Installed versions: 4.1.2!t(05:24:10 PM 04/11/2012)(-custom-cflags -debug -flask -pae -xsm)
[I] app-emulation/xen-tools
Available versions: 3.4.2-r3 (~)3.4.2-r5 (~)4.1.1-r5 4.1.1-r6 (~)4.1.2-r2!t {acm api custom-cflags debug doc flask hvm pygrub qemu screen xend}
Installed versions: 4.1.2-r2!t(05:23:08 PM 04/11/2012)(api hvm pygrub qemu screen xend -custom-cflags -debug -doc -flask)
Trying to search my issue in bugzilla. May be someone could share some
hints? ;)
--
Konstantin