From Fedora Project Wiki
m (Crobinso moved page QA:Testcase Virtualization KVM PCI Device Assignment assign using virt manager to QA:Testcase Virtualization KVM PCI Device Assignment: Better name) |
(Re-write the page, add VFIO bits) |
||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description= | |||
|description= | |||
Assign a physical PCI device to a KVM guest, and verify that it works as expected. | |||
|setup= | |||
* Functioning F19+ host and F19+ VM. | |||
* PCI device you can afford to devote entirely to a VM | |||
|actions= | |actions= | ||
# Run virt-manager, open an existing guest and go to the details | |||
# | # Run virt-manager, open an existing shutoff guest and go to the details page. | ||
# Choose the | # Add Hardware->PCI Host Device | ||
# Click | # Choose the device you want to assign from the list, like: <code>00:19.0 Interface eth0 (82566DM-2 Gigabit Network Connection)</code> | ||
# Click ''Finish'' | |||
# Start the guest and check the device is functional within the guest | # Start the guest and check the device is functional within the guest | ||
# Shut down the guest and check the device is functional within the host | # Shut down the guest and check the device is functional within the host | ||
# Select the device in virt-manager and ''Remove'' it | |||
== Device assignment with VFIO == | |||
[http://www.linux-kvm.org/wiki/images/d/d1/2011-forum-VFIO.pdf VFIO] is the new and improved PCI assignment method for kvm. It will likely become the default through libvirt in the future. | |||
# Verify your host as necessary hardware support for VFIO | |||
#* If on an Intel CPU, this command should show at least 2 matches: <code>dmesg <nowiki>|</nowiki> grep -e DMAR -e IOMMU</code> | |||
#* If on an AMD CPU, this command should show some output: <code>dmesg <nowiki>|</nowiki> grep AMD-Vi</code> | |||
# On the host, do <code>sudo chmod 666 /dev/vfio/vfio</code> | |||
#* XXX: This is a bug, fixed in kernel 3.10, need to backport it to F19 | |||
# Follow the regular PCI assignment steps up to step 4. | |||
# Change the host device to use the VFIO method: | |||
#* <code>sudo virsh edit test-day-vm</code> | |||
#* Add <code><driver name="vfio"/></code> to the PCI <code><hostdev></code> block | |||
#* Save and exit | |||
# Continue on at step 4 in the above steps. | |||
|results= | |results= | ||
No obvious errors occur. PCI device assignment can be quirky and does not always work with every PCI device or host PCI layout. If you get an error, ask in #fedora-test-day IRC first and we can likely provide some direction. | |||
}} | }} | ||
[[Category:Virtualization | |||
[[Category:Virtualization Test Cases]] |
Revision as of 17:19, 24 May 2013
Description
Assign a physical PCI device to a KVM guest, and verify that it works as expected.
Setup
- Functioning F19+ host and F19+ VM.
- PCI device you can afford to devote entirely to a VM
How to test
- Run virt-manager, open an existing shutoff guest and go to the details page.
- Add Hardware->PCI Host Device
- Choose the device you want to assign from the list, like:
00:19.0 Interface eth0 (82566DM-2 Gigabit Network Connection)
- Click Finish
- Start the guest and check the device is functional within the guest
- Shut down the guest and check the device is functional within the host
- Select the device in virt-manager and Remove it
Device assignment with VFIO
VFIO is the new and improved PCI assignment method for kvm. It will likely become the default through libvirt in the future.
- Verify your host as necessary hardware support for VFIO
- If on an Intel CPU, this command should show at least 2 matches:
dmesg | grep -e DMAR -e IOMMU
- If on an AMD CPU, this command should show some output:
dmesg | grep AMD-Vi
- If on an Intel CPU, this command should show at least 2 matches:
- On the host, do
sudo chmod 666 /dev/vfio/vfio
- XXX: This is a bug, fixed in kernel 3.10, need to backport it to F19
- Follow the regular PCI assignment steps up to step 4.
- Change the host device to use the VFIO method:
sudo virsh edit test-day-vm
- Add
<driver name="vfio"/>
to the PCI<hostdev>
block - Save and exit
- Continue on at step 4 in the above steps.
Expected Results
No obvious errors occur. PCI device assignment can be quirky and does not always work with every PCI device or host PCI layout. If you get an error, ask in #fedora-test-day IRC first and we can likely provide some direction.