From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
Cc: "<dev@openvswitch.org>" <dev@openvswitch.org>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Crashing OVS+DPDK at the host, from inside of a KVM Guest
Date: Wed, 25 May 2016 08:05:31 +0200 [thread overview]
Message-ID: <CAATJJ0LTkZopXt86u=76UgiaOd-Aw3s-Ty4XnncT=F6Er7=6OQ@mail.gmail.com> (raw)
In-Reply-To: <CAJSM8J063W1nKCkUnPtOMQiT0K82wfxC-H6nXXewz6cBZYaRKA@mail.gmail.com>
Hi,
ping ...
Later on I want to look at it again once we upgraded to more recent
releases of the software components involved, but those have to be made
ready to use first :-/
But the description is good and I wonder if anybody else could reproduce
this and/or would have a hint on where this might come from or already
existing related fixes.
I mean in general nothing should be able to crash the host right?
P.S. yeah two list cross posting, but it is yet unclear which it belongs to
so I'll keep it
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
On Sun, May 15, 2016 at 7:08 AM, Martinx - ジェームズ <thiagocmartinsc@gmail.com>
wrote:
> Guys,
>
> If using OVS 2.5 with DPDK 2.2, on Ubuntu Xenial, it is possible to crash
> the OVS running at the host, from inside of a KVM Guest.
>
> Basically, what I'm trying to do, is to run OVS+DPDK at the host, and
> also, inside of a KVM Guest, with multi-queue, but it doesn't work and
> crashes.
>
> Soon as you enable multi-queue at the guest, it crashes the OVS of the
> host!
>
> OVS+DPDK segfault at the host, after running "ovs-vsctl set Open_vSwitch .
> other_config:n-dpdk-rxqs=4" within a KVM Guest:
>
> https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1577088
>
> Thanks!
> Thiago
>
next prev parent reply other threads:[~2016-05-25 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 5:08 Martinx - ジェームズ
2016-05-25 6:05 ` Christian Ehrhardt [this message]
2016-05-25 13:53 ` Traynor, Kevin
2016-05-27 3:47 ` Yuanhan Liu
2016-05-25 15:32 ` Xie, Huawei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAATJJ0LTkZopXt86u=76UgiaOd-Aw3s-Ty4XnncT=F6Er7=6OQ@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=dev@openvswitch.org \
--cc=thiagocmartinsc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).