I had the same problem on a hardy amd64 hardy dom0 running xen 3.2 and kernel 2.6.24-21-xen. When I tried to install sun-java6-jdk on an i386 lucid domU.
I can confirm that the xen patch mentioned by Stefan in comment 58 solved my problem.
Before patching, the installation of sun-java6-bin crashed reliably, and calling 'dpkg --configure -a' showed this:
I applied the patch to the sources of xen-hypervisor-3.2_3.2.0_amd64.deb, rebooted with the patched hypervisor and the old dom0 kernel (2.6.24-21-xen).
The dpkg --configure step didn't crash the domU, and I can run tomcat6. Up to now, there has been no heavy load on the instance. I'll report back if I experience crashes.
I had the same problem on a hardy amd64 hardy dom0 running xen 3.2 and kernel 2.6.24-21-xen. When I tried to install sun-java6-jdk on an i386 lucid domU.
I can confirm that the xen patch mentioned by Stefan in comment 58 solved my problem.
Before patching, the installation of sun-java6-bin crashed reliably, and calling 'dpkg --configure -a' showed this:
----- 0ubuntu1~ lucid1~ ppa1) ... alternatives: using /usr/lib/ jvm/java- 6-sun/jre/ bin/ControlPane l to provide /usr/bin/ ControlPanel (ControlPanel) in auto mode. alternatives: using /usr/lib/ jvm/java- 6-sun/jre/ lib/jexec to provide /usr/bin/jexec (jexec) in auto mode. buildd/ linux-ec2- 2.6.32/ arch/x86/ mm/hypervisor. c:461! uevent_ seqnum entry_update+ 0x12d/0x1b0 0x9e/0xc0 0x99/0xa0 mm_fault+ 0x509/0x5b0 0x23a/0x2d0 fault+0x119/ 0x340 fault+0x0/ 0x340 0x3d/0x44
Setting up sun-java6-bin (6.21dlj-
update-
...
update-
[ 51.946179] ------------[ cut here ]------------
[ 51.946188] kernel BUG at /build/
[ 51.946192] invalid opcode: 0000 [#1] SMP
[ 51.946197] last sysfs file: /sys/kernel/
[ 51.946200] Modules linked in: ipv6
[ 51.946204]
[ 51.946208] Pid: 836, comm: java Not tainted (2.6.32-317-ec2 #36-Ubuntu)
[ 51.946211] EIP: 0061:[<c01184c0>] EFLAGS: 00010282 CPU: 0
[ 51.946217] EIP is at T.571+0x150/0x180
[ 51.946219] EAX: ffffffea EBX: e1dc3e70 ECX: 00000002 EDX: 00000000
[ 51.946222] ESI: b70d8000 EDI: 00000003 EBP: e1dc3ebc ESP: e1dc3e60
[ 51.946225] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0069
[ 51.946228] Process java (pid: 836, ti=e1dc2000 task=e19f72f0 task.ti=e1dc2000)
[ 51.946231] Stack:
[ 51.946233] c1df9960 e1dc3ee0 80000000 00000061 0000000e 00000000 e1a4b000 b70d8061
[ 51.946243] <0> 80000003 00000000 00000000 00000040 00000001 ffffffea e1dc3ee0 00000001
[ 51.946253] <0> 00000000 00007ff0 00000000 00000000 b70d8001 00000003 c233a000 e1dc3efc
[ 51.946265] Call Trace:
[ 51.946271] [<c011884d>] ? xen_l3_
[ 51.946276] [<c011454e>] ? pud_populate+
[ 51.946281] [<c01af189>] ? __pmd_alloc+
[ 51.946285] [<c01b35b9>] ? handle_
[ 51.946290] [<c01b833a>] ? do_munmap+
[ 51.946295] [<c0537d59>] ? do_page_
[ 51.946300] [<c0537c40>] ? do_page_
[ 51.946304] [<c0536185>] ? error_code+
----
I applied the patch to the sources of xen-hypervisor- 3.2_3.2. 0_amd64. deb, rebooted with the patched hypervisor and the old dom0 kernel (2.6.24-21-xen).
The dpkg --configure step didn't crash the domU, and I can run tomcat6. Up to now, there has been no heavy load on the instance. I'll report back if I experience crashes.
Thank you, Stefan.