stale hypervisor info in HVM after migration

stale hypervisor info in HVM after migration

[Olaf Hering]

[-- 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

Re: stale hypervisor info in HVM after migration

[Roger Pau Monné]

On Fri, Sep 14, 2018 at 10:29:07AM +0200, Olaf Hering wrote:
> 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.

There's no way to change what's printed in dmesg, and printing it
again on resume from migration seems unhelpful to me. Instead of
grepping dmesg to get the DMI information you should use dmidecode [0]
which I expect will print the updated information after migration.

Roger.

[0] https://www.nongnu.org/dmidecode/

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel