January 2012 - virt - lists.centos.org

How to debug Ubuntu 8.04 LTS guest crash during install?
by Neil Aggarwal 04 Nov '25

04 Nov '25

Hello: I am using kvm on a CentOS 5.4 server. I am trying to install the TunkeyLinux Core appliance found here: http://www.turnkeylinux.org/core I downloaded the ISO file from the web site. Then, I used this command to intall it: virt-install -n tkl-core -r 512 --vcpus=1 --check-cpu --os-type=linux --os-variant=ubuntuhardy -v --accelerate -c /tmp/turnkey-core-2009.10-hardy-x86.iso -f /var/lib/libvirt/images/tkl-core.img -s 15 -b br0 --vnc noautoconsole When I connect to the VNC console, I get the Turnkey linux options screen. I select Install to hard disk from there and it seems to start the install but crashes during the installer startup. This is repeatable so there has to be a way to debug it. I tried turning on the debug option for virt-install but that did not give me any useful info. Any ideas how to debug this? Thanks, Neil -- Neil Aggarwal, (281)846-8957, http://UnmeteredVPS.net/cpanel cPanel/WHM preinstalled on a virtual server for only $40/month! No overage charges, 7 day free trial, PayPal, Google Checkout

3 4

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

Re: [CentOS-virt] [CentOS] VirtIO disk 'leakage' across guests?
by James B. Byrne 20 Jan '12

20 Jan '12

On Mon, January 16, 2012 17:01, Dennis Jacobfeuerborn wrote: > On 01/16/2012 10:16 PM, James B. Byrne wrote: > > ... >> The xmldump for this guest instance contains this: > ... > > Please post the xmldumps of the original guest and cloned > guest right after > cloning and without any modifications. > > Regards, > Dennis Prototype dumpxml virsh # dumpxml vm-centos-6 <domain type='kvm' id='34'> <name>vm-centos-6</name> <uuid>77692b36-d424-175f-b991-abc58fa0359b</uuid> <description>vm clone prototype root user password: protoype</description> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='rhel6.0.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source dev='/dev/vg_vhost01/lv_vm_base'/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' unit='0'/> </disk> <controller type='ide' index='0'> <alias name='ide0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:28:7e:ce'/> <source bridge='br0'/> <target dev='vnet5'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/6'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/6'> <source path='/dev/pts/6'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5905' autoport='yes'/> <sound model='ac97'> <alias name='sound0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='cirrus' vram='9216' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='selinux' relabel='yes'> <label>system_u:system_r:svirt_t:s0:c299,c322</label> <imagelabel>system_u:object_r:svirt_image_t:s0:c299,c322</imagelabel> </seclabel> </domain> virsh # A substantially identical clone of the prototype. This guest has had no additional storage added to it. virsh # dumpxml sshpipe.harte-lyne.ca <domain type='kvm' id='19'> <name>sshpipe.harte-lyne.ca</name> <uuid>5fbd2bad-059c-da0d-c856-c16cfb831a9a</uuid> <description>vm clone prototype root user password: protoype</description> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='rhel6.0.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source dev='/dev/vg_vhost01/lv_vm_sshipe.harte-lyne.ca_00'/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' unit='0'/> </disk> <controller type='ide' index='0'> <alias name='ide0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='52:54:00:ee:d8:32'/> <source bridge='br0'/> <target dev='vnet2'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/3'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/3'> <source path='/dev/pts/3'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5902' autoport='yes'/> <sound model='ac97'> <alias name='sound0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='cirrus' vram='9216' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='selinux' relabel='yes'> <label>system_u:system_r:svirt_t:s0:c876,c1002</label> <imagelabel>system_u:object_r:svirt_image_t:s0:c876,c1002</imagelabel> </seclabel> </domain> virsh # The second guest, sshpipe, shows this for pvdisplay: [root@sshpipe ~]# pvdisplay Couldn't find device with uuid umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De. --- Physical volume --- PV Name /dev/vda2 VG Name vg_vm_centos_6 PV Size 7.32 GiB / not usable 3.00 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 1874 Free PE 0 Allocated PE 1874 PV UUID djM23m-6Yeb-BQ2x-gPh9-ORMt-dX2i-Ou9xBQ --- Physical volume --- PV Name unknown device VG Name vg_vm_centos_6 PV Size 31.25 GiB / not usable 3.97 MiB Allocatable yes PE Size 4.00 MiB Total PE 7999 Free PE 1855 Allocated PE 6144 PV UUID umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De and this for vgdisplay [root@sshpipe ~]# vgdisplay Couldn't find device with uuid umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De. --- Volume group --- VG Name vg_vm_centos_6 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 7 VG Access read/write VG Status resizable MAX LV 0 Cur LV 3 Open LV 2 Max PV 0 Cur PV 2 Act PV 1 VG Size 38.57 GiB PE Size 4.00 MiB Total PE 9873 Alloc PE / Size 8018 / 31.32 GiB Free PE / Size 1855 / 7.25 GiB VG UUID qa6jwq-5gTp-6mMH-IWl9-OrEK-HjWc-pbaFsa But, sshpipe should only have a single 8Gb VirtIO disk assigned. -- *** 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 -- *** 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 2

Re: [CentOS-virt] (no subject)
by Wendy William 18 Jan '12

18 Jan '12

http://luk-art.com/friend.links.php?usexjgo=26&ywywesok=36

1 0

Re: [CentOS-virt] VirtIO disk 'leakage' across guests?
by James B. Byrne 16 Jan '12

16 Jan '12

If I log on to the newly cloned guest and I try and rename the vg used by that instance I see this: [root@vm-centos-6 ~]# vgrename vg_vm_centos_6 vg_vm_renamed Couldn't find device with uuid umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De. Cannot change VG vg_vm_centos_6 while PVs are missing. Consider vgreduce --removemissing. [root@vm-centos-6 ~]# vgreduce vg_vm_centos_6 --removemissing Couldn't find device with uuid umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De. WARNING: Partial LV lv_pgsql needs to be repaired or removed. WARNING: Partial LV lv_backups needs to be repaired or removed. WARNING: There are still partial LVs in VG vg_vm_centos_6. To remove them unconditionally use: vgreduce --removemissing --force. Proceeding to remove empty missing PVs. The xmldump for this guest instance contains this: <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source dev='/dev/vg_vhost01/lv_vm_test-vg-rename'/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' unit='0'/> </disk> <controller type='ide' index='0'> <alias name='ide0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> The /dev entries for this vm guest are these: [root@vm-centos-6 ~]# ll /dev/vg_vm_centos_6/* lrwxrwxrwx. 1 root root 7 Jan 16 15:36 /dev/vg_vm_centos_6/lv_root -> ../dm-0 lrwxrwxrwx. 1 root root 7 Jan 16 15:36 /dev/vg_vm_centos_6/lv_swap -> ../dm-1 Searching for the missing uuid I find these files: # find /etc -print | xargs grep 'umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De' /etc/lvm/archive/vg_vm_centos_6_00005-1429183950.vg: id = "umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De" /etc/lvm/archive/vg_vm_centos_6_00002-807578735.vg: id = "umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De" /etc/lvm/archive/vg_vm_centos_6_00004-1687335328.vg: id = "umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De" /etc/lvm/archive/vg_vm_centos_6_00003-650133889.vg: id = "umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De" /etc/lvm/archive/vg_vm_centos_6_00006-1907108135.vg: id = "umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De" /etc/lvm/backup/vg_vm_centos_6: id = "umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De" Looking in the files of /etc/lvm/archive created by the vgrename command shows a complete mess of lvs from different vm guests non of which have anything in common with the test vm guest, other than they all share the same volume group name. Evidently, cloning vm instances for the purpose of setting up a new vm guest to run with other vms cloned from the same prototype is not a good idea, -- *** 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 -- *** 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

