On Mon, Feb 06, 2012 at 12:55:55PM -0800, Greg A. Woods wrote: > > Either that or maybe the support for the unique chips it alone can > handle should be migrated to rtk(4) and re(4) should be sent to the bit > bucket. (That's said with my only, at least even semi-recent, > experience with the both of them being now with XenClient.) That's pretty silly. The chips have two different modes, and the legacy mode rtk uses has awful performance -- as you have just found. A broken implementation that claims it's an 8169-like chip, on the part of QEMU or Xen, isn't a reason to cripple or discard a driver that works with the real hardware. Thor