search for: vg_vhost01

...-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 # dmse...

...-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 # dmse...

...thing. I have discovered that this is probably, indeed almost certainly, related to udev but the few work arounds I have found all seem to fail for me. Does anyone here know how to remove these things? When I try this: # for i in {1..200}; do udevadm control --stop-exec-queue ; lvremove -f /dev/vg_vhost01/lv_vm_inet05.harte-lyne.ca_01; udevadm control --start-exec-queue; done I get hundreds of these: Logical volume vg_vhost01/lv_vm_inet05.harte-lyne.ca_01 is used by another device. # lsof /dev/vg_vhost01/lv_vm_inet05.harte-lyne.ca_01 # I recall that I ran into this before and I have a sinking fe...

...ot> <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='...

...aught me that I need to partition it before attempting to add the new storage to the physical volume set of the intended guest. Up to now I have simply accepted the defaults given by fdisk after telling it that I want a new partition. The defaults always exclude the first 2048 sectors. Disk /dev/vg_vhost01/lv_vm_inet09.harte-lyne.ca_01: 33.6 GB, 33554432000 bytes 109 heads, 61 sectors/track, 9856 cylinders, total 65536000 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x2b33a3c9...

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

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