On 02/09/2016 10:54 AM, Vladimir Sementsov-Ogievskiy wrote:
> On 09.02.2016 00:14, John Snow wrote:
>>
>> On 02/06/2016 04:19 AM, Vladimir Sementsov-Ogievskiy wrote:
>>> On 05.02.2016 22:48, John Snow wrote:
On 01/22/2016 12:07 PM, Vladimir Sementsov-Ogievskiy wrote:
> Hi all.
>
On 09.02.2016 00:14, John Snow wrote:
On 02/06/2016 04:19 AM, Vladimir Sementsov-Ogievskiy wrote:
On 05.02.2016 22:48, John Snow wrote:
On 01/22/2016 12:07 PM, Vladimir Sementsov-Ogievskiy wrote:
Hi all.
This is the early begin of the series which aims to add external backup
api. This is nee
On 02/06/2016 04:19 AM, Vladimir Sementsov-Ogievskiy wrote:
> On 05.02.2016 22:48, John Snow wrote:
>>
>> On 01/22/2016 12:07 PM, Vladimir Sementsov-Ogievskiy wrote:
>>> Hi all.
>>>
>>> This is the early begin of the series which aims to add external backup
>>> api. This is needed to allow backup
On 05.02.2016 22:48, John Snow wrote:
On 01/22/2016 12:07 PM, Vladimir Sementsov-Ogievskiy wrote:
Hi all.
This is the early begin of the series which aims to add external backup
api. This is needed to allow backup software use our dirty bitmaps.
Vmware and Parallels Cloud Server have this fea
On 01/22/2016 12:07 PM, Vladimir Sementsov-Ogievskiy wrote:
> Hi all.
>
> This is the early begin of the series which aims to add external backup
> api. This is needed to allow backup software use our dirty bitmaps.
>
> Vmware and Parallels Cloud Server have this feature.
>
Have a link to the
Hi all.
This is the early begin of the series which aims to add external backup
api. This is needed to allow backup software use our dirty bitmaps.
Vmware and Parallels Cloud Server have this feature.
There is only one patch here, about querying dirty bitmap from qemu by
qmp command. It is just