Bug 1965589
| Summary: | Taint message generated during vm running is not preserved during libvirtd restart | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Fangge Jin <fjin> | |
| Component: | libvirt | Assignee: | khanicov | |
| Status: | CLOSED ERRATA | QA Contact: | Fangge Jin <fjin> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 8.5 | CC: | jdenemar, khanicov, lmen, mprivozn, virt-maint, xuzhang, yalzhang | |
| Target Milestone: | rc | Keywords: | Triaged, Upstream | |
| Target Release: | 8.6 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | libvirt-7.8.0-1.module+el8.6.0+12978+7d7a0321 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2001322 (view as bug list) | Environment: | ||
| Last Closed: | 2022-05-10 13:18:42 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: | 7.7.0 | |
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2001322 | |||
Patch proposed on the list: https://listman.redhat.com/archives/libvir-list/2021-July/msg00584.html Forgot to mention that hotplug cdrom/interface actually failed in comment 0 Merged upstream as: 878cbd0f6a qemu: save status xml after generating taint message v7.6.0-101-g878cbd0f6a Move to RHEL since RHEL-AV will only be a rebuild of RHEL starting w/ 8.6.0 Verify with libvirt-7.8.0-1.module+el8.6.0+12982+5e169f40.x86_64 One issue: There is no taint message generated when live attach a cdrom sourced by a host block device: # virsh attach-disk avocado-vt-vm1 --source /dev/cdrom --type cdrom --sourcetype block --target hda But this issue seems not related with this fix for this bug. Other scenarios work well. 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 (Moderate: 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:1759 |
Description of problem: Start a vm, execute some operations that can produce taint message, then restart libvirtd and check dominfo, and found that Taint message generated during vm running is not preserved during libvirtd restart Version-Release number of selected component (if applicable): libvirt-7.3.0-1.module+el8.5.0+11004+f4810536.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start a vm 2. Execute some operations that can produce taint message, e.g. 1) Execute agent command virsh qemu-agent-command $vm '{"execute": "guest-info"}' 2) Hotplug a cdrom type disk sourced by host block device # virsh attach-disk avocado-vt-vm1 --source /dev/cdrom --type cdrom --sourcetype block --target hda 3) Hotplug a interface device with script # virsh attach-device avocado-vt-vm1 net.xml # cat net.xml <interface type='ethernet'> <script path='/etc/qemu-ifup'/> </interface> 3. Check dominfo: # virsh dominfo avocado-vt-vm1 Id: 4 Name: avocado-vt-vm1 UUID: fa26e276-1bb1-47eb-be0e-57e8bb8cf0d9 OS Type: hvm State: running ... Messages: tainted: network configuration using opaque shell scripts tainted: potentially unsafe use of host CPU passthrough tainted: use of host cdrom passthrough tainted: custom guest agent control commands issued 4. Restart libvirtd 5. Check dominfo: # virsh dominfo avocado-vt-vm1 Id: 4 Name: avocado-vt-vm1 UUID: fa26e276-1bb1-47eb-be0e-57e8bb8cf0d9 OS Type: hvm State: running ... Messages: tainted: potentially unsafe use of host CPU passthrough Actual results: Taint message that are generated when vm starts is preserved during libvirtd restart, but not for those generated when vm is running Expected results: All taint messages should be preserved during libvirtd restart Additional info: