Message ID | 1446722065-32066-1-git-send-email-ciara.loftus@intel.com |
---|---|
State | Accepted |
Headers | show |
I applied this to master, thanks. We should remember to remove this when we move to DPDK 2.2 On 05/11/2015 03:14, "Ciara Loftus" <ciara.loftus@intel.com> wrote: >Currently when using QEMU v2.4.0+, two (or more) dpdkvhostuser ports >cannot >be unbound from the kernel driver in the guest without causing the >ovs-vswitchd process to crash. Document this limitation and potential >workarounds. > >Signed-off-by: Ciara Loftus <ciara.loftus@intel.com> >--- > INSTALL.DPDK.md | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > >diff --git a/INSTALL.DPDK.md b/INSTALL.DPDK.md >index 02588c4..96b686c 100644 >--- a/INSTALL.DPDK.md >+++ b/INSTALL.DPDK.md >@@ -891,6 +891,18 @@ Restrictions: > core count of the system to be less than or equal to 64 when using >an XL710 > interface with DPDK. > >+ vHost and QEMU v2.4.0+: >+ - For versions of QEMU v2.4.0 and later, it is currently not possible >to >+ unbind more than one dpdkvhostuser port from the guest kernel driver >+ without causing the ovs-vswitchd process to crash. If this is a >requirement >+ for your use case, it is recommended either to use a version of QEMU >+ between v2.2.0 and v2.3.1 (inclusive), or alternatively, to apply the >+ following patch to DPDK and rebuild: >+ >https://urldefense.proofpoint.com/v2/url?u=http-3A__dpdk.org_dev_patchwork >_patch_7736_&d=BQIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=SmB5 >nZacmXNq0gKCC1s_Cw5yUNjxgD4v5kJqZ2uWLlE&m=079UWIQfNZfFOiT1740c-D8BfVd8i013 >V-oxENZbxPY&s=1v4hVQpJqDFudC3HJ8roD6mOq2TTA9nMGnw5DJUEy9A&e= >+ This problem will likely be resolved in Open vSwitch at a later >date, when >+ the next release of DPDK (which includes the above patch) is >available and >+ integrated into OVS. >+ > Bug Reporting: > -------------- > >-- >1.9.3 > >_______________________________________________ >dev mailing list >dev@openvswitch.org >https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailma >n_listinfo_dev&d=BQIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=Sm >B5nZacmXNq0gKCC1s_Cw5yUNjxgD4v5kJqZ2uWLlE&m=079UWIQfNZfFOiT1740c-D8BfVd8i0 >13V-oxENZbxPY&s=hTQQo02twYmEekRcK86bhOCodaQ7cqLj4mSFbsrSkR4&e=
diff --git a/INSTALL.DPDK.md b/INSTALL.DPDK.md index 02588c4..96b686c 100644 --- a/INSTALL.DPDK.md +++ b/INSTALL.DPDK.md @@ -891,6 +891,18 @@ Restrictions: core count of the system to be less than or equal to 64 when using an XL710 interface with DPDK. + vHost and QEMU v2.4.0+: + - For versions of QEMU v2.4.0 and later, it is currently not possible to + unbind more than one dpdkvhostuser port from the guest kernel driver + without causing the ovs-vswitchd process to crash. If this is a requirement + for your use case, it is recommended either to use a version of QEMU + between v2.2.0 and v2.3.1 (inclusive), or alternatively, to apply the + following patch to DPDK and rebuild: + http://dpdk.org/dev/patchwork/patch/7736/ + This problem will likely be resolved in Open vSwitch at a later date, when + the next release of DPDK (which includes the above patch) is available and + integrated into OVS. + Bug Reporting: --------------
Currently when using QEMU v2.4.0+, two (or more) dpdkvhostuser ports cannot be unbound from the kernel driver in the guest without causing the ovs-vswitchd process to crash. Document this limitation and potential workarounds. Signed-off-by: Ciara Loftus <ciara.loftus@intel.com> --- INSTALL.DPDK.md | 12 ++++++++++++ 1 file changed, 12 insertions(+)