Description of problem: I have FC4 and FC development installed on the affected boxes, with separate /boot partitions that I use to choose which one to boot into. The root filesystem of each one is mountable on the other, such that I can install updates on both without having to reboot into each of the systems (selinux=0). The last time this worked was on 20060221, running rawhide from 20060220. From the next day on, running rawhide from 20060221, chrooting to the FC4 install would simply segfault, while running kernel-xen-hypervisor. If I boot into the non-xen kernel, chroot works just fine. This affects all of the boxes on which I've been trying Xen (same as those affected by bug 182608). Version-Release number of selected component (if applicable): xen-3.0.1-0.20060208.fc5.2 kernel-xen-hypervisor-2.6.15-1.1975_FC5.i686 How reproducible: Every time Steps to Reproduce: 1.Boot into Fedora devel 2.Mount the root filesystem of an FC4 install 3.chroot to it Actual results: Segmentation fault Expected results: A shell with the FC4 install as root Additional info:
I've just realized that, before installing the 20060221 updates, I was *not* running the Xen kernel. I'd modified grub to boot into the non-Xen kernel, but I had not modified /etc/sysconfig/kernel, so when I updated the kernel, it switched to the Xen kernel by default. So this was not quite a Xen regression, just a regular Xen bug.
Can you strace the chroot and see exactly where it's SEGVing, please?
It doesn't crash any more after the latest xen update.