virt

virt@lists.centos.org

2 participants
1612 discussions

Re: [CentOS-virt] Setting up a pci passthrough device
by James B. Byrne 08 Feb '12

08 Feb '12

On Mon, February 6, 2012 18:05, Ken Bass wrote: > Take a look at http://wiki.xensource.com/xenwiki/VTdHowTo > > Two things in particular about PCI passthrough: > > - Only devices with FLR capabilities are supported. > - Some motherboards are buggy. They advertised that they > support Vt-d > but do not correctly handle it (those with a broken ACPI > DMAR table) > > I think lspci -vv will tell you if the device supports > FLR. It will show > 'FLReset+' I believe. > 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 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 17 Region 0: I/O ports at d040 [size=32] Region 1: Memory at d0702000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at d020 [size=32] Region 3: Memory at d0701000 (32-bit, non-prefetchable) [size=4K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0+,D1-,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: serial No FLR string is present. So pci pass through is a dead end I take it? I increased the number of uarts available to the host system at boot with the 8250.nr_uarts=10 option. This gives me the following: # setserial -g /dev/ttyS* /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 /dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3 /dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4 /dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3 /dev/ttyS4, UART: 16950/954, Port: 0xd040, IRQ: 17 /dev/ttyS5, UART: 16950/954, Port: 0xd048, IRQ: 17 /dev/ttyS6, UART: 16950/954, Port: 0xd050, IRQ: 17 /dev/ttyS7, UART: 16950/954, Port: 0xd058, IRQ: 17 /dev/ttyS8, UART: unknown, Port: 0x0000, IRQ: 0 /dev/ttyS9, UART: unknown, Port: 0x0000, IRQ: 0 With this change I now can add one serial port (/dev/ttyS4) to a virtual guest using virt-manager and have the guest start, but no more than one. Any more that one and the guest fails to run with the same irq conflict error as before. I still have not tried to see if the serial port actually works in this case, just that the system starts. I ran across this thread relating to serial devices in qemu from some time ago: http://www.mail-archive.com/qemu-devel@nongnu.org/msg27354.html Which seems to me to imply that it is not possible for a qemu guest to have more than 2 serial ports, one of which I gather has to be the console. However, this statement attracted my attention: > This is wrong. Two devices should never be manipulating > the same qemu_irq object. If you want multiple devices > connected to the same IRQ then you need an explicit > multiplexer. e.g. arm_timer.c:sp804_set_irq. And in a later message in the same thread: > Two devices have the same s->irq. Give each on its own > qemu_irq, and feed it into a multiplexer that ORs them > together and sends the result to the interrupt > controller's qemu_irq: Is there a way to set irqs in quem to map to specific ports on a pci card as this seems to imply? How is it done? -- *** 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

Re: [CentOS-virt] Setting up a pci passthrough device
by James B. Byrne 06 Feb '12

06 Feb '12

On Sat, February 4, 2012 10:39, Nenad Opsenica wrote: > > > On 02/03/2012 05:32 PM, James B. Byrne wrote: >> Where does this go inside the rest of the guest >> configuration? > > virt-manager GUI places PCI device pass-through inside > <devices> ... http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualiz… I have followed the instructions in the RedHat reference above to the best of my ability to understand them. I add the pci multi-port serial io card through virt-manager and it was indeed entered into the virtual machine's configuration file inside the <devices> tag: <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </hostdev> However, when I try and start the virtual machine I get this error: Error starting domain: internal error Unable to reset PCI device 0000:00:03.0: no FLR, PM reset or bus reset available Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1050, in startup self._backend.create() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 511, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error Unable to reset PCI device 0000:00:03.0: no FLR, PM reset or bus reset available The steps I followed were: 1. Check VT-D extensions available and enabled in BIOS - yes 2. Restart virtual host - yes 3. Identify device - yes <address domain='0x000' bus='0x00' slot='0x03' function='0x0'/> 4. Add device to virtual machine configuration - yes . . . <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> 5. Enable SELinux boolean - yes getsebool virt_use_sysfs virt_use_sysfs --> on 6. Start virtual machine - fails Am I making any obvious errors? Has anyone here configured and managed to get a multi-port serial card working with a virtual guest? -- *** 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 1

