virt January 2012

virt@lists.centos.org

37 participants
23 discussions

Has anyone been able to start a Fedora 16 VM in Xen PV?
by Scot P. Floess 08 Jul '12

08 Jul '12

All, I've had a heck of a time getting Fedora 16 to run as a guest VM under CentOS 5.7 host as a paravirtualized Xen guest. I believe the issue has something to do with Fedora 16 using grub2... When I attempt to start the VM (via xm create), I get this error: Using config file "/etc/xen/fedora-workstation". Traceback (most recent call last): File "/usr/bin/pygrub", line 686, in ? fs = fsimage.open(file, get_fs_offset(file)) IOError: [Errno 95] Operation not supported No handlers could be found for logger "xend" Error: Boot loader didn't return any data! In my kickstart, I had to create a partition for F16 as: part biosboot --fstype=biosboot --size=1 I didn't readily find the error when googling... Has anyone been able to run F16 as a PV guest? And if so, what did you do to make it happen????? Thanks!!!!!!!!!!!!! Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare

6 10

centos6 and xen4 dom0 memory allocation
by Peter Peltonen 08 Jul '12

08 Jul '12

Hi, This is slightly OT as xen is not officially supported in EL6. But maybe someone else is running it on centos6 as well and could help me out here: I have problems allocating a static amount of memory for my xen dom0. It seems to reduce when new domUs are created, even though I *think* ballooning is disabled. Can someone advise me what I'm doing wrong? I have xen-4.1.1-3 installed from http://xenbits.xen.org/people/mayoung/EL6.xen on my centos6 server. I am running 2.6.32-131.12.1.el6.xendom0.x86_64 kernel available from the same place. 'xl info' reports about available memory as follows: total_memory : 24567 free_memory : 3698 xen_commandline : dom0_mem=2048M and in xend-config.sxp I have: (dom0-min-mem 256) (enable-dom0-ballooning no) (total_available_memory 0) Now one would think that I should have 2048M memory for dom0, right? I started from there, but when starting domUs it has been reduced to 1140M even though I think ballooning is disabled and there is free memory available? And the weird thing is that dom0 has done some swapping: # free -mt total used free shared buffers cached Mem: 1140 1052 88 0 2 12 -/+ buffers/cache: 1038 102 Swap: 8194 85 8109 Total: 9335 1138 8197 Shutting down domUs and making more memory available does not reverse the effect, dom0 does not allocate more memory. What am I missing here or is my xen setup acting strangely here? Best regards, Peter

2 4

New Tutorial - RHCS + DRBD + KVM; 2-Node HA on EL6
by Digimer 19 Jun '12

19 Jun '12

Hi all, I'm happy to announce a new tutorial! https://alteeve.com/w/2-Node_Red_Hat_KVM_Cluster_Tutorial This tutorial walks a user through the entire process of building a 2-Node cluster for making KVM virtual machines highly available. It uses Red Hat Cluster services v3 and DRBD 8.3.12. It is written such that you can use entirely free or fully Red Hat supported environments. Highlights; * Full network and power redundancy; no single-points of failure. * All off-the-shelf hardware; Storage via DRBD. * Starts with base OS install, no clustering experience required. * All software components explained. * Includes all testing steps covered. * Configuration is used in production environments! This tutorial is totally free (no ads, no registration) and released under the Creative Common 3.0 Share-Alike Non-Commercial license. Feedback is always appreciated! -- Digimer E-Mail: digimer(a)alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "omg my singularity battery is dead again. stupid hawking radiation." - epitron

8 13

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

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

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

Cannot remove lvs associated with deleted vm guests
by James B. Byrne 27 Jan '12

27 Jan '12

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

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt January 2012