virt February 2012

virt@lists.centos.org

19 participants
23 discussions

Setting up a pci passthrough device
by James B. Byrne 04 Feb '12

04 Feb '12

I have been investigating pci pass-through for virtualized guests and the documentation I have found seems to me to lack a certain consistency in its example. This may be due to my not understanding what it is trying to inform me. What I wish to do is to configure a pci multi-port serial i/o card for use by a single virtual host. I start by running lspci -v on the host to identify the serial card: 03:00.0 Serial controller: Oxford Semiconductor Ltd OX16PCI954 (Quad 16950 UART) function 0 (Uart) (prog-if 06 [16950]) Subsystem: Oxford Semiconductor Ltd Device 0000 Flags: medium devsel, IRQ 17 I/O ports at d040 [size=32] Memory at d0702000 (32-bit, non-prefetchable) [size=4K] I/O ports at d020 [size=32] Memory at d0701000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Kernel driver in use: serial I then check for possible multiple IRQ assignment: lspci -v | grep ' IRQ 17' Flags: medium devsel, IRQ 17 I next use lspci -n to identify the vendor codes: lspci -n | grep '00:03.0' 00:03.0 0780: 8086:2e24 (rev 03) So this is an Intel chipset and the device id is 2e24. Now this is the point in the example where the documentation and I part company. In the examples I have found, although the pci device ids listed from virsh nodedev-list are uniformly of the form pci_0000_00_03_0 those used in the examples then switch and use the form pci_8086_3a6c for the subsequent steps. This pattern appears to be the prefix pci followed by the manufacturer's code followed by the device id. There is no other mapping to the pci device ids previously reported by virsh nodedev-list and lspci in the examples that I can discern. However, if I attempt to use the manufacturer and device ids in the next step of the example, substituting those used in the example with those reported on my own system, then I get a device not found reported: virsh nodedev-dumpxml pci_8086_2e24 error: Could not find matching device 'pci_8086_2e24' error: Node device not found If instead I use the pci device ids exactly as reported by virsh nodedev-list then I get what I expect: virsh nodedev-dumpxml pci_0000_00_03_0 <device> <name>pci_0000_00_03_0</name> <parent>computer</parent> <capability type='pci'> <domain>0</domain> <bus>0</bus> <slot>3</slot> <function>0</function> <product id='0x2e24'>4 Series Chipset HECI Controller</product> <vendor id='0x8086'>Intel Corporation</vendor> <capability type='virt_functions'> </capability> </capability> </device> My question is: Why does the documentation change the form of the pci identifiers used in the second half of the example from those reported previously in the same example? Is this change significant? What does it mean? Am I missing something important here? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 3

CentOS6 virtio?
by Lars Hecking 01 Feb '12

01 Feb '12

Are there any updated instructions for installing Windows virtio drivers on a KVM Windows XP vm under CentOS6? The virtio .iso directory structure is slightly different from what is described in the RHEL6 virtualisation manual, and when I attempt to install e.g. the viostor driver, the device manager cannot find anything better than what is already installed. I tried each of the Wlh/Wnet/Wxp/XP directories.

3 3

Updated kvm kernael and now some guests are hung
by James B. Byrne 01 Feb '12

01 Feb '12

Earlier this evening I updated our CentOS-6.2 kvm virtual host to kernel 2.6.32-220.4.1.el6. After rebooting three guests are hung. I cannot establish connections via the network (no route to host) and the virtual console is unresponsive. On two of them I was able to initiate the login process but after the password prompt the system no longer responded. On the other the system hung when I tried to run the vi editor. The console display on each of the affected guests shows a long list of hung tasks: task jbd2/dm-0-0:384 blocked for more than 120 seconds . . . task jbd2/dm-3-8:838 blocked for more than 120 seconfs task master:1226 blocked for more than . . . task miniserv.pl:1248 blocked task pickup:29136 blocked The lists on each guest vary somewhat but share most of the same processes being blocked. One has a postmaster task that does not display on any of the others. I can recover from this but I want to get these guests restarted if I possibly can. Is there a way to do this? What would cause the problem? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt February 2012