Bug 1967895 - qemu-kvm killed by SIGSEGV during live storage migration
Summary: qemu-kvm killed by SIGSEGV during live storage migration
Keywords:
Status: CLOSED DUPLICATE of bug 1888344
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: 8.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.5
Assignee: Kevin Wolf
QA Contact: aihua liang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-04 10:37 UTC by Marian Jankular
Modified: 2024-10-01 18:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-08 07:34:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marian Jankular 2021-06-04 10:37:20 UTC 
Description of problem: 
qemu-kvm killed by SIGSEGV


Version-Release number of selected component (if applicable):
Red Hat Virtualization Host 4.4.5

kernel-4.18.0-240.22.1.el8_3.x86_64
qemu-kvm-5.1.0-21.module+el8.3.1+10464+8ad18d1a.x86_64

How reproducible:
during the live storage migration (does not have to be the real reason )

1 time occurence

Actual results:
qemu-kvm killed by SIGSEGV

Expected results:
vm will continue running

Additional info:
attaching coredump
Comment 3 John Ferlan 2021-06-04 11:59:46 UTC 
Fixing the product, component assignment, pool, and adding RHV to the dependent products
Comment 5 John Ferlan 2021-06-04 12:18:29 UTC 
Kevin - assigning to you since it was your tree for the commit. "If" a z-stream was requested to AV 8.4.0, how complicated would it be? I can only assume it could be more than just 1 patch.

As for process, I set ITR=8.5.0 and can look to get it to ON_QA once all the fields are adjusted. It would be good to get QE to develop some reproducer for 8.4 and prove that 8.5 does fix it...
Comment 7 aihua liang 2021-06-08 07:34:50 UTC 

*** This bug has been marked as a duplicate of bug 1888344 ***
Note You need to log in before you can comment on or make changes to this bug.