On Wednesday 08 September 2010, Krishna Kumar2 wrote: > > The new guest and qemu code work with old vhost-net, just with reduced > > performance, yes? > > Yes, I have tested new guest/qemu with old vhost but using > #numtxqs=1 (or not passing any arguments at all to qemu to > enable MQ). Giving numtxqs > 1 fails with ENOBUFS in vhost, > since vhost_net_set_backend in the unmodified vhost checks > for boundary overflow. > > I have also tested running an unmodified guest with new > vhost/qemu, but qemu should not specify numtxqs>1. Can you live migrate a new guest from new-qemu/new-kernel to old-qemu/old-kernel, new-qemu/old-kernel and old-qemu/new-kernel? If not, do we need to support all those cases? Arnd -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
