On 01/13/16 12:11, Denis V. Lunev wrote:
> On 01/13/2016 01:37 PM, Laszlo Ersek wrote:
>> meta comment here:
>>
>> On 01/12/16 16:47, Denis V. Lunev wrote:
>>
>>> P.S. Here is a summary that my colleague has receiver from libvirt
>>> list.
>>>
>>> Forwarded Message
>>> Sub
On 01/13/2016 01:37 PM, Laszlo Ersek wrote:
meta comment here:
On 01/12/16 16:47, Denis V. Lunev wrote:
P.S. Here is a summary that my colleague has receiver from libvirt
list.
Forwarded Message
Subject: Re: Snapshotting OVMF guests
Date: Mon, 11 Jan 2016 13:56:29 +0
On 01/12/16 18:40, Markus Armbruster wrote:
> Kevin Wolf writes:
>
>> Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
>>> On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
On 01/12/2016 06:20 PM, Kevin Wolf wrote:
> Am 12.01.2016 um 15:59 hat Paolo Bonzini geschrieben:
>>
>> O
On 01/12/16 18:50, Kevin Wolf wrote:
> Am 12.01.2016 um 18:40 hat Markus Armbruster geschrieben:
>> Kevin Wolf writes:
>>
>>> Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
> On 01/12/2016 06:20 PM, Kevin Wolf wrote:
>> Am 12.01.20
meta comment here:
On 01/12/16 16:47, Denis V. Lunev wrote:
> P.S. Here is a summary that my colleague has receiver from libvirt
>list.
>
> Forwarded Message
> Subject: Re: Snapshotting OVMF guests
> Date: Mon, 11 Jan 2016 13:56:29 +0100
> From: Laszlo Ersek
> To: Dmit
Kevin Wolf writes:
> Am 12.01.2016 um 18:40 hat Markus Armbruster geschrieben:
>> Kevin Wolf writes:
>>
>> > Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
>> >> On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
>> >> >On 01/12/2016 06:20 PM, Kevin Wolf wrote:
>> >> >>Am 12.01.2016 um 15:59
On 01/12/2016 08:50 PM, Kevin Wolf wrote:
Am 12.01.2016 um 18:40 hat Markus Armbruster geschrieben:
Kevin Wolf writes:
Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
On 01/12/2016 06:20 PM, Kevin Wolf wrote:
Am 12.01.2016 um 15:59 hat P
On 01/12/2016 08:40 PM, Markus Armbruster wrote:
Kevin Wolf writes:
Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
On 01/12/2016 06:20 PM, Kevin Wolf wrote:
Am 12.01.2016 um 15:59 hat Paolo Bonzini geschrieben:
On 12/01/2016 15:16, Kevi
Am 12.01.2016 um 18:40 hat Markus Armbruster geschrieben:
> Kevin Wolf writes:
>
> > Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
> >> On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
> >> >On 01/12/2016 06:20 PM, Kevin Wolf wrote:
> >> >>Am 12.01.2016 um 15:59 hat Paolo Bonzini geschriebe
Kevin Wolf writes:
> Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
>> On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
>> >On 01/12/2016 06:20 PM, Kevin Wolf wrote:
>> >>Am 12.01.2016 um 15:59 hat Paolo Bonzini geschrieben:
>> >>>
>> >>>On 12/01/2016 15:16, Kevin Wolf wrote:
>> >Thus we
On 01/12/2016 07:52 PM, Kevin Wolf wrote:
Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
On 01/12/2016 06:20 PM, Kevin Wolf wrote:
Am 12.01.2016 um 15:59 hat Paolo Bonzini geschrieben:
On 12/01/2016 15:16, Kevin Wolf wrote:
Thus we should
Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
> On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
> >On 01/12/2016 06:20 PM, Kevin Wolf wrote:
> >>Am 12.01.2016 um 15:59 hat Paolo Bonzini geschrieben:
> >>>
> >>>On 12/01/2016 15:16, Kevin Wolf wrote:
> >Thus we should avoid selection of "p
On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
On 01/12/2016 06:20 PM, Kevin Wolf wrote:
Am 12.01.2016 um 15:59 hat Paolo Bonzini geschrieben:
On 12/01/2016 15:16, Kevin Wolf wrote:
Thus we should avoid selection of "pflash" drives for VM state
saving.
For now "pflash" is read-write raw imag
On 01/12/2016 06:20 PM, Kevin Wolf wrote:
Am 12.01.2016 um 15:59 hat Paolo Bonzini geschrieben:
On 12/01/2016 15:16, Kevin Wolf wrote:
Thus we should avoid selection of "pflash" drives for VM state saving.
For now "pflash" is read-write raw image as it configured by libvirt.
Thus there are no
On 12/01/2016 16:20, Kevin Wolf wrote:
> > Flash is already being snapshotted as part of saving RAM state. In
> > fact, for this reason the device (at least the one used with OVMF; I
> > haven't checked other pflash devices) can simply save it back to disk
> > on the migration destination, wi
Am 12.01.2016 um 16:10 hat Denis V. Lunev geschrieben:
> On 01/12/2016 05:16 PM, Kevin Wolf wrote:
> >Am 12.01.2016 um 07:03 hat Denis V. Lunev geschrieben:
> >>There is a long-long story. OVMF VMs can not be snapsotted using
> >>'virsh snapshot' as they have "pflash" device which is configured as
Am 12.01.2016 um 16:16 hat Peter Maydell geschrieben:
> On 12 January 2016 at 15:13, Denis V. Lunev wrote:
> > The idea of this patch was trivial. First of all, I would like to keep
> > this image internally snapshoted. That is why the ultimate goal
> > was to switch from raw to qcow2 to keep chan
Am 12.01.2016 um 15:59 hat Paolo Bonzini geschrieben:
>
>
> On 12/01/2016 15:16, Kevin Wolf wrote:
> >> Thus we should avoid selection of "pflash" drives for VM state saving.
> >>
> >> For now "pflash" is read-write raw image as it configured by libvirt.
> >> Thus there are no such images in the
On 12 January 2016 at 15:13, Denis V. Lunev wrote:
> The idea of this patch was trivial. First of all, I would like to keep
> this image internally snapshoted. That is why the ultimate goal
> was to switch from raw to qcow2 to keep changes inside the
> image.
>
> Though in this case this drive cou
On 01/12/2016 05:59 PM, Paolo Bonzini wrote:
On 12/01/2016 15:16, Kevin Wolf wrote:
Thus we should avoid selection of "pflash" drives for VM state saving.
For now "pflash" is read-write raw image as it configured by libvirt.
Thus there are no such images in the field and we could safely disabl
On 01/12/2016 05:16 PM, Kevin Wolf wrote:
Am 12.01.2016 um 07:03 hat Denis V. Lunev geschrieben:
There is a long-long story. OVMF VMs can not be snapsotted using
'virsh snapshot' as they have "pflash" device which is configured as
"raw" image. There was a discussion in the past about that.
Good
On 12/01/2016 15:16, Kevin Wolf wrote:
>> Thus we should avoid selection of "pflash" drives for VM state saving.
>>
>> For now "pflash" is read-write raw image as it configured by libvirt.
>> Thus there are no such images in the field and we could safely disable
>> ability to save state to those
Am 12.01.2016 um 07:03 hat Denis V. Lunev geschrieben:
> There is a long-long story. OVMF VMs can not be snapsotted using
> 'virsh snapshot' as they have "pflash" device which is configured as
> "raw" image. There was a discussion in the past about that.
>
> Good description has been provided on t
There is a long-long story. OVMF VMs can not be snapsotted using
'virsh snapshot' as they have "pflash" device which is configured as
"raw" image. There was a discussion in the past about that.
Good description has been provided on topic by Laszlo Ersek, see below:
"It is true that a pflash drive
24 matches
Mail list logo