VirtIO disk 'leakage' across guests?
by James B. Byrne 16 Jan '12

16 Jan '12

We are in the process of migrating several stand-alone server hosts onto a CentOS-6 kvm virtual host. We also use Webmin to administer our hosts. All of the guests, without exception, have been cloned brom a prototype guest using virt-manager. All of the additional VirtIO disks assigned to some of the guests have been added through virt-manager as well. Recently I have encountered a situation with the development copy of Webmin where I can see an additional VirtIO disk assigned to one guest instance, but not yet added to the lvg of that guest, as an unknown device on different guest. Further, I can see an lv assigned to one guest instance as an lv on a difference guest. The webmin author is aware of this problem and is assiduously trying to determine its cause. My difficulty is answering the question: How is it even possible for an application running under a httpd service on one guest to see anything at all besides the VirtIO storage assigned to that guest? Has anyone else encountered this anomaly? -- *** 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

Re: [CentOS-virt] VirtIO disk 'leakage' across guests?
by James B. Byrne 16 Jan '12

16 Jan '12

On Mon, January 16, 2012 13:05, James B. Byrne wrote: > How is it even possible for an > application running under a httpd service on one guest to > see anything at all besides the VirtIO storage assigned to > that guest? > > Has anyone else encountered this anomaly? > I just cloned a guest instance. The clone prototype was set up with a single VirtIO disk of 8Gbs, divided into a 500 Mb boot and a ~7.1Gb root partition. The root partition was entirely assigned to the basic vg and two lv were created, one for swap and one for the actual root partition. When the guest was cloned there was only one VirtIO disk of 8 Gb assigned to it and this was cloned and given a new name. When I look at the newly cloned guest instance with pvdisplay this is what I see: # pvdisplay Couldn't find device with uuid umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De. --- Physical volume --- PV Name /dev/vda2 VG Name vg_vm_centos_6 PV Size 7.32 GiB / not usable 3.00 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 1874 Free PE 0 Allocated PE 1874 PV UUID djM23m-6Yeb-BQ2x-gPh9-ORMt-dX2i-Ou9xBQ --- Physical volume --- PV Name unknown device VG Name vg_vm_centos_6 PV Size 31.25 GiB / not usable 3.97 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 7999 Free PE 0 Allocated PE 7999 PV UUID umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De When I look at it using vgdisplay then this is what I see: # vgdisplay Couldn't find device with uuid umrIn6-Np0c-NC4Z-MuUo-5TBj-IKRE-XBU0De. --- Volume group --- VG Name vg_vm_centos_6 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 10 VG Access read/write VG Status resizable MAX LV 0 Cur LV 4 Open LV 2 Max PV 0 Cur PV 2 Act PV 1 VG Size 38.57 GiB PE Size 4.00 MiB Total PE 9873 Alloc PE / Size 9873 / 38.57 GiB Free PE / Size 0 / 0 VG UUID qa6jwq-5gTp-6mMH-IWl9-OrEK-HjWc-pbaFsa What is going on and how do I fix this? The size of the ghost pv (31Gb) is showing up as the size of the clone's vg whereas the pv for the cloned instance is only 8Gb. I am only using virt-manager to manage disk storage for these guests and I have no idea why or how this mismash is happening. Any ideas? -- *** 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 1

Centos 6.2 / KVM troubles with network
by Radek Bursztynowski 14 Jan '12

14 Jan '12

