From: Jeremy Plsek <jplsek@iol.unh.edu>
To: "Yao, Lei A" <lei.a.yao@intel.com>
Cc: "Xu, Qian Q" <qian.q.xu@intel.com>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>,
"ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 7th
Date: Wed, 8 May 2019 16:07:10 -0400 [thread overview]
Message-ID: <CA+xUZB6SVQ3qqsF+OOOrzKjyJccXm2b08EjtWfWA439nF4XCXA@mail.gmail.com> (raw)
In-Reply-To: <2DBBFF226F7CF64BAFCA79B681719D95496C0578@shsmsx102.ccr.corp.intel.com>
Hmmm, I am unable to reproduce the issue now. Maybe that was the case.
I thought I made sure to stop the OVS processes and VMs before trying
to unbind VFIO. I'll let you know if I experience it again.
Thanks
On Tue, May 7, 2019 at 10:23 PM Yao, Lei A <lei.a.yao@intel.com> wrote:
>
> Hi, Jeremy
>
> Could you have a check if you kill all OVS related process before
> unbind NIC from vfio-pci driver?
> If OVS process is still active, this action will fail.
>
> BRs
> Lei
>
> > -----Original Message-----
> > From: Xu, Qian Q
> > Sent: Wednesday, May 8, 2019 10:08 AM
> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>; ci@dpdk.org; Yao, Lei A
> > <lei.a.yao@intel.com>
> > Cc: Xu, Qian Q <qian.q.xu@intel.com>
> > Subject: RE: DPDK Community Lab Meeting Minutes, Tuesday May 7th
> >
> > > - For Intel, after binding drivers to VFIO for OVS tests, can't bind back to
> > > I40E/IXGBE. Jeremy will send details in email.
> >
> > + Lei in the loop. Lei, any comments for it? Thx.
> >
> > > -----Original Message-----
> > > From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim
> > > Sent: Tuesday, May 7, 2019 9:27 PM
> > > To: ci@dpdk.org
> > > Subject: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May
> > 7th
> > >
> > > Jeremy is working on setting up the OVS tests on the Intel and Mellanox
> > > machines. Issues have been encountered with both setups.
> > > - For Intel, after binding drivers to VFIO for OVS tests, can't bind back to
> > > I40E/IXGBE. Jeremy will send details in email.
> > > - For Mellanox, having issues trying to set up using VFIO. Jeremy will follow
> > up
> > > with Ali and Thomas.
> > >
> > > Testing is currently paused while Ali updates the Mellanox firmware. This
> > will be
> > > done today and tests should restart after that.
> > >
> > > There's a security issue if patches contains malicious code. Tests run on all
> > > servers with root permissions. Possible solutions include: stop running tests
> > as
> > > root, run tests in containers, implement static analysis of patches prior to
> > > running. Ali will investigate and make a recommendation.
--
Jeremy Plsek
UNH InterOperability Laboratory
next prev parent reply other threads:[~2019-05-08 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 13:27 O'Driscoll, Tim
2019-05-08 2:08 ` Xu, Qian Q
2019-05-08 2:22 ` Yao, Lei A
2019-05-08 20:07 ` Jeremy Plsek [this message]
2019-05-09 8:37 ` Xu, Qian Q
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=CA+xUZB6SVQ3qqsF+OOOrzKjyJccXm2b08EjtWfWA439nF4XCXA@mail.gmail.com \
--to=jplsek@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=lei.a.yao@intel.com \
--cc=qian.q.xu@intel.com \
--cc=tim.odriscoll@intel.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).