From Fedora Project Wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 6: | Line 6: | ||
* [[rhbug:499259|499259]] - svirt denials breaks KVM PCI device assignment | * [[rhbug:499259|499259]] - svirt denials breaks KVM PCI device assignment | ||
: Until this is fixed, all but the nodedev ops test case requires you to run SELinux in permissive mode | : Until this is fixed, all but the nodedev ops test case requires you to run SELinux in permissive mode | ||
* [[rhbug:499352|499352]] - Re-enable CONFIG_DMAR_DEFAULT_ON | * [[rhbug:499352|499352]] - Re-enable CONFIG_DMAR_DEFAULT_ON | ||
: You will need to boot the host with intel_iommu=on until this is fixed | : You will need to boot the host with intel_iommu=on until this is fixed | ||
* [[rhbug:499267|499267]] - Assigning a PCI device using virt-manager/virt-install fails | * [[rhbug:499267|499267]] - Assigning a PCI device using virt-manager/virt-install fails | ||
: | : No workaround for this; this affects the virt-manager and virt-install test cases; fix in progress | ||
* [[rhbug:499386|499386]] - libvirt's qemu driver interprets the <hostdev> "managed" attribute incorrectly | * [[rhbug:499386|499386]] - libvirt's qemu driver interprets the <hostdev> "managed" attribute incorrectly | ||
: | : Fix in progress for this; affects libvirt/virt-install/virt-manager test cases | ||
== Prerequisites == | == Prerequisites == | ||
In order to test KVM PCI device assignment, you need | In order to test KVM PCI device assignment, you need a host machine which has Intel VT-d or AMD IOMMU support. | ||
Please [http://smolts.org/smolt-wiki/Main_Page#Usage upload your smolt profile] using <code>smoltSendProfile</code> and add its URL to the table below. | Please [http://smolts.org/smolt-wiki/Main_Page#Usage upload your smolt profile] using <code>smoltSendProfile</code> and add its URL to the table below. | ||
Line 36: | Line 24: | ||
== Tests == | == Tests == | ||
The first thing you need to do is choose which PCI device on your KVM host that you will use for testing. Probably the most obvious to test with is a NIC. You'll need the device's nodedev name, and you can find this with | The first thing you need to do is choose which PCI device on your KVM host that you will use for testing. Probably the most obvious to test with is a NIC. You'll need the device's nodedev name, and you can find this with e.g. | ||
<pre> | <pre> | ||
$> virsh nodedev-list -- | $> for iii in $(virsh nodedev-list --cap net); do virsh nodedev-dumpxml $iii | grep parent; done | ||
<parent>pci_8086_10bd</parent> | |||
<parent>computer</parent> | |||
$> virsh nodedev-dumpxml pci_8086_10bd | $> virsh nodedev-dumpxml pci_8086_10bd | ||
<device> | <device> | ||
Line 89: | Line 72: | ||
| [http://www.smolts.org/client/show/pub_0f98ce1f-983e-4825-b8d7-7f366f49fca4 smolt] | | [http://www.smolts.org/client/show/pub_0f98ce1f-983e-4825-b8d7-7f366f49fca4 smolt] | ||
| [http://fpaste.org/paste/11088 lspci] | | [http://fpaste.org/paste/11088 lspci] | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
|} | |} | ||