On Tue, 2009-09-29 at 15:20 -0400, Jim Paris wrote:
> Nevermind that, my conclusions were bogus. Things still didn't quite add
> up, so I tracked down what's really going on here:
>
> - Libvirt 0.7.1 (as packaged by Debian) has IFF_VNET_HDR support.
> - Qemu-kvm 0.11.0 (as built by myself) did N
Jim Paris wrote:
> Daniel P. Berrange wrote:
> > On Tue, Sep 29, 2009 at 02:39:59AM -0400, Jim Paris wrote:
> > > Hi,
> > >
> > > After upgrading libvirt on one system, my kvm guests running a 2.6.26
> > > kernel with virtio networking could no longer communicate with the
> > > network.
> > >
> >
Daniel P. Berrange wrote:
> On Tue, Sep 29, 2009 at 02:39:59AM -0400, Jim Paris wrote:
> > Hi,
> >
> > After upgrading libvirt on one system, my kvm guests running a 2.6.26
> > kernel with virtio networking could no longer communicate with the
> > network.
> >
> > It seems that the problem is cau
On Tue, Sep 29, 2009 at 02:39:59AM -0400, Jim Paris wrote:
> Hi,
>
> After upgrading libvirt on one system, my kvm guests running a 2.6.26
> kernel with virtio networking could no longer communicate with the
> network.
>
> It seems that the problem is caused by newer libvirt versions
> unconditio
Hi,
After upgrading libvirt on one system, my kvm guests running a 2.6.26
kernel with virtio networking could no longer communicate with the
network.
It seems that the problem is caused by newer libvirt versions
unconditionally enabling GSO support by setting IFF_VNET_HDR [1].
However, support f
