From: Rich Persaud <persaur@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Juergen Gross" <JGross@suse.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: PV guest with PCI passthrough crash on Xen 4.8.3 inside KVM when booted through OVMF
Date: Fri, 16 Feb 2018 16:35:14 -0500 [thread overview]
Message-ID: <552B21FA-E41B-48B5-8FF4-E40B1DAE90AD@gmail.com> (raw)
In-Reply-To: <b8bb621f-1558-d207-4978-4dca46e350e6@citrix.com>
On Feb 16, 2018, at 14:02, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>
> IMO, PCI Passthrough is a trainwreck, and it is a miracle it functions
> at all.
Would that statement apply to other hypervisors like KVM, VMware ESX or Hyper-V, i.e. are the deficiencies in PCI devices/firmware, IOMMUs, platform firmware?
If the statement is Xen specific, are there specific issues or known sections of Xen code that would benefit from a rewrite or redesign inspired by other hypervisors?
Rich
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-16 21:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 17:48 PV guest with PCI passthrough crash on Xen 4.8.3 inside KVM when booted through OVMF Marek Marczykowski-Górecki
2018-02-16 17:52 ` Andrew Cooper
2018-02-16 18:51 ` Marek Marczykowski-Górecki
2018-02-16 19:02 ` Andrew Cooper
2018-02-16 19:54 ` Marek Marczykowski-Górecki
2018-02-19 17:23 ` Juergen Gross
2018-02-19 17:29 ` Marek Marczykowski-Górecki
2018-02-19 17:46 ` Juergen Gross
2018-02-19 17:49 ` Andrew Cooper
2018-02-16 21:35 ` Rich Persaud [this message]
2018-02-19 17:13 ` Roger Pau Monné
2018-02-19 17:30 ` Juergen Gross
2023-11-26 14:51 ` [Xen-devel] " Marek Marczykowski-Górecki
[not found] ` <CACHz=ZiWufUenyw_wg+QuK86+gU5RZNkuJNzX9-K1UM5P3m8+Q@mail.gmail.com>
2023-11-27 11:26 ` Marek Marczykowski-Górecki
2023-11-27 15:56 ` Jason Andryuk
2023-11-27 16:05 ` Juergen Gross
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=552B21FA-E41B-48B5-8FF4-E40B1DAE90AD@gmail.com \
--to=persaur@gmail.com \
--cc=JGross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.