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.
The virsh utility does not support system file-consistent snapshots for Windows XP and Windows 2003 virtual guest machines. As a consequence, running the snapshot-create-as --quiesce --disk-only command fails. To work around this problem, do not use the --quiesce option. Please note that the snapshots will not be consistent with the guest file system.
Description of problem: {"execute":"guest-fsfreeze-freeze"} was executed unsuccessfully on win2k3-64 guest. Version-Release number of selected component (if applicable): qemu-ga-7.0-8 virtio-win-1.7.0-1 qemu-kvm-1.5.3-60.el7.x86_64 kernel-3.10.0-118.el7.x86_64 How reproducible: 4/4 Steps to Reproduce: 1.boot up win2k3-64 guest /usr/libexec/qemu-kvm -M pc -m 2G -smp 2 -cpu Nehalem -usb -device usb-tablet -drive file=en_win_srv_2003_r2_enterprise_x64_with_sp2_cd1_X13-06188.iso,format=raw,if=none,media=cdrom,id=drive-ide0-0-1,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-1,id=ide0-0-1,bus=ide.0,unit=1,bootindex=1 -drive file=win2k3-64-new.raw,format=raw,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 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,id=net0 -uuid 4870b5fd-65d1-488a-9333-3c4e095285b0 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=a111,path=/tmp/monitor-win2012-serial,server,nowait -mon chardev=a111,mode=readline -vnc :3 -vga cirrus -monitor stdio -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 -cdrom /usr/share/virtio-win/virtio-win.iso 2.nc -U /tmp/qga.sock on host 3. {"execute":"guest-fsfreeze-freeze"} Actual results: The command could be executed successfully Expected results: Return error message {"execute":"guest-fsfreeze-freeze"} {"error": {"desc": "failed to set backup context: (error: 8004231b)"}} Additional info: