27.10.2020 19:42, Andrey Shinkevich wrote:
On 27.10.2020 19:21, Vladimir Sementsov-Ogievskiy wrote:
27.10.2020 19:01, Andrey Shinkevich wrote:
On 27.10.2020 18:09, Vladimir Sementsov-Ogievskiy wrote:
22.10.2020 21:13, Andrey Shinkevich wrote:
Avoid writing a filter JSON file name and a
On 27.10.2020 19:21, Vladimir Sementsov-Ogievskiy wrote:
27.10.2020 19:01, Andrey Shinkevich wrote:
On 27.10.2020 18:09, Vladimir Sementsov-Ogievskiy wrote:
22.10.2020 21:13, Andrey Shinkevich wrote:
Avoid writing a filter JSON file name and a filter format name to QCOW2
image when the
27.10.2020 19:01, Andrey Shinkevich wrote:
On 27.10.2020 18:09, Vladimir Sementsov-Ogievskiy wrote:
22.10.2020 21:13, Andrey Shinkevich wrote:
Avoid writing a filter JSON file name and a filter format name to QCOW2
image when the backing file is changed after the block stream job.
A user is
On 27.10.2020 18:09, Vladimir Sementsov-Ogievskiy wrote:
22.10.2020 21:13, Andrey Shinkevich wrote:
Avoid writing a filter JSON file name and a filter format name to QCOW2
image when the backing file is changed after the block stream job.
A user is still able to assign the 'backing-file'
22.10.2020 21:13, Andrey Shinkevich wrote:
Avoid writing a filter JSON file name and a filter format name to QCOW2
image when the backing file is changed after the block stream job.
A user is still able to assign the 'backing-file' parameter for a
block-stream job keeping in mind the possible
Avoid writing a filter JSON file name and a filter format name to QCOW2
image when the backing file is changed after the block stream job.
A user is still able to assign the 'backing-file' parameter for a
block-stream job keeping in mind the possible issue mentioned above.
If the user does not
