Has there been any update to this bug/issue last discussed on Tue 6 Sep 2016
14:37:21 +0100? Under Debian stretch running Xen & kernel version 4.8.0-1-amd64
I have a Windows HVM that cannot communicate with other PVM domU instances on
the same dom0. The PVM domU instances report: "net eth0: Inva
> -Original Message-
> From: Anthony Wright [mailto:anth...@overnetdata.com]
> Sent: 06 September 2016 14:37
> To: Paul Durrant ; Xen-devel de...@lists.xen.org>
> Subject: Re: Bug in hash changes to netback in 4.7.2 kernel
>
> On 06/09/2016 13:57, Paul Durrant wrote:
> >> -Original Me
On 06/09/2016 13:57, Paul Durrant wrote:
>> -Original Message-
>> From: Anthony Wright [mailto:anth...@overnetdata.com]
>> Sent: 06 September 2016 13:23
>> To: Xen-devel
>> Cc: Paul Durrant
>> Subject: Bug in hash changes to netback in 4.7.2 kernel
>>
>> When I run Xen (4.7.0) nested in V
> -Original Message-
> From: Anthony Wright [mailto:anth...@overnetdata.com]
> Sent: 06 September 2016 13:23
> To: Xen-devel
> Cc: Paul Durrant
> Subject: Bug in hash changes to netback in 4.7.2 kernel
>
> When I run Xen (4.7.0) nested in VirtualBox (5.0.24_Ubuntu r108355) with a
> linux
When I run Xen (4.7.0) nested in VirtualBox (5.0.24_Ubuntu r108355) with a
linux-4.7.2 Dom0 kernel, none of my DomU's (linux-3.17.3) have network
connectivity because they reject all packets with the error 'Invalid extra
type: 4'. When I run exactly the same setup on bare metal, I don't get the
