Bug 2004416
Summary: | fails to revert snapshot of a VM [balloon/page-poison] | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Dr. David Alan Gilbert <dgilbert> | |
Component: | qemu-kvm | Assignee: | Dr. David Alan Gilbert <dgilbert> | |
qemu-kvm sub component: | Live Migration | QA Contact: | Yumei Huang <yuhuang> | |
Status: | CLOSED ERRATA | Docs Contact: | Jiri Herrmann <jherrman> | |
Severity: | high | |||
Priority: | high | CC: | coli, ddepaula, dgilbert, gfialova, jherrman, jinzhao, juzhang, kkiwi, mcasquer, mmarhefk, pkrempa, virt-maint, vpolasek, xiaohli, xuzhang, yisun, yuhuang | |
Version: | 8.6 | Flags: | yuhuang:
needinfo-
|
|
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | qemu-kvm-6.2.0-1.module+el8.6.0+13725+61ae1949 | Doc Type: | Bug Fix | |
Doc Text: |
.VM migration and snapshots no longer failing due to `virtio-balloon`
Previously, attempting to migrate a virtual machine (VMs) with a more recent guest operating system (such as RHEL 9) failed if the VM was using the `virtio-balloon` device. Similarly, creating a snapshot of such a VM failed. This update fixes a bug in the `page poison` feature of `virtio-balloon`, which prevents the described problem from occurring.
|
Story Points: | --- | |
Clone Of: | 1984401 | |||
: | 2004535 (view as bug list) | Environment: | ||
Last Closed: | 2022-05-10 13:21:40 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: | ||||
Bug Depends On: | 1984401, 2027716 | |||
Bug Blocks: | 2004535 |
Description
Dr. David Alan Gilbert
2021-09-15 08:51:35 UTC
Upstream patch/discussion: https://lists.nongnu.org/archive/html/qemu-devel/2021-09/msg03682.html Will clone for AV 8.5.0 to ensure this gets fixed there too. Reproduced with rhel8.5 guest(adding page_poison=1 kernel option) with q35 machine type. qemu-kvm-6.0.0-29.module+el8.5.0+12386+43574bac guest kernel: 4.18.0-332.el8.x86_64 This is now merged upstream in 243a9284a989a38e32ce so 8.6 will get it when it does the 6.2 rebase. -> POST (I have done a c9s backport for bz 1984401) Mass update of DTM/ITM to +3 values since the rebase of qemu-6.2 into RHEL 8.6 has been delayed or slowed due to process roadblocks (authentication changes, gating issues). This avoids the DevMissed bot and worse the bot that could come along and strip release+. The +3 was chosen mainly to give a cushion. Also added the qemu-6.2 rebase bug 2027716 as a dependent. QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass. Test steps: 1. Boot rhel8.6 guest with balloon device under q35, see the full cmdline below. 2. Add 'page_poison=1' to guest kernel line, and reboot guest. 3. Create internal snapshot and revert it. (qemu) savevm sn0 (qemu) loadvm sn0 Reproduce: qemu-kvm-6.1.0-5.module+el8.6.0+13430+8fdd5f85 host kernel: 4.18.0-355.el8.x86_64 guest kernel: 4.18.0-356.el8.x86_64 Loadvm hit error as below, (qemu) loadvm sn0 VQ 1 size 0x80 < last_avail_idx 0x0 - used_idx 0x32b0 Failed to load virtio-balloon:virtio error while loading state for instance 0x0 of device '0000:00:05.0:00.0/virtio-balloon' Error: Error -1 while loading VM state Verify: qemu-kvm-6.2.0-1.module+el8.6.0+13725+61ae1949 host kernel: 4.18.0-355.el8.x86_64 guest kernel: 4.18.0-356.el8.x86_64 The issue is gone, so it's been fixed. Full qemu-kvm command: /usr/libexec/qemu-kvm \ -name 'avocado-vt-vm1' \ -machine q35 \ -nodefaults \ -device VGA,bus=pcie.0,addr=0x1 \ -device pvpanic,ioport=0x505,id=id5SK4co \ -device pcie-root-port,id=pcie.0-root-port-2,slot=2,chassis=2,addr=0x2,bus=pcie.0 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie.0,addr=0x3 \ -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/rhel860-64-virtio-scsi.qcow2 \ -device scsi-hd,id=image1,drive=drive_image1 \ -device pcie-root-port,id=pcie.0-root-port-4,slot=4,chassis=4,addr=0x4,bus=pcie.0 \ -device virtio-net-pci,mac=9a:41:3a:3b:3c:3d,id=idzyzw7g,vectors=4,netdev=idhia6GM,bus=pcie.0-root-port-4,addr=0x0 \ -netdev tap,id=idhia6GM \ -smp 8 \ -m 8G,maxmem=80G,slots=20 \ -cpu host \ -vnc :1 \ -rtc base=utc,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off,strict=off \ -enable-kvm \ -device pcie-root-port,id=pcie.0-root-port-5,slot=5,chassis=5,addr=0x5,bus=pcie.0 \ -device virtio-balloon-pci,id=balloon0,bus=pcie.0-root-port-5 \ -monitor stdio \ -serial tcp:0:1234,server,nowait \ -monitor unix:/tmp/monitor3,server,nowait \ -qmp tcp:0:3333,server,nowait \ 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 |