[pve-devel] create snapshots

[Dietmar Maurer]

I just upload a fix - please can you test again?

https://git.proxmox.com/?p=pve-qemu-kvm.git;a=commitdiff;h=e3a988892faa026b88b8ceb61897b7a0753c76a9

> -----Original Message-----
> From: Alexandre DERUMIER [mailto:aderumier at odiso.com]
> Sent: Mittwoch, 05. September 2012 09:17
> To: Dietmar Maurer
> Cc: pve-devel at pve.proxmox.com
> Subject: Re: [pve-devel] create snapshots
> 
> >>qm start -stateuri <statefile>
> >>
> 
> # qm start 115 -stateuri /tmp/snap1
> cat: write error: Broken pipe
> 
> 
> same with --incoming "exec:cat /tmp/snap1"
> 
> 
> is it broken in current qemu? (I never try it before)
> 
> 
> ----- Mail original -----
> 
> De: "Alexandre DERUMIER" <aderumier at odiso.com>
> À: "Dietmar Maurer" <dietmar at proxmox.com>
> Cc: pve-devel at pve.proxmox.com
> Envoyé: Mercredi 5 Septembre 2012 07:58:50
> Objet: Re: [pve-devel] create snapshots
> 
> 
> >>The idea is to save the state into an external file. That will work for all
> storage
> >>types.
> Great :) so it'll work for rbd or nexenta :)
> 
> 
> >>Sorry, I do not understand what you mean?
> When I have done tests with savevm, the qmp socket timeout each time
> during the vmstate save.
> It's also take more time to take than using your vmstate file. (maybe because
> savevm write the state in the main volume and need to do space inside.).
> 
> >>qm start -stateuri <statefile>
> Oh, yes, it should works. (like for migratation with statefile). I'll test that this
> morning.
> 
> 
> ----- Mail original -----
> 
> De: "Dietmar Maurer" <dietmar at proxmox.com>
> À: "Alexandre DERUMIER" <aderumier at odiso.com>
> Cc: pve-devel at pve.proxmox.com
> Envoyé: Mercredi 5 Septembre 2012 07:50:55
> Objet: RE: [pve-devel] create snapshots
> 
> > what is the statefile argument ?
> > I thinked that the state was saved inside the (first) disk. (so vmstate is
> > snapshoted and we can rollback it easily) Or it's for doing some tests ?
> 
> The idea is to save the state into an external file. That will work for all storage
> types.
> 
> > I don't know if the vmstate is ok, but it seem faster to take than using the
> > savevm command. (and also qmp socket don't timeout like with savevm)
> 
> Sorry, I do not understand what you mean?
> 
> > When I tried to use loadvm, it complain that state is not available.(So we
> > need to hack loadvm too to use external statefile)
> 
> # qm start -stateuri <statefile>
> 
> should do the trick - but I have not tested that.
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel