Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1592786

Summary: Starting guest crashes host (kvm/qemu/libvirt)
Product: Red Hat Enterprise Linux 7 Reporter: fred.filozof
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED NOTABUG QA Contact: jiyan <jiyan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.5CC: fred.filozof, jsuchane, lhuang, lmen, pkrempa, xuzhang, yalzhang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-23 07:15:46 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:
Description Flags
Logs none

Description fred.filozof 2018-06-19 10:07:45 UTC 
Created attachment 1452868 [details]
Logs

Description of problem:
Starting virtual machine (kvm+qemu+libvirt) crashes host.

Version-Release number of selected component (if applicable):
ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch
libvirt-3.9.0-14.el7_5.5.x86_64
libvirt-admin-3.9.0-14.el7_5.5.x86_64
libvirt-client-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-config-network-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-config-nwfilter-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-interface-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-lxc-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-network-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-nodedev-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-nwfilter-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-qemu-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-secret-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-storage-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-storage-core-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-storage-disk-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-storage-gluster-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-storage-iscsi-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-storage-logical-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-storage-mpath-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-storage-rbd-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-driver-storage-scsi-3.9.0-14.el7_5.5.x86_64
libvirt-daemon-kvm-3.9.0-14.el7_5.5.x86_64
libvirt-glib-1.0.0-1.el7.x86_64
libvirt-libs-3.9.0-14.el7_5.5.x86_64
libvirt-python-3.9.0-1.el7.x86_64
qemu-img-1.5.3-156.el7_5.2.x86_64
qemu-kvm-1.5.3-156.el7_5.2.x86_64
qemu-kvm-common-1.5.3-156.el7_5.2.x86_64


How reproducible:
Brand-new CentOS 7 installation with the following:
yum groupinstall "Virtualization Host"
yum install virt-manager virt-viewer

Steps to Reproduce:
1. Configure virtual machine (guest) with virt-manager
2. start guest
3. After 10-15 seconds host crashes and reboots 

Actual results:


Expected results:


Additional info:
I was using kvm+qemu+libvirt for about 6 years on the same host.
After replacing motherboard and CPU hypervisor crashes host.

Software:
CentOS Linux release 7.5.1804 (Core)

Hardware:
Intel(R) Xeon(R) CPU E3-1270 V2 @ 3.50GHz
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt ibpb ibrs stibp dtherm arat pln pts spec_ctrl intel_stibp

Base Board Information
        Manufacturer: ASUSTeK Computer INC.
        Product Name: P8B WS
        Version: Rev 1.xx
        Serial Number: ST2019010000193
        Asset Tag: To be filled by O.E.M.
        Features:
                Board is a hosting board
                Board is replaceable
        Location In Chassis: To be filled by O.E.M.
        Chassis Handle: 0x0003
        Type: Motherboard
        Contained Object Handles: 0
Comment 2 Jaroslav Suchanek 2018-07-13 11:54:45 UTC 
Can you please share also the configuration of the 'mw' domain? Either way, the probability that libvirt would cause host crash is pretty low, but we should investigate.

Thanks.
Comment 3 fred.filozof 2018-07-21 20:06:26 UTC 
Hi Jaroslav,

Please cancel the request.
It seems that the culprit of all the problems is the new motherboard I bought (Asus P8B WS that turned out to be refurbished; before that I had the same model of the motherboard that worked fine for about 6 years until I accidently broke the pins of socket and had to replace the mobo). It must be faulty in some way because I noticed crashing the host also during an attempt to encrypt the pendrive with VeraCrypt software. The replacement motherboard didn't want to work with old Sandy Bridge processor. I bought Ivy Bridge processor that it could work with but with some issues.

It's all ASUS' policy fault. 
Instead to withdraw broken motherboards they try to sell them with hope the consumer will not be able to figure out it is broken and retun it on time to get refund. That's how they make money these days. Shame on you ASUS!

Regards,
Jan
Comment 4 Peter Krempa 2018-07-23 07:15:46 UTC 
Okay then I removed the needinfo and I'll close this bug. Please file a new one or reopen if you'll suspect a software problem.