Bug 1306239 - VFIO: missing documentation for VFIO enabling procedure on PPC platforms.
VFIO: missing documentation for VFIO enabling procedure on PPC platforms.
Status: CLOSED CURRENTRELEASE
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt (Show other bugs)
3.6.3
ppc Unspecified
unspecified Severity medium (vote)
: ovirt-3.6.4
: ---
Assigned To: Martin Polednik
Nisim Simsolo
:
Depends On:
Blocks: RHEV3.6PPC
  Show dependency treegraph
 
Reported: 2016-02-10 06:45 EST by Nisim Simsolo
Modified: 2016-02-21 05:58 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Release Note
Doc Text:
The special procedure to enble vfio passthrough through boot command line is not required on POWER. please make sure doc is aligned
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-02-10 08:00:12 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
michal.skrivanek: ovirt‑3.6.z?
rule-engine: planning_ack?
michal.skrivanek: devel_ack+
rule-engine: testing_ack?


Attachments (Terms of Use)

  None (edit)
Description Nisim Simsolo 2016-02-10 06:45:11 EST
Description of problem:

Currently, there is no specific procedure that describes how to enable PCI passthrough on PPC platforms.
Browsing feature page http://www.ovirt.org/Features/hostdev_passthrough does not show any reference for PPC platforms.
Preconditions that needs to be clarified before enabling PCI passthrough:
1. Should it be enabled in BIOS level or not? if so, what should be enabled (in intel for example, vt-d must be enabled).
2. Should IOMMU be enabled at grub or not? if so, what is the line should be entered? (in intel for example, intel_iommu=on must be set).
3. In case of GPU passthrough, should it be unbinded from host kernel driver and binded to pci-stub driver?
Comment 1 Martin Polednik 2016-02-10 08:00:12 EST
Wiki has been updated to reflect the steps requires (= no steps required) to set the feature up.

Note You need to log in before you can comment on or make changes to this bug.