On 10/20/2022 2:13 PM, Parav Pandit wrote:
From: Si-Wei Liu
Sent: Thursday, October 20, 2022 2:12 PM
On 10/19/2022 10:25 PM, Jason Wang wrote:
On Wed, Oct 19, 2022 at 8:56 AM Si-Wei Liu
wrote:
Live migration of vdpa would typically require re-instate vdpa device
with an idential set of con
> From: Si-Wei Liu
> Sent: Thursday, October 20, 2022 2:12 PM
>
>
> On 10/19/2022 10:25 PM, Jason Wang wrote:
> > On Wed, Oct 19, 2022 at 8:56 AM Si-Wei Liu
> wrote:
> >> Live migration of vdpa would typically require re-instate vdpa device
> >> with an idential set of configs on the destinatio
On 10/19/2022 10:25 PM, Jason Wang wrote:
On Wed, Oct 19, 2022 at 8:56 AM Si-Wei Liu wrote:
Live migration of vdpa would typically require re-instate vdpa
device with an idential set of configs on the destination node,
same way as how source node created the device in the first
place. In ord
On Wed, Oct 19, 2022 at 8:56 AM Si-Wei Liu wrote:
>
> Live migration of vdpa would typically require re-instate vdpa
> device with an idential set of configs on the destination node,
> same way as how source node created the device in the first
> place. In order to save orchestration software from
Live migration of vdpa would typically require re-instate vdpa
device with an idential set of configs on the destination node,
same way as how source node created the device in the first
place. In order to save orchestration software from memorizing
and keeping track of vdpa config, it will be help
