Re: [Xen-devel] Bug in hash changes to netback in 4.7.2 kernel

2016-09-06 Thread Anthony Wright
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 &g

Re: [Xen-devel] xen/xen vs xen/kvm nesting with pv drivers

2016-09-06 Thread Anthony Wright
On 06/09/2016 14:05, Andrew Cooper wrote: > On 06/09/16 13:47, Anthony Wright wrote: >> I tried to install Xen (4.7.0 with linux 4.7.2 Dom0) on an AWS virtual >> machine and it failed because while AWS uses Xen it requires that you use >> the PVHVM network driver. I then tr

[Xen-devel] xen/xen vs xen/kvm nesting with pv drivers

2016-09-06 Thread Anthony Wright
dered what are the challenges to getting the pv drivers working in a nested environment. Is this a problem with the Dom0 kernel only expecting there to be a single XenStore, or is there also a problem in Xen? Thanks, Anthony Wright ___ Xen-devel mailing

[Xen-devel] Bug in hash changes to netback in 4.7.2 kernel

2016-09-06 Thread Anthony Wright
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

Re: [Xen-devel] PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0

2014-12-09 Thread Anthony Wright
On 09/12/2014 22:30, Siegmann Joseph wrote: > > Would you mind sharing what it would take to correct this issue… is > there a file I could just replace until a patch is released? > We simply applied David Vrabel's patch from 8/12/14 to a stock 3.17.3 kernel we were running in the DomU and it fixed

Re: [Xen-devel] PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0

2014-12-09 Thread Anthony Wright
On 08/12/2014 12:03, David Vrabel wrote: > Does this patch to netfront fix it? > > 8<- > xen-netfront: use correct linear area after linearizing an skb > > Commit 97a6d1bb2b658ac85ed88205ccd1ab809899884d (xen-netfront: Fix > handling packets on compound p

Re: [Xen-devel] PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0

2014-12-04 Thread Anthony Wright
> On 01/12/14 14:22, David Vrabel wrote: > This VIF protocol is weird. The first slot contains a txreq with a > size > for the total length of the packet, subsequent slots have sizes for > that > fragment only. > > netback then has to calculate how long the first slot is, by > subtracting > all th

Re: [Xen-devel] PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0

2014-12-02 Thread Anthony Wright
- Original Message - > On 01/12/14 14:22, David Vrabel wrote: > > On 28/11/14 15:19, Anthony Wright wrote: > > The guest's frontend driver isn't putting valid requests onto the > > ring > > (it crosses a page boundary) so this is a frontend bug. >

Re: [Xen-devel] PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0

2014-12-01 Thread Anthony Wright
> On 28/11/14 15:19, Anthony Wright wrote: > > We have a 64 bit PV DomU that we recently upgraded from linux 3.3.2 > > to > > 3.17.3 running on a 64 bit 3.17.3 Dom0 with Xen 4.4.0. > > > > Shortly after the upgrade we started to lose network connectivity to > &

Re: [Xen-devel] PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0

2014-11-28 Thread Anthony Wright
On 28/11/2014 15:23, Ian Campbell wrote: > On Fri, 2014-11-28 at 15:19 +0000, Anthony Wright wrote: >> We have a 64 bit PV DomU that we recently upgraded from linux 3.3.2 to >> 3.17.3 > Is this a Debian kernel? In which case you might be seeing It's a stock kernel from kerne

[Xen-devel] PV DomU running linux 3.17.3 causing xen-netback fatal error in Dom0

2014-11-28 Thread Anthony Wright
We have a 64 bit PV DomU that we recently upgraded from linux 3.3.2 to 3.17.3 running on a 64 bit 3.17.3 Dom0 with Xen 4.4.0. Shortly after the upgrade we started to lose network connectivity to the DomU a few times a day that required a reboot to fix. We see nothing in the xen logs or xl dmesg, b