| 1 |
On Wed, 2012-04-11 at 17:38 +0300, Konstantin wrote: |
| 2 |
> Greetings, |
| 3 |
> |
| 4 |
> Tuesday, April 10, 2012, 03:13:36, Hacking Network Solutions - Gentoo List Subscriptions wrote: |
| 5 |
> > On Mon, 2012-04-09 at 19:32 +0300, Konstantin wrote: |
| 6 |
> >> |
| 7 |
> >> What kernel versions are you using for Dom0? Today I've tried to use |
| 8 |
> >> sys-kernel/gentoo-sources-3.2.12 and couldn't find any backend driver |
| 9 |
> >> support. Am I missed something? ;) |
| 10 |
> >> |
| 11 |
> |
| 12 |
> > Hi Konstantin, |
| 13 |
> > I use Xen with Gentoo for both Dom0 and DomU. |
| 14 |
> > The back-end driver support is well hidden in the menus, |
| 15 |
> Device Drivers --->> Xen driver support ---> Backend driver support |
| 16 |
> > is required to show them. |
| 17 |
> > I have attached a working .config 3.2.12 for your convenience. |
| 18 |
> |
| 19 |
> Thank you very much for your kernel configuration file. I've tried to |
| 20 |
> compile 3.3.1-gentoo with slightly modified your .config by changing |
| 21 |
> CPU to Intel Core2 and disabling Xen unnecessary for Dom0 frontend |
| 22 |
> drivers. And kernel seems working, but not with the app-emulation/xen. |
| 23 |
> It still crashes while booting with something like: |
| 24 |
> |
| 25 |
> [ 1.391175] Code: 97 81 e8 5f ... |
| 26 |
> [ 1.394173] RIP [<ffffffff0141a9f5>] xen_irq_init+0x15/0xa0 |
| 27 |
> [ 1.394173] RSP <ffff...> |
| 28 |
> [ 1.394173] CR2: 0000000000000040 |
| 29 |
> [ 1.394173] ---[ end trace 4eaa2a86a8e2da22 ]--- |
| 30 |
> [ 1.395470] swapper/0 used greatest stack depth: 4264 bytes left |
| 31 |
> [ 1.395580] Kernel panic - not syncing: Attempted to kill init |
| 32 |
> |
| 33 |
> Right now I've tried to use latest xen ebuilds: |
| 34 |
> |
| 35 |
> [I] app-emulation/xen |
| 36 |
> Available versions: 3.4.2-r4!t 4.1.1-r2!t (~)4.1.2!t {acm custom-cflags debug flask pae xsm} |
| 37 |
> Installed versions: 4.1.2!t(05:24:10 PM 04/11/2012)(-custom-cflags -debug -flask -pae -xsm) |
| 38 |
> |
| 39 |
|
| 40 |
I may be wrong about this but I seem to remember reading somewhere that |
| 41 |
enabling Xen always enables PAE in the kernel (on 32-bit systems) which |
| 42 |
therefore requires that the pae use-flag be specified when building xen |
| 43 |
and xen-tools. |
| 44 |
|
| 45 |
|
| 46 |
> [I] app-emulation/xen-tools |
| 47 |
> 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} |
| 48 |
> 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) |
| 49 |
> |
| 50 |
> Trying to search my issue in bugzilla. May be someone could share some |
| 51 |
> hints? ;) |
| 52 |
> |
Archives