WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Xen 3.4.0 and Linux Kernel 2.6.29.5: Success, but...

To: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Xen 3.4.0 and Linux Kernel 2.6.29.5: Success, but...
From: Stephan Austermühle <au@xxxxxxx>
Date: Thu, 18 Jun 2009 10:41:44 +0200
Delivery-date: Thu, 18 Jun 2009 01:47:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.21 (Windows/20090302)
Hi all,

my Xen 3.3.1 (64bit) and Linux 2.6.26 (64bit, Debian Lenny) worked well and 
stable as long as I ran Linux domU's only. Unfortunately I have to run a 
Windows (Server 2008, 64bit) domU that causes physical server reboots after 
some minutes up to some days (GPLPV 0.10.0.69 installed) depending on (I/O?) 
activity. Thus I decided to upgrade to Xen 3.4.0 and Linux 2.6.29.5. The error 
message

        Error: Device 0 (vif) could not be connected. Hotplug scripts not 
working.

drove me nuts until I have reviewed the Linux config and found that some Xen 
options have to be build into the kernel instead of modules.

Finally I got Xen 3.4.0 and Linux 2.6.29.5 (dom0) running. I have tested to run 
domU's with 2.6.29.5 but that throws error messages (see attached logs) 
although it seems to run (can anybody tell what those error message mean and if 
they are critical?). Anyway, for now it is okay to run 2.6.26.

Next step: Configure HVM, setup W2k8 (installation was corrupted somehow). 
Reboot: okay, system comes up. Installing GPLPV 0.10.0.69: System reboots 
during boot without an error message or shows the BSOD with stop code 
0x0000005C or 0x0000007B. Upgraded to Xen 3.4.1-rc3 but it looks like this 
GPLPV version is simply not compatible with Xen 3.4.

Just for the records: I took the patches for kernel 2.6.29.5 from

        http://code.google.com/p/gentoo-xen-kernel/downloads/list

By the way, I would really appreciate it if the nasty 2.6.18 dependency would 
be dropped by whatever (pv_ops, dom0 integration into the mainstream kernel, or 
"official" patches against recent kernels).

Next is to test PCI passthrough because Xen 3.3 broke it. But that's something 
for one of the next weekends...

Anybody having the same experience or knows how to make W2k8 run fast and 
stable in a domU?

Kind regards,

Stephan
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.29.5-hcsd-1 (root@n0002) (gcc version 4.3.2 
(Debian 4.3.2-1.1) ) #3 SMP Wed Jun 17 20:45:27 CEST 2009
[    0.000000] Command line: root=/dev/hda1 ro console=xvc0 
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] Xen-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 0000000100800000 (usable)
[    0.000000] last_pfn = 0x100800 max_arch_pfn = 0x80000000
[    0.000000] last_pfn = 0x100000 max_arch_pfn = 0x80000000
[    0.000000] init_memory_mapping: 0000000000000000-0000000100000000
[    0.000000] last_map_addr: 100000000 end: 100000000
[    0.000000] init_memory_mapping: 0000000100000000-0000000100800000
[    0.000000] last_map_addr: 100800000 end: 100800000
[    0.000000] RAMDISK: 00da3000 - 02203000
[    0.000000] ------------[ cut here ]------------
[    0.000000] WARNING: at drivers/firmware/dmi_scan.c:425 
dmi_matches+0x2a/0x76()
[    0.000000] dmi check: not initialized yet.
[    0.000000] Modules linked in:
[    0.000000] Pid: 0, comm: swapper Not tainted 2.6.29.5-hcsd-1 #3
[    0.000000] Call Trace:
[    0.000000]  [<ffffffff8022d95d>] warn_slowpath+0xd8/0x112
[    0.000000]  [<ffffffff80243f34>] up+0xe/0x36
[    0.000000]  [<ffffffff8022e5b3>] vprintk+0x2be/0x319
[    0.000000]  [<ffffffff8046bad4>] printk+0x4e/0x5a
[    0.000000]  [<ffffffff803e4944>] dmi_matches+0x2a/0x76
[    0.000000]  [<ffffffff803e49cc>] dmi_check_system+0x15/0x41
[    0.000000]  [<ffffffff805b0095>] setup_arch+0x391/0xda3
[    0.000000]  [<ffffffff805b8780>] cgroup_init_subsys+0x105/0x10e
[    0.000000]  [<ffffffff805aa729>] start_kernel+0x98/0x3d3
[    0.000000]  [<ffffffff805aa1c1>] x86_64_start_kernel+0xaf/0xb5
[    0.000000] ---[ end trace 4eaa2a86a8e2da22 ]---
[    0.000000] ------------[ cut here ]------------

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Xen 3.4.0 and Linux Kernel 2.6.29.5: Success, but..., Stephan Austermühle <=