Bug 2236353

Summary: qemu crashed when migrate guest with blob resources enabled
Product: Red Hat Enterprise Linux 9 Reporter: Lili Zhu <lizhu>
Component: qemu-kvmAssignee: Marc-Andre Lureau <marcandre.lureau>
qemu-kvm sub component: Graphics QA Contact: Guo, Zhiyi <zhguo>
Status: CLOSED MIGRATED Docs Contact:
Severity: unspecified    
Priority: unspecified CC: coli, fjin, jinzhao, juzhang, kraxel, lmen, virt-maint, xuzhang, zhetang
Version: 9.4Keywords: MigratedToJIRA
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 18:15:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lili Zhu 2023-08-31 03:21:48 UTC
Description of problem:
qemu crashed when migrate guest with blob resources enabled


Version-Release number of selected component (if applicable):
libvirt-9.5.0-6.el9.x86_64
qemu-kvm-8.0.0-13.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. prepare a guest with the following xml snippet
# virsh dumpxml lizhu --xpath //video
<video>
  <model type="virtio" heads="1" primary="yes" blob="on"/>
  <alias name="video0"/>
  <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/>
</video>

2. migrate the guest to another host
# virsh migrate lizhu qemu+ssh://$target_host/system --verbose --live
Migration: [98.32 %]error: operation failed: domain is not running

3. check the qemu log on target host
#cat /var/log/libvirt/qemu/lizhu.log
...
2023-08-30 14:35:30.653+0000: Domain id=1 is tainted: host-cpu
char device redirected to /dev/pts/2 (label charserial0)
2023-08-30T14:35:37.352236Z qemu-kvm: Failed to load virtio-gpu:virtio-gpu
2023-08-30T14:35:37.352266Z qemu-kvm: error while loading state for
instance 0x0 of device '0000:00:01.0/virtio-gpu'
2023-08-30T14:35:37.352442Z qemu-kvm: load of migration failed: Invalid argument
2023-08-30 14:35:37.754+0000: shutting down, reason=crashed

4. check the qemu log on source host
#cat /var/log/libvirt/qemu/lizhu.log
...
2023-08-30 14:35:30.974+0000: initiating migration
2023-08-30 14:35:37.789+0000: shutting down, reason=crashed

5. check the guest states on source host
# virsh domstate lizhu --reason
shut off (unknown)

Actual results:
Migration failed, qemu crashed

Expected results:
Qemu should not crash.

Comment 1 Guo, Zhiyi 2023-09-06 11:22:59 UTC
I think live migration should be blocked if blob is enabled

Comment 2 Marc-Andre Lureau 2023-09-06 13:09:28 UTC
I sent a patch to the ML: "[PATCH] virtio-gpu: block migration of VMs with blob=true"

we will need future work to allow migration.

Comment 3 RHEL Program Management 2023-09-22 18:10:39 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-22 18:15:41 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.