>I guess the only thing that would need to implement something new is
>qcow2_snapshot_goto(), which currently refuses to load a snapshot that
>has a different disk size.
>Once this is done, just removing the check in qcow2_truncate() should be
>okay.
Thanks! I'll see what I can do, later.
Am 06.01.2016 um 17:30 hat Max Reitz geschrieben:
> On 06.01.2016 17:28, Eric Blake wrote:
> > On 01/06/2016 09:20 AM, Max Reitz wrote:
> >
> >>> If I take a snapshot while the guest sees a 1G disk, then resize the
> >>> disk to 2G, then roll back to the point in time of the snapshot, I'd
> >>> ex
On 06.01.2016 17:28, Eric Blake wrote:
> On 01/06/2016 09:20 AM, Max Reitz wrote:
>
>>> If I take a snapshot while the guest sees a 1G disk, then resize the
>>> disk to 2G, then roll back to the point in time of the snapshot, I'd
>>> expect the disk to roll back to 1G in size. Anything else is li
On 01/06/2016 09:20 AM, Max Reitz wrote:
>> If I take a snapshot while the guest sees a 1G disk, then resize the
>> disk to 2G, then roll back to the point in time of the snapshot, I'd
>> expect the disk to roll back to 1G in size. Anything else is likely to
>> confuse the guest. And that's what
On 06.01.2016 16:04, Eric Blake wrote:
> On 01/05/2016 07:50 PM, lihuiba wrote:
>> At 2016-01-05 21:55:56, "Eric Blake" wrote:
>>> On 01/05/2016 05:10 AM, lihuiba wrote:
>>>
>> In our production environment, we need to extend a qcow2 image with
>> snapshots in it.
>>>
> The thing is th
On 01/05/2016 07:50 PM, lihuiba wrote:
> At 2016-01-05 21:55:56, "Eric Blake" wrote:
>> On 01/05/2016 05:10 AM, lihuiba wrote:
>>
> In our production environment, we need to extend a qcow2 image with
> snapshots in it.
>>
The thing is that one would need to update all the inactive L1
At 2016-01-05 21:55:56, "Eric Blake" wrote:
>On 01/05/2016 05:10 AM, lihuiba wrote:
>
In our production environment, we need to extend a qcow2 image with
snapshots in it.
>
>>> The thing is that one would need to update all the inactive L1 tables. I
>>> don't think it should be too diffi
On 01/05/2016 08:55 AM, Eric Blake wrote:
> On 01/05/2016 05:10 AM, lihuiba wrote:
>
In our production environment, we need to extend a qcow2 image with
snapshots in it.
>
>>> The thing is that one would need to update all the inactive L1 tables. I
>>> don't think it should be too dif
On 01/05/2016 05:10 AM, lihuiba wrote:
>>> In our production environment, we need to extend a qcow2 image with
>>> snapshots in it.
>> The thing is that one would need to update all the inactive L1 tables. I
>> don't think it should be too difficult, it's just that apparently so far
>> nobody eve
Max,
I'll see what I can do, and give you my plan.
Thanks!
>On 29.12.2015 10:38, lihuiba wrote:
>> Hi,
>>
>> In our production environment, we need to extend a qcow2 image with
>> snapshots in it. This feature, however, is not implemented yet.
>>
>> So I want to ask, if this feature is und
On 29.12.2015 10:38, lihuiba wrote:
> Hi,
>
> In our production environment, we need to extend a qcow2 image with
> snapshots in it. This feature, however, is not implemented yet.
>
> So I want to ask, if this feature is under active development?
No, it is not.
> How can I
> help with this fea
Hi,
In our production environment, we need to extend a qcow2 image with snapshots
in it. This feature, however, is not implemented yet.
So I want to ask, if this feature is under active development? How can I help
with this feature?
It seems that, this feature is not too difficult as long
12 matches
Mail list logo