I've just was able to reproduce Thiago's instruction on Lucid RC for Xen 4.0 & 2.6.32.10 pvops kernel ( C2D E8400 , ASUS P5Q-E, 8 GB RAM) . ACPI Processor
has been disabled, what is particular MB issue
Quote :-
1.Clone JF's Git Repo:
cd /usr/src
git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen
cd linux-2.6-xen
git checkout -b xen/stable origin/xen/stable
2. Configure, compile and install:
make menuconfig # Enabled the dom0 support and the Xen backend as usual on U 9.10, F12
make -j2
chmod g-s /usr/src -R
make deb-pkg
dpkg -i ../linux-image*2.6.32.10*.deb
depmod 2.6.32.10
update-initramfs -c -k
2.6.32.10
update-grub
echo "xen-evtchn" >> /etc/modules
3- Download and install the latest Xen:
Preparing your environment:
apt-get build-dep xen-3.3
aptitude install uuid-dev iasl texinfo
Download and compile:
cd /usr/src
Uncompress xen-4.0.0.tar.gz
cd xen-4.0.0
make xen
make tools
make install-xen
make install-tools PYTHON_PREFIX_ARG=
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20
4. Add to /boot/grub/grub.cfg
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Xen 4.0 / Ubuntu 10.4 RC kernel 2.6.32.10 pvops" {
insmod ext2
set root=(hd1,4)
multiboot (hd1,4)/xen.gz
dummy=dummy
module (hd1,4)/vmlinuz-2.6.32.10 dummy=dummy root=/dev/sdb5 ro console=tty0
module (hd1,4)/initrd.img-2.6.32.10
Quote ends.
--- On
Fri, 4/23/10, Gerry Reno <greno@xxxxxxxxxxx> wrote:
From: Gerry Reno <greno@xxxxxxxxxxx>
Subject: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Friday, April 23, 2010, 1:50 PM
I previously had the pv_ops dom0 2.6.31.6 kernel built and running on my hardware (amd phenom ii x4 quad-core) just fine under karmic. But that kernel had issues with rxchecksumming. So I upgraded the server to lucid and am now trying to compile a new pv_ops dom0 kernel for it.
Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) pv_ops dom0 kernel twice.
Once from the config in the email Lucid pv_ops dom0 howto and once from the lucid server config modified by adding all the XEN configurations. I get the same result both ways. After building the kernel, I try to start the pv_ops dom0 kernel as domU just to make sure it runs and it crashes right at the start of boot complaining like this:
__vmallic_node+0xa2/0xb0
? alloc_large_system_hash+0x15/0x21
? inet_init+0x0/0x209
__vmalloc+0x22/0x30
alloc_large_system_hash+0x15/0x21a
? inet_init+0x0/0x209
? inet_init+0x0/0x209
tcp_init+0xa3//0x37e
inet_init+0x14b/0x209
do_one_initcall+0x3c/0x10a
kernel_init+0x159/0x1af
child_rip+0xa/0x20
Code: d0 49 8b 04 24 48 85 c0 75 ec eb c5 55 48 89 e5 48 8....
9 5d e8 4c 89 65 f0 4c 89 6d f8 0f 1f 44 00 00 48 89 e5 48 8....
RIP [<ffffffff810f4f5f>] __free_pages+0x1f/0x90
---[ end trace e93713a9d40cd06d ]---
Kernel panic - not syncing: Attempted to kill
init!
Pid: 1, comm: swapper Tainted: G D W 2.6.32.10 #4
panic+0x78/0x136
? mm_release+0x60/0x130
do_exit+0x6ca/0x7f0
oops_end+0xaf/0xf0
die+0x5b/0x90
do_general_protection+0x152/0x160
general_protection+0x25/0x30
? __free_pages+0x1f/0x90
__vunmap+0x7a/0x110
vfree+0x2a/0x30
__vmalloc_area_node+0x15c/0x190
? alloc_large_system_hash+0x15a/0x21a
__vmalloc_node+0xa2/0xb0
? alloc_large_system_hash+0x15a/0x21a
? inet_init+0x0/0x209
? inet_init+0x0/0x209
tcp_init+0xa3//0x37e
inet_init+0x14b/0x209
do_one_initcall+0x3c/0x10a
kernel_init+0x159/0x1af
child_rip+0xa/0x20
? kernel_init+0x10/0x1af
? child_rip+0x0/0x20
I fired up the old 2.6.31.6 kernel with lucid and it boots just fine as domU.
Can anyone shed some light on what may be the problem here and how I can build a working 2.6.32.10 pv_ops dom0 kernel for this hardware?
-Gerry
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel