From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 197813] KVM: entry failed, hardware error 0x5
Date: Thu, 15 Feb 2018 18:12:08 +0000 [thread overview]
Message-ID: <bug-197813-28872-xKGWjYxRrW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197813-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197813
--- Comment #5 from Bandan Das (bsd@redhat.com) ---
bugzilla-daemon@bugzilla.kernel.org writes:
> https://bugzilla.kernel.org/show_bug.cgi?id=197813
>
> --- Comment #4 from Carlos Lopez (clopezbelenguer@es.amnesty.org) ---
> At the moment since we are using PRoxmox and they build the distro around the
> ubuntu kernel we could wait until the release of ubuntu 18.04 when they build
> the next versión to try a new kernel.
> but
> Considering we haven't the skills to debug more thoroughly the panic, atm,
> we
> are thinking in Downgrade the platform to an older one and see if the problem
> persist.
> We have been experiencing worse and worse behaviour at every update of the
> kernel/distro
This does sound good. If you can run an older version of the kernel and confirm
if the issue goes away, that would be a good place to start. Please update the
bug
with the older kernel version when you get a chance to run this test.
> Since we have another machine with an older processor from the same family
> and
> we are not experiencing any issues i attach cpuinfo of the problematic one
> and
> the goodold one in case is relevant.
What's the qemu cmdline for the Haswell host ? Can you try -cpu Haswell on the
Broadwell
host as well and see if it makes any difference ?
> [KVM WITh panics/frozen vm]
> Kernel
>
> 4.13.13-5-pve #1 SMP PVE 4.13.13-38 x86_64
>
> processor : 40
> vendor_id : GenuineIntel
> cpu family : 6
> model : 79
> model name : Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
> stepping : 1
> microcode : 0xb000021
> cpu MHz : 2199.991
> cache size : 30720 KB
> physical id : 0
> siblings : 24
> core id : 10
> cpu cores : 12
> apicid : 21
> initial apicid : 21
> fpu : yes
> fpu_exception : yes
> cpuid level : 20
> wp : yes
> 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 pdpe1gb
> rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
> nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est
> tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt
> tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
> cpuid_fault epb cat_l3 cdp_l3 invpcid_single intel_pt tpr_shadow vnmi
> flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms
> invpcid
> rtm cqm rdt_a rdseed adx smap xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total
> cqm_mbm_local dtherm ida arat pln pts
> bugs : cpu_meltdown spectre_v1 spectre_v2
> bogomips : 4399.98
> clflush size : 64
> cache_alignment : 64
> address sizes : 46 bits physical, 48 bits virtual
> power management:
>
>
> [KVM WITHOUT PROBLEMS]
> Kernel 4.4.95-1-pve #1 SMP PVE 4.4.95-99
>
> processor : 39
> vendor_id : GenuineIntel
> cpu family : 6
> model : 63
> model name : Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
> stepping : 2
> microcode : 0x31
> cpu MHz : 2743.203
> cache size : 25600 KB
> physical id : 1
> siblings : 20
> core id : 12
> cpu cores : 10
> apicid : 57
> initial apicid : 57
> fpu : yes
> fpu_exception : yes
> cpuid level : 15
> wp : yes
> 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 pdpe1gb
> 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 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt
> tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb tpr_shadow vnmi
> flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid
> cqm
> xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts
> bugs :
> bogomips : 5201.14
> clflush size : 64
> cache_alignment : 64
> address sizes : 46 bits physical, 48 bits virtual
> power management:
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2018-02-15 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 9:28 [Bug 197813] New: KVM: entry failed, hardware error 0x5 bugzilla-daemon
2018-02-13 17:26 ` [Bug 197813] " bugzilla-daemon
2018-02-13 17:32 ` bugzilla-daemon
2018-02-13 18:13 ` bugzilla-daemon
2018-02-14 15:15 ` bugzilla-daemon
2018-02-15 18:12 ` Bandan Das
2018-02-15 18:12 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-197813-28872-xKGWjYxRrW@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.