Hi, I have installed CentOS 6.2 x86_64 and KVM/Qemu and I have some troubles with network. The first case: ----------------- The configuration is: - CentOS 6.2 (hardware machine) has one Ethernet interface with static IP address (eth0). - Virtual machine has bridge network interface with eth0 interface on CentOS 6.2. This bridge is created using wizard integrated with virt-manager. - Bridge interface on virtual machine receives IP addres from DHCP server. IP address is received well. - All firewalls and SELinux are closed. Virtual machine has no any connection with CentOS 6.2 hardware machine, and CentOS 6.2 has no any connection with virtual machine. But every others machines have all connection with both virtual and CentOS 6.2 machine. The question: Why? The second case: ---------------------- The configuration is: - On CentOS 6.2 (hardware machine) I created bridhe (br0) with eth0 hardware interface. Two situations: + I force two different IP addresses for eth0 and br0 interfaces - there no any connection with this server. So I don't test this case. + I forced one IP addres for both eth0 and br0 interfaces. ifconfig shows that eth0 has no IP address, br0 has IP address. So, I test this case. - I use Red Hat documentation: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html-single/Vi…) - On virtual machine I created bridge connection with br0 interface on CentOS 6.2. - All machines have all connections. - All firewalls and SELinux are closed. NFS server on CentOS 6.2 (hardware machine) doesn't serve exported file system. The questions: 1. Is it proper that eth0 has no IP addres and bridge (br0) interface has? 2. What about my NFS? NFS server worked well before starting virtualization. Who can me help with my troubles? Regards, Radek

3 4

No module named cygvirtmod
by Lars Hecking 12 Jan '12

12 Jan '12

I'm trying to set up a xen guest on a machine that already has a few others running (not set up by me). It fails with the following error: + virt-install -r 512 -n host5 -f /dev/vol0/lvol5 --nographics -p --os-type=linux --os-variant=rhel5 --accelerate -l http://bla -x ks=http://bla/ks.cfg -m MA:CA:DD:RE:SS Traceback (most recent call last): File "/usr/bin/virt-install", line 31, in ? import libvirt File "/usr/lib64/python2.4/site-packages/libvirt.py", line 12, in ? import cygvirtmod as libvirtmod ImportError: No module named cygvirtmod This is a standard CentOS 5.4 x86_64 install, and I have not been able to find a solution on the web.

3 5

centos 6 domU doesn't see all memory?
by Chris Wik 11 Jan '12

11 Jan '12

I'm running CentOS 6 x86_64 domU on CentOS 5 x86_64 dom0 The host is running 2.6.18-238.19.1.el5xen The guest is 2.6.32-220.2.1.el6.x86_64 'xm list' on the host shows 512mb memory allocated. 'free -m' in the guest shows 224mb memory. 'xm mem-set 21 1024' (21 being the domU ID), 'xm list' now shows 1024mb, but in the guest I now see 736mb. Anyone else seeing this? Any ideas on how to fix it? Chris -- Chris Wik Anu Internet Services Ltd www.cwik.ch | www.anu.net

1 0

KVM VM crash under I/O load (e1000 and virtio)
by Ben Clay 09 Jan '12

09 Jan '12

