virt

virt@lists.centos.org

1608 discussions

Re: [CentOS-virt] Unable to use all the memory available
by James B. Byrne 22 Feb '12

22 Feb '12

On Tue, February 21, 2012 02:23, Henry Addington wrote: > Hello: > > As you can see from xm info below, we have almost 200GB of > memory in our > server running CentOS 5.2. But, we can't seem to allocate > all the memory. > For some reason, the total memory that can be allocated > maxes out at 188.4 > GB. None of the VMs has hit its own max-mem limit. Even > when we set one of > the VM's memory so the total is above 188.4 GB, its memory > allocation stops > when the total memory allocation reaches 188.4 GB. > > Thanks for your assistance. > What is the hardware limit for the server? -- *** 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

3 3

Unable to use all the memory available
by Henry Addington 21 Feb '12

21 Feb '12

Hello: As you can see from xm info below, we have almost 200GB of memory in our server running CentOS 5.2. But, we can't seem to allocate all the memory. For some reason, the total memory that can be allocated maxes out at 188.4 GB. None of the VMs has hit its own max-mem limit. Even when we set one of the VM's memory so the total is above 188.4 GB, its memory allocation stops when the total memory allocation reaches 188.4 GB. Thanks for your assistance. HS release : 2.6.18-274.7.1.el5xen version : #1 SMP Thu Oct 20 17:06:34 EDT 2011 machine : x86_64 nr_cpus : 32 nr_nodes : 1 sockets_per_node : 8 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2293 hw_caps : 178bfbff:efd3fbff:00000000:00000110:00802009:00000000:000007ff total_memory : 196607 free_memory : 0 node_to_cpu : node0:0-31 xen_major : 3 xen_minor : 1 xen_extra : .2-274.7.1.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-51) cc_compile_by : mockbuild cc_compile_domain : centos.org cc_compile_date : Thu Oct 20 16:13:16 EDT 2011 xend_config_format : 2

1 0

CentOS 6.2: Start and use guest as regular user under qemu-kvm?
by David McGuffey 11 Feb '12

11 Feb '12

Trying to set up a copy of CentOS 6.2 for home use and give each family member their own guest. Goal is to cripple the host so that no meaningful work can be done through it and each family member must use their own guest. "Gold Disk" masters would be kept of each guest, so if they screw it up, I can simply overwrite their current guest from the master. SELinux is enabled and sVirt separates each guest (I want to keep it that way). Default settings require a regular user to run the Virtual Machine Manager via sudo. Once they do that, they can see (and access) any other family member's guest. Would really like to avoid this. Have read several blurbs about getting qemu-kvm to run under a regular user, but not sure if the version provided with CentOS 6 is compiled with the options to allow that. When I follow the guidance to put users in the kvm group and change the ownership of key files, I fail. Appears to me that qemu-kvm with CentOS 6 is not set up (compliled) to run under a regular user. Say users are u1, u2, u3, and u4, and all are in the kvm group. What else do I need to do to allow them to start, suspend, and stop their own guest VM? Dave

2 1

virt-io drivers for 64 bit Win7 needed for USB passthrough?
by David McGuffey 11 Feb '12

11 Feb '12

Have been trying to get a 64-bit Win7 guest to access a usb thumbdrive (and eventually an Apple iTouch). Host is CentOS 6.2 and the guest is running under qemu-kvm with SELinux enabled and sVirt separating guests from each other and guests from the host. Do I need to install the virt-io drivers in the Win7 guest, or are there more permission and SELinux blocks in my path? Dave

1 0

Re: [CentOS-virt] Setting up serial ports on kvm guests
by James B. Byrne 08 Feb '12

08 Feb '12

On Wed, February 8, 2012 11:06, Ed Heron wrote: > On Tue, 2012-01-31 at 14:01 -0500, James B. Byrne wrote: >> CentOS-6.2 >> >> We have a dedicated CentOS-5.7 host used for fax >> reception >> and transmission that we wish to move to a CentOS-6.2 >> virtual guest instance. The CentOS-6.2 virtual host has >> a >> 4-port serial card installed. > > Consider replacing your multi-serial port card with a > VoIP analog > gateway and use a pre-rolled Asterisk with virtual > faxmodems, like > Elastix. Just make sure your codec is high enough > quality. We used to > receive faxes using a dedicated Linux box with a Comtrol > Rocketport and > an USRobotics MP8. We Converted to SIP trunks and managed > to get our > faxes in the SIP trunks, as well. > > This will remove the PCI pass-through from the equation. > After a brief read this seems to me the approach we should take. Recently I have discovered more about irqs, timing delays, and the difficulties/impossiblities of switching hardware from vm instances than I ever wanted to know. Given that we have three dedicated fax lines and 6 voice is there any hardware that would you suggest for a 4 core x86_64 Intel based host system? We have looked at going completely to v/f-oip but I do not have the time to deal with those intricacies and get this move completed at the same time. So, for the nonce it appears that we would have to employ an FXO gateway to connect our existing POTS lines to the host. -- *** 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

Setting up serial ports on kvm guests
by James B. Byrne 08 Feb '12

08 Feb '12

CentOS-6.2 We have a dedicated CentOS-5.7 host used for fax reception and transmission that we wish to move to a CentOS-6.2 virtual guest instance. The CentOS-6.2 virtual host has a 4-port serial card installed. lspci -v tshows this this: 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 setserial -g /dev/ttyS* shows this: /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 /dev/ttyS1, UART: 16950/954, Port: 0xd040, IRQ: 17 /dev/ttyS2, UART: 16950/954, Port: 0xd048, IRQ: 17 /dev/ttyS3, UART: 16950/954, Port: 0xd050, IRQ: 17 But, in virt-manage, when I try to add a serial device to the guest as the physical character device /dev/ttyS1 I get this error and the device is not added. XML error: unknown device type Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/addhardware.py", line 1026, in add_device self.vm.attach_device(self._dev) File "/usr/share/virt-manager/virtManager/domain.py", line 698, in attach_device self._backend.attachDevice(devxml) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 400, in attachDevice if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) libvirtError: XML error: unknown device type We wish to have at least two, preferably three, andf ideally all four, serial ports enabled on the virtual guest. Does anyone know how this is accomplished? -- *** 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

4 3

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 07 Feb '12

07 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt