From: Stephen Hemminger <stephen@networkplumber.org>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [Bug 204] Crash on Vmware esxi host when dpdk guest reboots.
Date: Mon, 4 Feb 2019 18:41:47 +1300 [thread overview]
Message-ID: <CAOaVG17DfXFywK+1Mmeamd=p+0DazNWcEbwko0zOj62+swmksg@mail.gmail.com> (raw)
In-Reply-To: <bug-204-3@http.bugs.dpdk.org/>
Anything that crashes a host is a host bug. The host can never trust the
guest to be well behaved. These are serious often with security
implications. Hopefully VMware will or has already addressed it.
On Sat, Feb 2, 2019, 6:18 AM <bugzilla@dpdk.org wrote:
> https://bugs.dpdk.org/show_bug.cgi?id=204
>
> Bug ID: 204
> Summary: Crash on Vmware esxi host when dpdk guest reboots.
> Product: DPDK
> Version: 18.11
> Hardware: x86
> OS: Other
> Status: CONFIRMED
> Severity: major
> Priority: Normal
> Component: core
> Assignee: dev@dpdk.org
> Reporter: girish_potti@affirmednetworks.com
> Target Milestone: ---
>
> Running Vmware esxi 6.5 with i40en driver 1.7.11 . Guest running debian8.0
> with
> either dpdk 18.05.1 or dpdk18.11 (lts) .
>
> When the guest is rebooted occasionally we see the crash on esxi host and
> the
> guest is shut down.
>
> vmware-9.log:2018-09-24T00:57:09.434Z| vmx| I120+ PCI passthru device
> 0000:03:0e.0 caused an IOMMU fault type 4 at address 0x7881ba04e3000.
> Powering
> off the virtual machine. If the problem persists please contact the
> device's
> vendor.```
>
> The Device 0000:03:0e.0 is a fortville 25g nic. The guests have vfs as
> adapters
> running dpdk.
>
> If we dont have dpdk running on guest(just the linux vfs driver) this
> issue
> doesnt happen on host.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
prev parent reply other threads:[~2019-02-04 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 17:18 bugzilla
2019-02-04 5:41 ` Stephen Hemminger [this message]
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='CAOaVG17DfXFywK+1Mmeamd=p+0DazNWcEbwko0zOj62+swmksg@mail.gmail.com' \
--to=stephen@networkplumber.org \
--cc=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).