From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xenproject.org
Subject: stale hypervisor info in HVM after migration
Date: Fri, 14 Sep 2018 10:29:07 +0200 [thread overview]
Message-ID: <20180914102907.1337e33b.olaf@aepfle.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 405 bytes --]
During boot of a HVM domU, the running hypervisor ist recorded in DMI and dmesg:
crash> dmesg | grep -m1 Xen
[ 0.000000] DMI: Xen HVM domU, BIOS 4.7.2_02-36.1.1284 08/28/2017
But after migration to another host, that info is not updated.
Is there a chance to update that info in the kernels "resume" path?
It would probably be ok to just do a printk in case DMI is a static string.
Olaf
[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2018-09-14 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:29 Olaf Hering [this message]
2018-09-14 10:19 ` stale hypervisor info in HVM after migration Roger Pau Monné
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=20180914102907.1337e33b.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xenproject.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 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).