> On Tue, Apr 14, 2015 at 9:37 AM, Rogers, Gerald <gerald.rog...@intel.com>
> wrote:
> > There are some deployments that are using or require older OS
> > distributions using qemu versions prior to version 2.1, thus would
> > require the support for vHost-cuse. Most general reason is
> > qualification cycles for new OS versions. The patch provides compile
> > time support for choosing which vHost version to use. The support for
> > vhost-cuse should be kept for at least several releases with
> > documentation indicating it will be eventually deprecated.
>
> I think it's a bit odd to mark something as deprecated before it even makes it
> to the first release. This is brand new functionality in OVS and so I'm not
> sure
> why existing deployments would have much of an impact. Based on the list
> of distributions that Kevin sent out, it seems like the most recent version of
> each of them supports a sufficiently new version of qemu. That seems
> reasonable enough to support to me given that there's still quite a bit of
> active development going on here.
From the list Kevin sent on the distributions that would be impacted are:
Fedora 20: 1.6.2
CentOS 7/ RHEL 7.0: 1.5.3
Debian wheezy: 1.1.2
As this is what is/isn't supported with the Qemu versions:
Qemu version vHost Cuse vHost User
< 2.0 Supported Not Supported
2.0 Not supported Not supported
> 2.0 Supported Supported
From an OPNFV project perspective there would be an impact on any projects
that which to use vhost as a guest access method with OVS + DPDK if vhost-cuse
was removed. The first release "Arno" is using CentOS 7 and QEMU 1.5.3.
so removing support for cuse would mean the projects would not be able to
use vhost as a guest access method. One such project is the
characterize_vswitch_performance_for_telco_nfv_use_cases which is initially
targeting OVS + DPDK and vhost-cuse as a guest access method.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