CentOS6 virt-manager fails
by Lars Hecking 06 Feb '12

06 Feb '12

I've been playing around with virt-manager. Set up a single vm and enabled autostart, then rebooted the host to test it. It does work, but I can no longer use virt-manager. virt-viewer works, though. 22:17:04,529 (cli:71): virt-manager startup 2012-02-02 22:17:04,530 (virt-manager:292): Launched as: /usr/share/virt-manager/virt-manager.py --debug --no-dbus 2012-02-02 22:17:04,530 (virt-manager:293): GTK version: (2, 18, 9) 2012-02-02 22:17:04,530 (virt-manager:294): virtManager import: <module 'virtManager' from '/usr/share/virt-manager/virtManager/__init__.pyc'> 2012-02-02 22:17:04,662 (virt-manager:390): Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-5jSZbnyIwm: Connection refused) Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 383, in <module> main() File "/usr/share/virt-manager/virt-manager.py", line 315, in main config = virtManager.config.vmmConfig(appname, appversion, glade_dir) File "/usr/share/virt-manager/virtManager/config.py", line 96, in __init__ self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE) The /tmp dbus socket doesn't exist, but dbus-daemon is running. The only references to this problem I could find were old and unanswered posts to Fedora lists.

1 1

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

Problem with Centos 6.2 KVM
by Rajagopal Swaminathan 31 Jan '12

31 Jan '12

Greetings, Launching the virt-manager yeilds following error Error polling connection 'qemu:///system': internal error Cannot find suitable emulator for x86_64 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 440, in _tick conn.tick() File "/usr/share/virt-manager/virtManager/connection.py", line 1414, in tick newNets, self.nets) = self._update_nets() File "/usr/share/virt-manager/virtManager/connection.py", line 1277, in _update_nets lookup_func, build_class) File "/usr/share/virt-manager/virtManager/connection.py", line 1209, in _poll_helper if not check_support(): File "/usr/share/virt-manager/virtManager/connection.py", line 501, in is_network_capable virtinst.support.SUPPORT_CONN_NETWORK) File "/usr/lib/python2.6/site-packages/virtinst/support.py", line 574, in check_conn_support return _check_support(conn, feature, conn) File "/usr/lib/python2.6/site-packages/virtinst/support.py", line 443, in _check_support actual_drv_ver = _hv_ver(conn, uri) File "/usr/lib/python2.6/site-packages/virtinst/support.py", line 376, in _hv_ver ret = cmd(*args) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2823, in getVersion if ret == -1: raise libvirtError ('virConnectGetVersion() failed', conn=self) libvirtError: internal error Cannot find suitable emulator for x86_64 yum list gives Installed Packages libvirt.x86_64 0.9.4-23.el6_2.4 @updates libvirt-client.x86_64 0.9.4-23.el6_2.4 @updates libvirt-python.x86_64 0.9.4-23.el6_2.4 @updates Available Packages libvirt-client.i686 0.9.4-23.el6_2.4 updates any clues? TIA -- Regards, Rajagopal

5 6

Re: [CentOS-virt] Cannot remove lvs associated with deleted vm guests
by James B. Byrne 30 Jan '12

30 Jan '12

This problem was finally resolved with the generous help of Bryn M. Reeves on the inux-lvm(a)redhat.com list. The difficulty was that the utility kpartx had the lvs opened via their mappings. Further, the mappings were created with the -pp option of kpartx and that option had to be provided to the delete action in order for that to work: # kpartx -d -pp /path/to/logical/volume/name Once the mappings were removed then the lvremove also worked and the volumes were removed. A small point, failure to provide the -pp option to the kpartx -d action does not raise an error. Nor does it remove the mapping however. -- *** 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

