Test Day:2009-09-17 Virtualization VT-d

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(add test cases)
m (Changed category)
 
(One intermediate revision by one user not shown)
Line 21: Line 21:
  
 
The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion:
 
The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion:
 +
 +
* ''add your name here''
  
 
=== What's needed to test ===
 
=== What's needed to test ===
Line 72: Line 74:
 
|}
 
|}
  
[[Category:Test Days]]
+
[[Category:Fedora_12_Test_Days]]
 
[[Category:Virtualization]]
 
[[Category:Virtualization]]

Latest revision as of 14:22, 3 February 2010

DATE TIME WHERE
Thursday Sep 17, 2009 All day #fedora-test-day (webchat)


Contents

[edit] What to test?

This part of today's Fedora Test Day will focus on testing the KVM PCI Device Assignment feature added in Fedora 11.

Since several improvements have been made to the feature since Fedora 11 and it is very closely related to the SR-IOV feature in Fedora 12, it is worthwhile re-testing the feature.

If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test VT-d and provide feedback.

[edit] Who's available

Mark McLoughlin is your host for today.

The following people have also agreed to be available for testing, workarounds, bug fixes, and general discussion:

  • add your name here

[edit] What's needed to test

  • A fully updated Fedora 12 Rawhide machine. See instructions on the main test day page.
  • At least one guest image installed before the test day (suggested reading - Virtualization_Quick_Start)
  • A host machine which has Intel VT-d or AMD IOMMU support

[edit] Test Cases

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

  $> virsh nodedev-list --tree
  computer
    |
    ...
    +- pci_8086_10bd
    |   |
    |   +- net_00_13_20_f5_f9_5a
    ...
  $> virsh nodedev-dumpxml pci_8086_10bd
  <device>
    <name>pci_8086_10bd</name>
    <parent>computer</parent>
    <capability type='pci'>
      <domain>0</domain>
      <bus>0</bus>
      <slot>25</slot>
      <function>0</function>
      <product id='0x10bd'>82566DM-2 Gigabit Network Connection</product>
      <vendor id='0x8086'>Intel Corporation</vendor>
    </capability>
  </device>

Follow each of these test cases:

  1. libvirt nodedev operations
  2. assigning a device using libvirt
  3. assigning a device using virt-manager
  4. virt-install --host-device

[edit] Issues that were identified

Tester Description Bug references Status
#XXXXX ASSIGNED