[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] xen-netback: make feature-rx-notify mandatory -- Breaks stubdoms
On 10/12/14 13:42, John wrote: > David, > > This patch you put into 3.18.0 appears to break the latest version of > stubdomains. I found this out today when I tried to update a machine to > 3.18.0 and all of the domUs crashed on start with the dmesg output like > this: Cc'ing the lists and relevant netback maintainers. I guess the stubdoms are using minios's netfront? This is something I forgot about when deciding if it was ok to make this feature mandatory. The patch cannot be reverted as it's a prerequisite for a critical (security) bug fix. I am also unconvinced that the no-feature-rx-notify support worked correctly anyway. This can be resolved by: - Fixing minios's netfront to support feature-rx-notify. This should be easy but wouldn't help existing Xen deployments. Or: - Reimplement feature-rx-notify support. I think the easiest way is to queue packets on the guest Rx internal queue with a short expiry time. > [ 83.045785] device vif2.0 entered promiscuous mode > [ 83.059220] vif vif-2-0: 22 feature-rx-notify is mandatory > [ 83.060763] vif vif-2-0: 1 mapping in shared page 2047 from domain 2 > [ 83.060861] vif vif-2-0: 1 mapping shared-frames 2047/2046 port tx 4 > rx 4 > > This is on the very latest patched version of 4.4. David _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |