> I have a new kernel (2.6.38-0.rc4.git3.1.xendom0.fc15) at
> http://koji.fedoraproject.org/koji/taskinfo?taskID=2833991 . This uses the
> Konrad's devel/next-2.6.38 branch (from
> http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git ), as I have been
> having trouble which Jeremy's xen/next-2.6.38 branch.
> It has the revised xen-netback patches, so doesn't need the hack to
> /etc/sysconfig/modules/xen.modules that the previous kernel needed to
> avoid backtraces (indeed the hack stops xen-netback loading with this
> kernel as the netback_kthread parameter has been dropped).
I just booted 2.6.38-0.rc4.git3.1.xendom0.fc15 on
xen-4.1.0-0.1.rc4.fc14.x86_64. I end up with the xen_netback kernel
$ lsmod | grep net
xen_netback 24607 0 [permanent]
I'm not sure if this is what you were refering to by "indeed the hack
stops xen-netback loading..."
It also seems that my DomU does not have its network facilities set up. I
don't end up with a vifX.Y device on Dom0. This is different behavior
than what was provided by Michael's previous kernel package. With
the previous one, DomU would have network connectivity after booting,
although eventually it would seem to break.
xen mailing list