Bug 182614

Summary:	can't chroot to FC4 install from FC devel install with kernel-xen-hypervisor
Product:	[Fedora] Fedora	Reporter:	Alexandre Oliva <oliva>
Component:	kernel-xen	Assignee:	Juan Quintela <quintela>
Status:	CLOSED RAWHIDE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	bstein, sct
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-03-01 20:15:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	179599

Description Alexandre Oliva 2006-02-23 17:46:03 UTC

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:

Comment 1 Alexandre Oliva 2006-02-23 17:51:11 UTC

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.

Comment 2 Stephen Tweedie 2006-02-24 20:39:50 UTC

Can you strace the chroot and see exactly where it's SEGVing, please?

Comment 3 Alexandre Oliva 2006-03-01 20:15:37 UTC

It doesn't crash any more after the latest xen update.