Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This issue is addressed by Microsoft KB975688: http://support.microsoft.com/kb/975688/
This happens because "VSS in Windows Server 2008 R2 and in Windows 7 does not return the VSS_E_HOLD_WRITES_TIMEOUT error when a snapshot provider takes more than 10 seconds to create a snapshot."
The fix is included in Windows 7 Service Pack 1.
Created attachment 884440 [details] screenshot of eventvwr Description of problem: Version-Release number of selected component (if applicable): qemu-ga-7.0-8 virtio-win-1.7.0-1 How reproducible: 100% Steps to Reproduce: 1.Start win7-64 /usr/libexec/qemu-kvm -M pc -m 6G -smp 4 -cpu host -usb -device usb-tablet -drive file=win7-64.qcow2,format=qcow2,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device e1000,netdev=hostnet0,mac=00:52:36:18:34:22,id=net0 -uuid 534daeff-e3af-451c-bbb7-b4ab8fb84079 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=a,path=/tmp/monitor-win2k8R2-serial,server,nowait -mon chardev=a,mode=readline -name win2k8-R2-serial -vnc :2 -vga cirrus -device virtio-serial-pci,id=serial0 -chardev socket,id=chardev0,path=/tmp/tt,server,nowait -device virtserialport,id=port0,name=com.redhat.rhevm.vdsm,chardev=chardev0 -monitor stdio -cdrom /usr/share/virtio-win/virtio-win-1.7.0.iso -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 2.on the host {"execute":"guest-fsfreeze-freeze"} 3.check eventvwr.msc in the guest Actual results: It prompts "VSS waited more than 40 seconds for all volumes to be flushed" Expected results: should be 10 secs Additional info: