Red Hat Bugzilla – Bug 1003629
VM operating system stuck (Windows) during successful live disk resize with VirtIO disk
Last modified: 2016-02-10 12:48:52 EST
Created attachment 792857 [details] ## Logs rhevm, vdsm, libvirt, thread dump, superVdsm Description of problem: Failed live resize VM disk (VirtIO disk type) with Windows OS installed on it Version-Release number of selected component (if applicable): RHEVM 3.3 - IS12 environment: RHEVM: rhevm-3.3.0-0.18.master.el6ev.noarch PythonSDK: rhevm-sdk-python-3.3.0.12-1.el6ev.noarch VDSM: vdsm-4.12.0-92.gita04386d.el6ev.x86_64 LIBVIRT: libvirt-0.10.2-18.el6_4.9.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.355.el6_4.7.x86_64 SANLOCK: sanlock-2.8-1.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. On FCP Data Center create VM with VirtIO disk type and 20 GB disk size 2. Install Windows OS (Windows 7 or Windows 2008). Finish installation process. 3. During running VM resize VM’s disk size to 25GB Actual results: OS stuck Expected results: Successfully run live resize VM disk, without OS stuck. Impact on user: Can’t work with VM Workaround: Do cold resize VM disk. Power Off OS, resize VM disk, Power On VM. Additional info: * Live resize VM disk work ok with Linux OS * Failed live resize VM disk with Windows OS on RAW and QCOW2 disks /var/log/ovirt-engine/engine.log /var/log/vdsm/vdsm.log
*** Bug 1003632 has been marked as a duplicate of this bug. ***
Created attachment 807083 [details] online resize logs
(In reply to Sean Cohen from comment #8) Hi Sean, Since we are talking about a BSOD, we need more focus on the Windows side of this bug. Can you provide us a memory dump from C:\Windows\memory.dmp. If it is not there, please enable it from System Properties -> advanced, and in the meantime send the latest file from C:\Windows\minidump The file is big. Please Zip it, and put it somewhere where we can access it. And since we are not familiar with it, what exactly is "Try resize disk"? Can you describe the failure? Is it really a BSOD? What is the Error's code and text? Thanks, Ronen.
Vladimir, please provide Ronen with the memory dump
Logs attached
Created attachment 808461 [details] ## Logs rhevm, vdsm, libvirt, thread dump, superVdsm
Since currently we are not talking about a Windows size BSOD, reassigning. Ronen.
(In reply to Ronen Hod from comment #23) > Since currently we are not talking about a Windows size BSOD, reassigning. > > Ronen. The bug was opened as BSOD, reassigning this bug because QA encountered another regression during verification (bug 1015872) is only making confusion. The bug is already correctly depending on 1015872.
QE, Please check with both virtio-win build 72 and the bug fix from bug 1015872.
we will wait for fix of 1015872 then retry to verify, as it is ON_QA removing needinfo from Vlad.
Used latest Windows Virt-IO Drivers: http://download.devel.redhat.com/brewroot/packages/virtio-win-prewhql/0.1/72/win/virtio-win-prewhql-0.1.zip Tested on FCP Data Centers Verified, tested on RHEVM 3.3 - IS18 environment: Host OS: RHEL 6.5 RHEVM: rhevm-3.3.0-0.25.beta1.el6ev.noarch PythonSDK: rhevm-sdk-python-3.3.0.15-1.el6ev.noarch VDSM: vdsm-4.13.0-0.2.beta1.el6ev.x86_64 LIBVIRT: libvirt-0.10.2-27.el6.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.412.el6.x86_64 SANLOCK: sanlock-2.8-1.el6.x86_64
(In reply to vvyazmin@redhat.com from comment #27) > Used latest Windows Virt-IO Drivers: > http://download.devel.redhat.com/brewroot/packages/virtio-win-prewhql/0.1/72/ > win/virtio-win-prewhql-0.1.zip > > > Tested on FCP Data Centers > Verified, tested on RHEVM 3.3 - IS18 environment: > > Host OS: RHEL 6.5 > > RHEVM: rhevm-3.3.0-0.25.beta1.el6ev.noarch > PythonSDK: rhevm-sdk-python-3.3.0.15-1.el6ev.noarch > VDSM: vdsm-4.13.0-0.2.beta1.el6ev.x86_64 > LIBVIRT: libvirt-0.10.2-27.el6.x86_64 > QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.412.el6.x86_64 > SANLOCK: sanlock-2.8-1.el6.x86_64 Thanks, Vadim.
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.