From: Mario Smarduch <msmarduch@digitalocean.com>
To: philmd@redhat.com, mtosatti@redhat.com, pbonzini@redhat.com,
armbru@redhat.com
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org, rth@twiddle.net,
ehabkost@redhat.com, Mario Smarduch <msmarduch@digitalocean.com>
Subject: [PATCHv2 0/2] log guest name and memory error type AO, AR for MCEs
Date: Wed, 9 Oct 2019 09:44:57 -0700 [thread overview]
Message-ID: <20191009164459.8209-1-msmarduch@digitalocean.com> (raw)
In a large VPC environment we want to log memory error occurrences
and log them with guest name and type - there are few use cases
- if VM crashes on AR mce inform the user about the reason and resolve the case
- if VM hangs notify the user to reboot and resume processing
- if VM continues to run let the user know, he/she maybe able to correlate
to vm internal outage
- Rawhammer attacks - isolate/determine the attacker possible migrating it off
the hypervisor
- In general track memory errors on a hyperviosr over time to determine trends
Monitoring our fleet we come across quite a few of these and been
able to take action where before there were no clues to the causes.
When memory error occurs we get a log entry in qemu log:
Guest [Droplet-12345678] 2019-08-02T05:00:11.940270Z qemu-system-x86_64:
Guest MCE Memory Error at QEMU addr 0x7f3c7622f000 and GUEST 0x78e42f000
addr of type BUS_MCEERR_AR injected
with enterprise logging environment we can to take further actions.
v1 -> v2:
- split into two patches one to get the gustname second to log MCEs
- addressed comments for MCE logging
Mario Smarduch (2):
util/qemu-error: add guest name helper with -msg options
target/i386: log MCE guest and host addresses
include/qemu/error-report.h | 1 +
qemu-options.hx | 10 ++++++----
target/i386/kvm.c | 29 ++++++++++++++++++++++++-----
util/qemu-error.c | 31 +++++++++++++++++++++++++++++++
vl.c | 5 +++++
5 files changed, 67 insertions(+), 9 deletions(-)
--
2.9.3
next reply other threads:[~2019-10-09 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 16:44 Mario Smarduch [this message]
2019-10-09 16:44 ` [PATCHv2 1/2] util/qemu-error: add guest name helper with -msg options Mario Smarduch
2019-10-09 21:16 ` Paolo Bonzini
2019-10-10 7:02 ` Markus Armbruster
2019-10-10 8:16 ` Markus Armbruster
2019-10-10 11:25 ` Paolo Bonzini
2019-10-09 16:44 ` [PATCHv2 2/2] target/i386: log MCE guest and host addresses Mario Smarduch
2019-10-09 21:19 ` [PATCHv2 0/2] log guest name and memory error type AO, AR for MCEs Paolo Bonzini
2019-10-09 23:01 ` Mario Smarduch
2019-10-09 22:55 ` no-reply
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=20191009164459.8209-1-msmarduch@digitalocean.com \
--to=msmarduch@digitalocean.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rth@twiddle.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).