From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH-SERIES swtpm/qemu-server] Improve swtpm logging
Date: Thu, 23 Feb 2023 16:19:23 +0100 [thread overview]
Message-ID: <68d31e63-f2fe-96a7-ea92-f07b43b9e0db@proxmox.com> (raw)
In-Reply-To: <20230118122109.304270-1-f.ebner@proxmox.com>
Am 18/01/2023 um 13:21 schrieb Fiona Ebner:
> There was a recent failure when migrating a production VM
>> kvm: tpm-emulator: Setting the stateblob (type 1) failed with a TPM error 0x3 a parameter is bad
>> kvm: error while loading state for instance 0x0 of device 'tpm-emulator'
>> kvm: load of migration failed: Input/output error
> and it's not clear what exactly triggered it.
>
> Start collecting logs in /run/qemu-server/<ID>-swtpm.log to have some
> information available for any future swtpm failures.
>
> Also add a few more logs in swtpm itself, to better see what exactly
> triggers the TPM_BAD_PARAMETER (0x3) error in case such a migration
> failure happens again.
>
>
> swtpm:
>
> Fiona Ebner (1):
> control channel: add error logs upon receiving short input
>
> src/swtpm/ctrlchannel.c | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
>
> qemu-server:
>
> Fiona Ebner (2):
> swtpm: enable logging
> swtpm: use start time as prefix for logging
>
> PVE/QemuServer.pm | 5 +++++
> 1 file changed, 5 insertions(+)
>
applied all three patches, thanks!
prev parent reply other threads:[~2023-02-23 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 12:21 [pve-devel] " Fiona Ebner
2023-01-18 12:21 ` [pve-devel] [PATCH swtpm 1/1] control channel: add error logs upon receiving short input Fiona Ebner
2023-01-18 12:21 ` [pve-devel] [PATCH qemu-server 1/2] swtpm: enable logging Fiona Ebner
2023-01-18 12:21 ` [pve-devel] [PATCH qemu-server 2/2] swtpm: use start time as prefix for logging Fiona Ebner
2023-02-23 15:19 ` Thomas Lamprecht [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=68d31e63-f2fe-96a7-ea92-f07b43b9e0db@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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