For additionial information, i've placed some printf's within KVMs e1000 emualted drivers.
It turns out the within the e1000 receive function (e1000_receive) the correct size is received. Somewhere between there and the upper layers something goes wrong. I am continuing to investiage this problem, but if anyone else shed some light on this I would be greatful. 2008/10/30 Matthew Faulkner <[EMAIL PROTECTED]>: > I'm not using a bridge. And i have set the mtu on both tapX and ethX to 9000. > > Having done a little packet sniffing from the hostmachine -> virtual > machine I can see that packets of the correct (large) size are being > sent. Whilst sniffing on the virtual machine I don't see any packets. > This indicates to me that the network emulation drivers in KVM aren't > setup correctly? > > I'm using the e1000 drivers. > > Anyone any thoughts? > > 2008/10/30 Javier Guerra <[EMAIL PROTECTED]>: >> On Thu, Oct 30, 2008 at 4:41 AM, Matthew Faulkner >> <[EMAIL PROTECTED]> wrote: >>> I go no respone. So i started with a lower packet size and figured out >>> below a size of 4054 packets were sent and recevied (without ip >>> fragmentation), however, as soon as the packets were >= 4055 it >>> stopped working. >>> >>> Is this a known problem? Have I set something up incorrectly? >> >> are you using a bridge? it has some problems with long packets. >> >> if you can, try without a bridge. if not, make sure that you set the >> MTU of both ethX and tapX to 9000 before adding anything to the >> bridge. i think the bridge itself has its own MTU that is set >> according to the interfaces it gets; but i don't know if it can change >> MTU when an interface changes. >> >> >> -- >> Javier >> > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
