Red Hat Bugzilla – Bug 208062
[IA64-Xen] XenU would crash Xen0, if insmod xennet.ko
Last modified: 2008-02-26 18:28:27 EST
Description of problem:
After recreate initrd by following description of bug #207241, xenU can be
booted up successfully. But XenU VNIF can not work properly, even if vif option
If manually insmod xennet.ko in xenU, it will trigger xen0 crashing.
The crashing log will put to the attachment.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot FC6-test3 Xen0
2. Create XenU
3. insmod /lib/modules/.../xennet.ko
4. Xen0 Crashed.
XenU would crash Xen0.
Created attachment 137108 [details]
xen0 crashed log
I have retested this issue. This bug is still in kernel-xen-2.6.18-1.2784.fc6
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
change QA contact
This report targets FC6, which is now end-of-life.
Please re-test against Fedora 7 or later, and if the issue persists, open a new bug.