"Michael S. Tsirkin" writes:
> On Wed, Nov 30, 2016 at 01:16:59PM +0100, Maxime Coquelin wrote:
>>
>>
>> On 11/30/2016 12:23 PM, Jason Wang wrote:
>> >
>> >
>> > On 2016年11月30日 18:10, Maxime Coquelin wrote:
>> > > This series implements Virtio spec update from Aaron Conole
On Wed, Nov 30, 2016 at 01:16:59PM +0100, Maxime Coquelin wrote:
>
>
> On 11/30/2016 12:23 PM, Jason Wang wrote:
> >
> >
> > On 2016年11月30日 18:10, Maxime Coquelin wrote:
> > > This series implements Virtio spec update from Aaron Conole which
> > > defines a way for the host to expose its max
On 11/30/2016 12:23 PM, Jason Wang wrote:
On 2016年11月30日 18:10, Maxime Coquelin wrote:
This series implements Virtio spec update from Aaron Conole which
defines a way for the host to expose its max MTU to the guest.
This third version re-desings how MTU value is provided to QEMU.
Now,
On 2016年11月30日 18:10, Maxime Coquelin wrote:
This series implements Virtio spec update from Aaron Conole which
defines a way for the host to expose its max MTU to the guest.
This third version re-desings how MTU value is provided to QEMU.
Now, host_mtu parameter is added to provide QEMU with
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [Qemu-devel] [RFC v3 0/3] virtio-net: Add support to MTU feature
Type: series
Message-id: 20161130101017.13382-1
This series implements Virtio spec update from Aaron Conole which
defines a way for the host to expose its max MTU to the guest.
This third version re-desings how MTU value is provided to QEMU.
Now, host_mtu parameter is added to provide QEMU with the MTU value,
and the backend, if supported,