Re: [PATCH v0 0/2] allow to set 'drive' property on a realized block device

2020-03-02 Thread Vladimir Sementsov-Ogievskiy
02.03.2020 18:39, Kevin Wolf wrote: Am 02.03.2020 um 14:55 hat Denis Plotnikov geschrieben: On 02.03.2020 16:38, Kevin Wolf wrote: Am 10.11.2019 um 20:03 hat Denis Plotnikov geschrieben: This allows to replace the file on a block device and is useful to workaround the cases (migration) when

Re: [PATCH v0 0/2] allow to set 'drive' property on a realized block device

2020-03-02 Thread Kevin Wolf
Am 02.03.2020 um 14:55 hat Denis Plotnikov geschrieben: > > > On 02.03.2020 16:38, Kevin Wolf wrote: > > Am 10.11.2019 um 20:03 hat Denis Plotnikov geschrieben: > > > This allows to replace the file on a block device and is useful > > > to workaround the cases (migration) when the VM image is

Re: [PATCH v0 0/2] allow to set 'drive' property on a realized block device

2020-03-02 Thread Denis Plotnikov
On 02.03.2020 16:38, Kevin Wolf wrote: Am 10.11.2019 um 20:03 hat Denis Plotnikov geschrieben: This allows to replace the file on a block device and is useful to workaround the cases (migration) when the VM image is placed on some shared storage with exclusive file opening model but the

Re: [PATCH v0 0/2] allow to set 'drive' property on a realized block device

2020-03-02 Thread Kevin Wolf
Am 10.11.2019 um 20:03 hat Denis Plotnikov geschrieben: > This allows to replace the file on a block device and is useful > to workaround the cases (migration) when the VM image is placed on > some shared storage with exclusive file opening model but the image > should be open form more than one

Re: [PATCH v0 0/2] allow to set 'drive' property on a realized block device

2019-11-18 Thread Denis Plotnikov
Ping! On 10.11.2019 22:03, Denis Plotnikov wrote: > This allows to replace the file on a block device and is useful > to workaround the cases (migration) when the VM image is placed on > some shared storage with exclusive file opening model but the image > should be open form more than one app. >