Re: [CentOS-virt] Cannot remove lvs associated with deleted vm guests
by James B. Byrne 30 Jan '12

30 Jan '12

On Sat, January 28, 2012 12:19, Phil Schaffner wrote: > Pardon the top-post and cross-post, but this apparently > should have gone > to centos-virt(a)centos.org > > Phil > > chris procter wrote on 01/27/2012 03:29 PM: >> Hi, >> >> Its ages since I came across this problem so my memory >> is a little hazey but something is obviously holding on >> to the lv so you'll need to figure out whats holding it >> and kill that. The open value returned by "dmsetup info" >> is how many things have the device file open), it looks >> to be 2 at the moment and you cant "dmsetup remove" >> untill its zero (lvm might be one of them I cant >> remember) >> >> >> A few things worth trying are >> >> >> 1) make sure its not mounted anywhere! [root@vhost01 ~]# umount /dev/vg_vhost01/lv_vm_base umount: /dev/vg_vhost01/lv_vm_base: not mounted >> 2) if multipathd is running try stopping that. [root@vhost01 ~]# ps -ef | grep multipathd root 465 307 0 09:40 pts/0 00:00:00 grep multipathd [root@vhost01 ~]# service multipathd status multipathd: unrecognized service [root@vhost01 ~]# find / -name multipathd [root@vhost01 ~]# >> 3) either lsof or fuser on the device file may be able [root@vhost01 ~]# fuser /dev/vg_vhost01/lv_vm_base [root@vhost01 ~]# lsof /dev/vg_vhost01/lv_vm_base [root@vhost01 ~]# >> 4) something vm related might not have let go properly, >> are there any deamons/processes etc still running? There are many vm qeum processes running, non contain any reference to lv_vm_base [root@vhost01 ~]# ps -ef | grep vm_base root 549 307 0 09:44 pts/0 00:00:00 grep vm_base [root@vhost01 ~]# >> 5) reboot, the sledgehammer aproach to killing off >> processes!! >> >> 6) you could try hitting it with dmsetup again, you need >> to suspend the device first using "dmsetup suspend" >> which *may* persuade the holding process to let go, if >> it does reduce the open count you'll need to "dmsetup >> resume" and then suspend again untill open reaches zero >> when "dmsetup remove" should work. I'd try and avoid >> this option if you can, you're messing beneath the lvm >> layer and it may not like that, should be ok but... [root@vhost01 ~]# dmsetup info -c vg_vhost01-lv_vm_base Name Maj Min Stat Open Targ Event UUID vg_vhost01-lv_vm_base 253 5 L--w 2 1 0 LVM-gXMt00E1RDjpSX3INLZ35Prtg66aX36BeAOlKIkmfSNQRNol3Hni920R4YVaZr52 [root@vhost01 ~]# dmsetup suspend vg_vhost01-lv_vm_base [root@vhost01 ~]# dmsetup info -c vg_vhost01-lv_vm_base Name Maj Min Stat Open Targ Event UUID vg_vhost01-lv_vm_base 253 5 L-sw 2 1 0 LVM-gXMt00E1RDjpSX3INLZ35Prtg66aX36BeAOlKIkmfSNQRNol3Hni920R4YVaZr52 >> if none of that is possible/works you could try asking >> on the lvm-linux list. Am so doing. >> >> >> Reinstalling really shouldn't be necesary. >> Yes. However. . . -- *** 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

Re: [CentOS-virt] [CentOS] Cannot remove lvs associated with deleted vm guests
by Phil Schaffner 28 Jan '12

28 Jan '12

Pardon the top-post and cross-post, but this apparently should have gone to centos-virt(a)centos.org Phil chris procter wrote on 01/27/2012 03:29 PM: > Hi, > > Its ages since I came across this problem so my memory is a little hazey but something is obviously holding on to the lv so you'll need to figure out whats holding it and kill that. The open value returned by "dmsetup info" is how many things have the device file open), it looks to be 2 at the moment and you cant "dmsetup remove" untill its zero (lvm might be one of them I cant remember) > > > A few things worth trying are > > > 1) make sure its not mounted anywhere! > 2) if multipathd is running try stopping that. > > 3) either lsof or fuser on the device file may be able to tell you which process has it open > 4) something vm related might not have let go properly, are there any deamons/processes etc still running? > > 5) reboot, the sledgehammer aproach to killing off processes!! > > 6) you could try hitting it with dmsetup again, you need to suspend the device first using "dmsetup suspend" which *may* persuade the holding process to let go, if it does reduce the open count you'll need to "dmsetup resume" and then suspend again untill open reaches zero when "dmsetup remove" should work. I'd try and avoid this option if you can, you're messing beneath the lvm layer and it may not like that, should be ok but... > > > if none of that is possible/works you could try asking on the lvm-linux list. > > > Reinstalling really shouldn't be necesary. > > > chris > > > > > > ----- Original Message ----- >> From: James B. Byrne<byrnejb(a)harte-lyne.ca> >> To: centos-virt(a)centos.org; centos(a)centos.org >> Cc: >> Sent: Friday, 27 January 2012, 17:50 >> Subject: [CentOS] Cannot remove lvs associated with deleted vm guests >> >> At the beginning of January I encountered a problem where >> several vm guests on a single host somehow managed to see >> the the virtual disks assigned to other guests on the same >> hosts. I was unable to resolve this situation and >> shutdown the affected guests after creating new guest >> instances and moving the services and data off the >> corrupted guests. >> >> I have since removed these guests via virt-manager but all >> attempts to remove from the host the logical volumes >> associated with the former VirtIO disks fail. The volumes >> are considered open by lvremove and nothing I have tried >> can get them to close for removal. The --force option has >> no effect on this situation. >> >> # /sbin/lvremove -f /dev/vg_vhost01/lv_vm_base >> Can't remove open logical volume "lv_vm_base" >> >> # dmsetup info -c vg_vhost01-lv_vm_base >> Name Maj Min Stat Open Targ Event UUID >> vg_vhost01-lv_vm_base 253 5 L--w 2 1 0 >> LVM-gXMt00E1RDjpSX3INLZ35Prtg66aX36BeAOlKIkmfSNQRNol3Hni920R4YVaZr52 >> >> # dmsetup remove vg_vhost01-lv_vm_base >> device-mapper: remove ioctl failed: Device or resource busy >> Command failed >> >> >> There are several bugs filed on similar issues and udev is >> sometimes identified as the culprit. If I kill the udev >> daemon with T=`pidof -x udevd`; kill $T and rerun the >> lvremove -f command then I see this change in behaviour: >> >> # /sbin/lvremove -f /dev/vg_vhost01/lv_vm_base >> Found duplicate PV djM23m6YebBQ2xgPh9ORMtdX2iOu9xBQ: >> using /dev/mapper/vg_vhost01-lv_vm_pas.harte--lyne.cap2 >> not >> /dev/mapper/vg_vhost01-lv_vm_pgsql--dbms.harte--lyne.ca_00p2 >> Found duplicate PV djM23m6YebBQ2xgPh9ORMtdX2iOu9xBQ: >> using /dev/mapper/vg_vhost01-lv_vm_basep2 not >> /dev/mapper/vg_vhost01-lv_vm_pas.harte--lyne.cap2 >> Can't remove open logical volume "lv_vm_base" >> >> I need to get this system stable and return the lost disk >> space to the storage pool. Does anyone have any >> suggestions as to how to proceed? >> >> If I cannot solve this using the available system commands >> then prudence dictates that I have to re-install the >> server OS and rebuild all of the vm guests. As these >> guests have been laboriously transferred from other hosts >> during the past month this is a task I would rather not >> have to do. >> >> Any help is gratefully accepted. >> >> -- >> *** 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 >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> http://lists.centos.org/mailman/listinfo/centos >> > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt