Bug 2107954
| Summary: | Unclear error message output when poweroff vm during postcopy migration. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Fangge Jin <fjin> | ||||
| Component: | libvirt | Assignee: | Jiri Denemark <jdenemar> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fangge Jin <fjin> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 8.7 | CC: | dzheng, jdenemar, lcheng, lmen, virt-maint | ||||
| Target Milestone: | rc | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | libvirt-8.0.0-10.module+el8.7.0+16047+746a126c | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-11-08 09:20:55 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: | |||||||
| Attachments: |
|
||||||
Could you please check if this is reproducible with upstream or RHEL-9.1.0 libvirt to confirm my suspicion this is in fact caused by backporting the zero-copy migration patches to a different code base. It can't be reproduce with libvirt-8.5.0-1.el9.x86_64 Thanks. And I just noticed this bug is filed for 9.1 despite talking about libvirt from 8.7.0. Versions: libvirt-8.0.0-10.module+el8.7.0+16047+746a126c.x86_64 qemu-kvm-6.2.0-18.module+el8.7.0+15999+d24f860e.x86_64 Test scenarios: * non-p2p, poweroff vm during postcopy(passed) ** error: operation failed: domain is not running * p2p, poweroff vm during postcopy(passed) ** error: operation failed: domain is not running * non-p2p, poweroff vm during precopy(failed) ** error: cannot get locked memory limit of process -1: No such file or directory ** Also tested with libvirt-8.0.0-9.module+el8.7.0+15830+85788ab7.x86_64, can reproduce. * p2p, poweroff vm during postcopy(passed) ** error: operation failed: domain is not running Also tested same scenarios with RHEL9 packages, all passed: libvirt-8.5.0-3.el9.x86_64 qemu-kvm-7.0.0-9.el9.x86_64 (In reply to Fangge Jin from comment #9) > * non-p2p, poweroff vm during precopy(failed) > ** error: cannot get locked memory limit of process -1: No such file or > directory > ** Also tested with libvirt-8.0.0-9.module+el8.7.0+15830+85788ab7.x86_64, > can reproduce. This is an issue even in upstream although it's masked by a patch which changed the PID of an inactive domain from 0 to -1. As a result of this change virProcessGetMaxMemLock does not fail when trying to get the limit for PID -1, but rather succeeds reading the limit for PID 0, i.e., libvirt. Which might actually be even worse as it may set the limit on libvirt daemon itself. Anyway, it's harmless on RHEL 8.7.0. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Low: virt:rhel and virt-devel:rhel security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:7472 |
Created attachment 1897866 [details] libvirtd log Description of problem: Do live migration, switch to postcopy, then poweroff inside vm. Migration failed, but the error message is not expected: # virsh migrate vm1 qemu+tcp://dell-per740-04.******/system --live --verbose --postcopy --p2p --bandwidth 3 --postcopy-bandwidth 10 Migration: [ 96 %]error: cannot get locked memory limit of process -1: No such file or directory Our automation script covers this scenario, but you can close it if you think it is not a bug or not worth fixing Version-Release number of selected component (if applicable): libvirt-client-8.0.0-9.module+el8.7.0+15830+85788ab7.x86_64 qemu-kvm-6.2.0-17.module+el8.7.0+15924+b11d8c3f.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start vm 2. Do live migration, and switch to postcopy 3. Check error message Actual results: error: cannot get locked memory limit of process -1: No such file or directory Expected results: error: operation failed: domain is not running Additional info: