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.

You have to use the --live (VIR_DUMP_LIVE) flag to not pause the guest while dumping it.

Hi Peter
The guest won't be paused again after specify the --live option, however, I doubt that if we have failed to dump the guest why still pause the guest if we didn't specify the --live option, this was  a little unreasonable, can't we check that if the dump path didn't exsit then report the error and skip the virsh dump directly. thanks

It would be possible to achieve that in the code. As the situation is happening in a place where the guest would be paused in the success case, pausing it also if the file can't be created doesn't make much difference. There are other cases where the dump would fail and the guest would need to be paused eg. when the dump file is stored on a device that is full.