I'm pretty consistently getting crashed KVM VMs under network I/O load when using the e1000 and virtio NIC models, with the follow message in dmesg: qemu-kvm[8785]: segfault at d0 ip 00000031e3200a08 sp 0000000047784080 error 4 in libnvidia-tls.so.285.05.23[31e3200000+3000] qemu-kvm[8791]: segfault at d0 ip 00000031e3200a08 sp 0000000049f89080 error 4 in libnvidia-tls.so.285.05.23[31e3200000+3000] qemu-kvm[8792]: segfault at d0 ip 00000031e3200a08 sp 000000004a78a080 error 4 in libnvidia-tls.so.285.05.23[31e3200000+3000] [<ffffffff8113b41b>] ? newseg+0xf0/0x213 [<ffffffff8113b32b>] ? newseg+0x0/0x213 These VMs are not performing any tasks with their display that I am aware of, and are not assigned GPUs. I'm aware that this isn't the latest nvidia driver, but I guess I don't understand why it's causing the problem in the first place. The same thing also happens when using the virtio block driver under heavy load. Unfortunately this is forcing me to fall back to the default NIC drivers, which are very slow (~120Mbit/s VM<->VM vs ~460Mbit/s with virtio). We're using vanilla kernel 2.6.32, with the following KVM-related packages: kmod-kvm-83-239.el5.centos kvm-qemu-img-83-239.el5.centos kvm-83-239.el5.centos libvirt-0.8.2-22.el5 Here is an example config (you can see where I commented out the model lines, because the VMs won't stay up): <domain type='kvm'> <name>myvm</name> <memory>8388608</memory> <currentMemory>8388608</currentMemory> <vcpu cpuset="0-7">8</vcpu> <os> <type arch='x86_64' machine='rhel5.4.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' cache='none' type='raw'/> <source file='/vm/path/disk.raw'/>  <target dev='vda'/> </disk> <interface type='bridge'> <mac address='mac1'/> <source bridge='br0'/>  </interface> <interface type='bridge'> <mac address='mac2'/> <source bridge='br9'/>  </interface> <serial type='pty'> <source path='/dev/pts/2'/> <target port='0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target port='0'/> </console>  </devices> </domain> Any help would be appreciated! -Ben

1 0

qemu-kvm
by Radek Bursztynowski 06 Jan '12

06 Jan '12

Hi everybody, I am new member at this list but I am not new with CentOS. I use CentOS 5.x till today, but I try CentOS 6.2 now. Regarding virtualization on CentOS 6.2 (i386) I have some problem. I installed all rpm packages joined to CentOS 6.2 and virtualization. When I try to start virt-manager I receive request to install qemu-kvm package. I try to do it accepting virt-manager advice but i can read message that this package is not available. So, I try to install qemu-kvm using yum - still nothing. Next I added additional packages and repositories as follow: epel-release-6-5.noarch.rpm remi-release-6.rpm centos-release-cr-6-0.el6.centos.i686.rpm rpmfusion-free-release-6-0.1.noarch.rpm rpmfusion-nonfree-release-6-0.1.noarch.rpm Still nothing. I visited http://rpmfind.net/linux/rpm2html/search.php?query=qemu-kvm but there are qemu-kvm packages destined for CentOS x86_64. Could anybody advice me where qemu-kvm packages for CentOS 6.2 i386 is placed or what should I to do to fix my problem? Thanks for any help, Radek

4 7

server host keys for kvm clones
by James B. Byrne 05 Jan '12

05 Jan '12

Respecting cloning vm guests, I see in /etc/ssh the following: ssh_host_dsa_key ssh_host_dsa_key.pub ssh_host_key ssh_host_key.pub ssh_host_rsa_key ssh_host_rsa_key.pub Is there a simple script somewhere to regenerate all the server host keys for the new guest after cloning? -- *** 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

7 14

turning off udev for eth0
by James B. Byrne 04 Jan '12

04 Jan '12

I have set up a kvm host and configured a standard clone prototype for generating new guests. One persistent (pun intended) annoyance when cloning is the behaviour of udev with respect to the virtual network interface. The prototype is configured with just eth0 having a dedicated IP addr. When the prototype is cloned udev creates rules for both eth0 and eth1 in the clone. Because eth1 does not exist in the cloned guest one has to manually edit /etc/udev/rules.d/70-persistent-net.rules to get rid of the bogus entries and then restart the clone instance to have the changes take effect. All this does is return the new guest to the prototype eth0 configuration. Is there no way to alter udev's behaviour? Is udev even needed on a server system using virtual hardware? Altering the rules file not a big deal in itself but it adds needless busywork when setting up a new 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

3 2

iscsi target rescan means connections hang for five seconds
by Dennis Jacobfeuerborn 03 Jan '12

03 Jan '12

Hi, I'm starting to experiment with iscsi based volumes and while this works fine so far I ran into a problem. When I add a LUN to a target and refresh tgtd all i/o to that target seems to hang for five seconds. This is obviously less than ideal if the plan is to use the target for lots of guests. There is also the possibility to create one target with one LUN for each guest disk but that sounds like a management nightmare and the libvirt pool functions become useless. Is there a way to make this less intrusive? How do you guys cope with this issue? Regards, Dennis

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt January 2012