Description of problem: Failed to backup windows vm Version-Release number of selected component (if applicable): 4.11 How reproducible: 100% Steps to Reproduce: 1. Create windows vm with guest agent 2. Wait to guest agent to be active: status: conditions: status: "True" type: AgentConnected 3. Create backup Actual results: backup partially failed Expected results: backup complete Additional info: oc logs -n openshift-adp velero... time="2022-07-31T14:54:17Z" level=info msg="stderr: {\"component\":\"freezer\",\"level\":\"info\",\"msg\":\"Starting...\",\"pos\":\"main.go:46\",\"timestamp\":\"2022-07-31T14:54:12.836933Z\"}\n{\"component\":\"freezer\",\"level\":\"error\",\"msg\":\"Freezeing VMI failed\",\"pos\":\"main.go:81\",\"reason\":\"server error. command Freeze failed: \\\"LibvirtError(Code=86, Domain=10, Message='Guest agent is not responding: Guest agent not available for now')\\\"\",\"timestamp\":\"2022-07-31T14:54:17.887495Z\"}\n" backup=openshift-adp/backup-ns hookCommand="[/usr/bin/virt-freezer --freeze --name vm-8696-1659275420-9791226 --namespace velero-test-ns]" hookContainer=compute hookName="<from-annotation>" hookOnError=Fail hookPhase=pre hookSource=annotation hookTimeout="{30s}" hookType=exec logSource="pkg/podexec/pod_command_executor.go:174" name=virt-launcher-vm-8696-1659275420-9791226-8hqqx namespace=velero-test-ns resource=pods time="2022-07-31T14:54:17Z" level=error msg="Error executing hook" backup=openshift-adp/backup-ns error="command terminated with exit code 1" hookPhase=pre hookSource=annotation hookType=exec logSource="internal/hook/item_hook_handler.go:214" name=virt-launcher-vm-8696-1659275420-9791226-8hqqx namespace=velero-test-ns resource=pods
I remember having issue with fsfreeze in windows VMs. I reached out to the qemu-dev team asking about it at the time, I was told I My "version of GuestAgent is too old". I was having version 100.0.0 the I was told "has a bug related to wrong error messages". Can you check for this issue what is the version of the guest-agent used when recreating this bug? and if its older then 103.0.0 can you check about upgrading it and see if it recreates for that too? @dafrank
Dalia, any updates?
@dafrank Is the bug reproducible using an updated windows on cnv 4.10 using the qemu guest agent version of the iso cnv ships in 4.10, and can the bug be prevented by installing a newer qemu guest agent version in the guest?
Tested with Windows 2022 with guest agent version 105.0.2, and the backup and restore works fine, closing the bug.