From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Wolfgang Bumiller <w.bumiller@proxmox.com>
Cc: Stefan Reiter <s.reiter@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
alexandre derumier <aderumier@odiso.com>
Subject: Re: [pve-devel] applied: Re: [PATCH qemu] drop patch force-disabling smm
Date: Tue, 24 Aug 2021 11:28:43 +0200 [thread overview]
Message-ID: <f0383edc-23c7-d3de-5711-d0a24448ac66@proxmox.com> (raw)
In-Reply-To: <20210824092419.ztsmgdymgv6kagv4@olga.proxmox.com>
On 24/08/2021 11:24, Wolfgang Bumiller wrote:
> On Tue, Aug 24, 2021 at 11:19:52AM +0200, Thomas Lamprecht wrote:
>> On 24/08/2021 10:52, Stefan Reiter wrote:
>>> I've tested live-migration in both directions (with patch <-> current),
>>> Linux and Windows guests on a nested setup (but SMM is emulated in QEMU
>>> so nested shouldn't matter AFAIU). All worked without issue.
>>>
>>> I'm not sure if there is something specific a guest would need to do to
>>> exercise SMM support, but since we're turning it on, not off, I'm pretty
>>> sure that at least forward migration should always work.
>>
>> sounds sensible
>
> I think this mostly happens on boot, so perhaps migrating to a patched
> qemu, *soft*-rebooting the guest and then migrating back might be a
> problem.
>
But the backmigration from new -> old is not supported by us anyway, so even if
that would cause a problem it's a non issue.
prev parent reply other threads:[~2021-08-24 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 7:55 [pve-devel] " Wolfgang Bumiller
2021-08-10 13:47 ` alexandre derumier
2021-08-23 16:01 ` Thomas Lamprecht
2021-08-24 8:52 ` Stefan Reiter
2021-08-24 9:19 ` [pve-devel] applied: " Thomas Lamprecht
2021-08-24 9:24 ` Wolfgang Bumiller
2021-08-24 9:28 ` 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=f0383edc-23c7-d3de-5711-d0a24448ac66@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.reiter@proxmox.com \
--cc=w.bumiller@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 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.