Description of problem: I have tested latest Xen RPMs in IA32 and x86_64 platform. Xen/XenU/VMX hasn't problem to run in IA32 platform. But in x86_64 platform, if I destroy a VMX domain, the Xen0 will hang. XenU hasn't this problem. I paste the serial port output to attachment. Version-Release number of selected component (if applicable): kernel-xen0-2.6.15-1.2032_FC5.x86_64.rpm kernel-xenU-2.6.15-1.2032_FC5.x86_64.rpm xen-3.0.1-3.x86_64.rpm OR: kernel-xen0-2.6.15-1.2025_FC5.x86_64.rpm kernel-xenU-2.6.15-1.2025_FC5.x86_64.rpm xen-3.0.1-2.x86_64.rpm How reproducible: Every time. Steps to Reproduce: 1. Install Xen RPMs in FC5-test3 2. Reboot system and go into Xen0 3. Xend start 4. Create a VMX domain 5. After VMX domain is booted up, destroy it in Xen0 or poweroff in VMX. 6. Whole system is hang. Actual results: Xen0 hang, if destroy VMX in x86_64 platform. Expected results: Additional info:
Created attachment 125790 [details] serial port output when xen0 hang.
A fix for this got committed to the upstream Xen repository today. Jeremy? James? Feel like pulling in this patch?
Juan, please pull in upstream xen-unstable.hg csets 9232 and 9236 to fix this.
:) Any updates?
These have been committed and should appear in the next FC5 updates kernel.
Closing on basis that comment #5 says its fixed & FC5 is end-of-life.