Description of problem: The operation of extend volume on Block storage fails on '_shouldExtendVolume', the error message on vdsm log: "periodic/1::ERROR::2015-08-19 15:08:50,036::vm::1011::virt.vm::(_shouldExtendVolume) vmId=`3debe87f-75a2-48f7-89ed-0d7d8d6ca6d2`::Improbable extension request for volume 8aca8f4c-1bb4-4019-ba19-892fee6a66c1 on domain 3104d6bf-5ce6-42c8-adb6-de27c1131daf, pausing the VM to avoid corruptions (capacity: 8589934592, allocated: 1075404288, physical: 0, next physical size: 1073741824) periodic/1::INFO::2015-08-19 15:08:50,037::vm::4910::virt.vm::(_logGuestCpuStatus) vmId=`3debe87f-75a2-48f7-89ed-0d7d8d6ca6d2`::CPU stopped: pause periodic/1::DEBUG::2015-08-19 15:08:50,037::__init__::206::jsonrpc.Notification::(emit) Sending event {"params": {"notify_time": 4378903740, "3debe87f-75a2-48f7-89ed-0d7d8d6ca6d2": {"status": "Paused"}}, "jsonrpc": "2.0", "method": "|virt|VM_status|3debe87f-75a2-48f7-89ed-0d7d8d6ca6d2"} pe" VM's status switches to Paused. Version-Release number of selected component (if applicable): rhevm-3.6.0-0.11.master.el6.noarch vdsm-4.17.2-1.el7ev.noarch How reproducible: 100% (tested with fcp and iSCSI) Steps to Reproduce: 1.create a new vm 2.create a new bootable qcow2 disk 3.attach disk to vm 4.install operating system Actual results: Vdsm fails to extend the disk Expected results: Vdsm should be able to extend qcows Additional info:
Created attachment 1064870 [details] logs
Seems like a duplicate of bug 1253756. Nir, can you please confirm (and close)?
Ori, please specify the version of the operating system you are testing, and libvirt-daemon version.
Libvrit always returns 0 for physical volume size, so this indeed looks like a duplicate of bug 1253756: $ grep extendDrivesIfNeeded vdsm.log | tail -n 1 periodic/5::INFO::2015-08-19 14:58:59,976::vm::1037::virt.vm::(extendDrivesIfNeeded) vmId=`3debe87f-75a2-48f7-89ed-0d7d8d6ca6d2`::Requesting extension for volume 8aca8f4c-1bb4-4019-ba19-892fee6a66c1 on domain 3104d6bf-5ce6-42c8-adb6-de27c1131daf (apparent: 1073741824, capacity: 8589934592, allocated: 684764672, physical: 0) Ori, please close this bug as duplicate if you are running rhel 7.2 with same libvirt version specified in the original bug.
Not the same version of libvirt or qemu. [root@adder ~]# rpm -qa | grep libvirt libvirt-daemon-driver-network-1.2.17-4.el7.x86_64 libvirt-daemon-config-nwfilter-1.2.17-4.el7.x86_64 libvirt-daemon-driver-secret-1.2.17-4.el7.x86_64 libvirt-daemon-driver-nwfilter-1.2.17-4.el7.x86_64 libvirt-daemon-driver-nodedev-1.2.17-4.el7.x86_64 libvirt-daemon-driver-storage-1.2.17-4.el7.x86_64 libvirt-daemon-1.2.17-4.el7.x86_64 libvirt-lock-sanlock-1.2.17-4.el7.x86_64 libvirt-daemon-kvm-1.2.17-4.el7.x86_64 libvirt-client-1.2.17-4.el7.x86_64 libvirt-daemon-driver-interface-1.2.17-4.el7.x86_64 libvirt-daemon-driver-qemu-1.2.17-4.el7.x86_64 libvirt-python-1.2.17-2.el7.x86_64 You have new mail in /var/spool/mail/root [root@adder ~]# rpm -qa | grep qemu qemu-kvm-common-rhev-2.3.0-18.el7.x86_64 qemu-img-rhev-2.3.0-18.el7.x86_64 ipxe-roms-qemu-20130517-7.gitc4bce43.el7.noarch qemu-kvm-tools-rhev-2.3.0-18.el7.x86_64 qemu-kvm-rhev-2.3.0-18.el7.x86_64 libvirt-daemon-driver-qemu-1.2.17-4.el7.x86_64
Based on comment 6, this is a duplicate. The original bug was reported on libvirt 1.2.17-2.el7, and the issue is fixed in libvirt-1.2.17-5.el7 (not released yet). If this issue blocks testing and you need a temporary fix, you can use https://gerrit.ovirt.org/44489 *** This bug has been marked as a duplicate of bug 1251008 ***