Re: [dpdk-dev] [RFC] net/vdev_netvsc: check for required related drivers

2019-03-18 Thread Stephen Hemminger
On Sun, 17 Mar 2019 06:53:02 + Matan Azrad wrote: > Hi > > From: Stephen Hemminger > > wrote: > > > > > Hi > > > > > > From: Stephen Hemminger > > > > The vdev_netvsc virtual driver that is used to do initialization on > > > > Hyper- V/Azure won't work without failsafe and tap device. >

Re: [dpdk-dev] [RFC] net/vdev_netvsc: check for required related drivers

2019-03-16 Thread Matan Azrad
Hi From: Stephen Hemminger > wrote: > > > Hi > > > > From: Stephen Hemminger > > > The vdev_netvsc virtual driver that is used to do initialization on > > > Hyper- V/Azure won't work without failsafe and tap device. > > > If the related devices aren't present, it causes confusing errors > > > l

Re: [dpdk-dev] [RFC] net/vdev_netvsc: check for required related drivers

2019-03-14 Thread Stephen Hemminger
On Thu, 14 Mar 2019 11:26:05 + Matan Azrad wrote: > Hi > > From: Stephen Hemminger > > The vdev_netvsc virtual driver that is used to do initialization on Hyper- > > V/Azure won't work without failsafe and tap device. > > If the related devices aren't present, it causes confusing errors late

Re: [dpdk-dev] [RFC] net/vdev_netvsc: check for required related drivers

2019-03-14 Thread Matan Azrad
Hi From: Stephen Hemminger > The vdev_netvsc virtual driver that is used to do initialization on Hyper- > V/Azure won't work without failsafe and tap device. > If the related devices aren't present, it causes confusing errors later in > initialization when it crafts devargs and attempts to send th

[dpdk-dev] [RFC] net/vdev_netvsc: check for required related drivers

2019-03-13 Thread Stephen Hemminger
The vdev_netvsc virtual driver that is used to do initialization on Hyper-V/Azure won't work without failsafe and tap device. If the related devices aren't present, it causes confusing errors later in initialization when it crafts devargs and attempts to send them to a device driver that isn't ther