|
From: | Anton Kuchin |
Subject: | Re: [PATCH v3 1/1] vhost-user-fs: add migration type property |
Date: | Mon, 6 Mar 2023 22:55:29 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 |
On 01/03/2023 22:22, Michael S. Tsirkin wrote:
On Wed, Mar 01, 2023 at 09:35:56PM +0200, Anton Kuchin wrote:I do trust them :) I have to, otherwise we would need to pack all the properties and flags of qemu to the migration stream and validate them at destination or entire migration ends up broken beyond repair if orchestrators tend to do stupid things and need babysitting.This is not at all a crazy idea. It has some disadvantages too esp around cross version migration, which is why we don't do this yet.
Indeed. I know VMMs that chose this path. But as long as qemu decided to trust orchestrators I think we'd better keep this consistent across the codebase. Only ivshmem_pre_load callback bothers to check device property and virtio_net_tx_waiting_pre_load checks that number of queue pairs doesn't exceed allowed maximum, all other *_pre_load functions generally just initialize some parts of state that need to be set before stream starts loading.
[Prev in Thread] | Current Thread | [Next in Thread] |