With kernel-xen-2.6.27-0.2.rc0.git6.fc10.x86_64 Running a 32 bit binary on Intel x86_64 Xen DomU: $> strace /usr/bin/newaliases ... open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(0x3, 0xffd8ea60) = 0 mmap2(NULL, 38827, PROT_READ, MAP_PRIVATE, 3, 0) = 0xfffffffff7e9f000 close(3) ... mprotect(0xf7842000, 4096, PROT_READ) = 0 mprotect(0xf7865000, 4096, PROT_READ) = 0 mprotect(0xf7881000, 4096, PROT_READ) = 0 mprotect(0xf7add000, 8192, PROT_READ) = 0 mprotect(0xf7b56000, 4096, PROT_READ) = 0 mprotect(0xf7ba4000, 4096, PROT_READ) = 0 mprotect(0xf7bb9000, 4096, PROT_READ) = 0 mprotect(0xf7ec5000, 4096, PROT_READ) = 0 munmap(0xf7e9f000, 38827) = 0 --- SIGSEGV (Segmentation fault) @ 0 (0) --- and dmesg shows: newaliases[2907] general protection ip:0 sp:0 error:0 It's a known issue with sysenter/vdso from a compat-mode 32 bit userspace. A workaround is to boot with "vdso32=0" on the kernel command line
Looks like Jeremy and Eduardo found the fix for this: http://lkml.org/lkml/2008/7/21/409
The following patch to fix sysexit is equally important.
Yep, thanks - I figured as much, just didn't link to it. But here it is: http://lkml.org/lkml/2008/7/21/410
kernel-xen is dead, moving to kernel
This is long fixed AFAIR