+++ This bug was initially created as a clone of Bug #208062 +++ 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 is provided. 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): kernel-xen-2.6.17-1.2630.fc6 How reproducible: everytime Steps to Reproduce: 1. Boot FC6-test3 Xen0 2. Create XenU 3. insmod /lib/modules/.../xennet.ko 4. Xen0 Crashed. Actual results: XenU would crash Xen0. Expected results: Additional info: -- Additional comment from yongkang.you on 2006-09-26 02:57 EST -- Created an attachment (id=137108) xen0 crashed log -- Additional comment from yongkang.you on 2006-10-17 23:13 EST -- I have retested this issue. This bug is still in kernel-xen-2.6.18-1.2784.fc6
I think this specific problem is solved by the xencomm patches, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=210637
I confirmed that this issue is fixed at 2.6.18-1.2839.el5xen. Best Regards, Akio Takebe
2.6.18-7.el5 included in 20070125.1.
Confirmed in latest tree.