On 07/30/10 - 10:43:01AM, Luiz Capitulino wrote:
> On Fri, 30 Jul 2010 11:34:57 +0200
> Markus Armbruster wrote:
>
> > Miguel Di Ciurcio Filho writes:
> >
> > > This patch address two issues.
> > >
> > > 1) When savevm is run using an previously saved snapshot id or name, it
> > > will
> > > d
On Fri, 30 Jul 2010 16:43:09 +0200
Markus Armbruster wrote:
> Luiz Capitulino writes:
>
> > On Fri, 30 Jul 2010 11:34:57 +0200
> > Markus Armbruster wrote:
> >
> >> Miguel Di Ciurcio Filho writes:
> >>
> >> > This patch address two issues.
> >> >
> >> > 1) When savevm is run using an previou
Luiz Capitulino writes:
> On Fri, 30 Jul 2010 11:34:57 +0200
> Markus Armbruster wrote:
>
>> Miguel Di Ciurcio Filho writes:
>>
>> > This patch address two issues.
>> >
>> > 1) When savevm is run using an previously saved snapshot id or name, it
>> > will
>> > delete the original and create a
On Fri, 30 Jul 2010 11:34:57 +0200
Markus Armbruster wrote:
> Miguel Di Ciurcio Filho writes:
>
> > This patch address two issues.
> >
> > 1) When savevm is run using an previously saved snapshot id or name, it will
> > delete the original and create a new one, using the same id and name and no
Miguel Di Ciurcio Filho writes:
> This patch address two issues.
>
> 1) When savevm is run using an previously saved snapshot id or name, it will
> delete the original and create a new one, using the same id and name and not
> prompting the user of what just happened.
>
> This behaviour is not go
This patch address two issues.
1) When savevm is run using an previously saved snapshot id or name, it will
delete the original and create a new one, using the same id and name and not
prompting the user of what just happened.
This behaviour is not good, IMHO.
We add a '-f' parameter to savevm,
