similar to: Inspection of disk snapshots

On Mon, Mar 23, 2015 at 10:41:01PM +0000, Richard W.M. Jones wrote: > On Mon, Mar 23, 2015 at 04:34:21PM +0200, NoxDaFox wrote: > > Greetings, > > > > I have the following typical scenario: given one or more qcow2 base images > > I clone them with COW and start the VMs. > > > > At a certain point I'd like to inspect them in order to see their evolution

I was sure I was doing something wrong as I'm not yet fully aware of QCOW2 snapshot feature and how it interacts with libguestfs. I'll try to explain better the scenario: I have several hosts running lots of VMs which are generated from few base images, say A, B, C the base images (backing file) and A1, A2, A*, B1, B2, B* clones on top of which the newly spawned VMs are running. I need

On Mon, Mar 23, 2015 at 04:34:21PM +0200, NoxDaFox wrote: > Greetings, > > I have the following typical scenario: given one or more qcow2 base images > I clone them with COW and start the VMs. > > At a certain point I'd like to inspect them in order to see their evolution > compared to the known base images. To do so I was thinking about taking a > disk snapshot of

On Wed, Mar 25, 2015 at 07:38:03PM +0100, Kashyap Chamarthy wrote: > On Mon, Mar 23, 2015 at 10:43:30PM +0000, Richard W.M. Jones wrote: > > [. . .] > > > > This makes a copy of the whole disk image. It's also not a consistent > > > (point in time) copy. > > > > Oh I see that you're copying the _snapshot_ that you created with > >

On Mon, Mar 23, 2015 at 10:43:30PM +0000, Richard W.M. Jones wrote: [. . .] > > This makes a copy of the whole disk image. It's also not a consistent > > (point in time) copy. > > Oh I see that you're copying the _snapshot_ that you created with > libvirt; it's not a whole disk copy. There's still not any point in > doing this, and what I said below

On Fri, Mar 27, 2015 at 12:31:41PM +0000, Richard W.M. Jones wrote: > On Fri, Mar 27, 2015 at 12:15:34PM +0000, Stefan Hajnoczi wrote: > > On Thu, Mar 26, 2015 at 12:02:27AM +0100, Kashyap Chamarthy wrote: > > > So, something like? > > > > > > . . . > > > { 'execute': 'drive-backup', 'arguments': > > > {

On Fri, Mar 27, 2015 at 03:21:25PM +0000, Stefan Hajnoczi wrote: > On Fri, Mar 27, 2015 at 12:31:41PM +0000, Richard W.M. Jones wrote: > > On Fri, Mar 27, 2015 at 12:15:34PM +0000, Stefan Hajnoczi wrote: > > > On Thu, Mar 26, 2015 at 12:02:27AM +0100, Kashyap Chamarthy wrote: > > > > So, something like? > > > > > > > > . . . > > >

On Thu, Mar 26, 2015 at 12:02:27AM +0100, Kashyap Chamarthy wrote: > [Added Stefan Hajnoczi, who wrote the 'drive-backup' QMP command and > Eric Blake.] > > On Wed, Mar 25, 2015 at 07:41:23PM +0000, Richard W.M. Jones wrote: > > On Wed, Mar 25, 2015 at 07:38:03PM +0100, Kashyap Chamarthy wrote: > > > On Mon, Mar 23, 2015 at 10:43:30PM +0000, Richard W.M. Jones

On Fri, Mar 27, 2015 at 12:15:34PM +0000, Stefan Hajnoczi wrote: > On Thu, Mar 26, 2015 at 12:02:27AM +0100, Kashyap Chamarthy wrote: > > So, something like? > > > > . . . > > { 'execute': 'drive-backup', 'arguments': > > { 'device': 'drive-virtio-disk1', 'sync': 'full', 'target': >

A lot of code runs 'qemu-img create' or 'truncate' to create blank disk images. In the past I resisted adding an API to do this, since it essentially duplicates what you can already do using other tools (ie. qemu-img). However this does simplify calling code quite a lot since qemu-img is somewhat error-prone to use (eg: don't try to create a disk called "foo:bar")

Hi, this series cleans up the Python sources, either static or generated, including also tests, to make them PEP 8 compliant; see https://www.python.org/dev/peps/pep-0008/ and tools like pep8. Almost all the issues reported by pep8 are fixed, reducing the issues from 3818 to 7. The changes should have no effect on the actual code, while it will help Python users with consistency with other

2015-05-28 10:40 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > On Thu, May 28, 2015 at 10:33:48AM +0300, NoxDaFox wrote: > > To create the snapshots I'm using the libvirt command snapshotCreateXML > > with no flag set. Does libvirt support consistent snapshotting or shall I > > rely on QEMU backup new feature only? > > According to:

[Added Stefan Hajnoczi, who wrote the 'drive-backup' QMP command and Eric Blake.] On Wed, Mar 25, 2015 at 07:41:23PM +0000, Richard W.M. Jones wrote: > On Wed, Mar 25, 2015 at 07:38:03PM +0100, Kashyap Chamarthy wrote: > > On Mon, Mar 23, 2015 at 10:43:30PM +0000, Richard W.M. Jones wrote: [. . .] > > > > If you want lightweight, consistent, point-in-time snapshots

2015-05-28 10:10 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > On Thu, May 28, 2015 at 09:48:41AM +0300, NoxDaFox wrote: > > 2015-05-27 15:21 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > > > > > On Wed, May 27, 2015 at 09:38:38AM +0300, NoxDaFox wrote: > > > > * RuntimeError: file receive cancelled by daemon - On r = > > >

On Tue, Mar 24, 2015 at 10:54:05AM +0200, NoxDaFox wrote: > I was sure I was doing something wrong as I'm not yet fully aware of QCOW2 > snapshot feature and how it interacts with libguestfs. > > I'll try to explain better the scenario: > > I have several hosts running lots of VMs which are generated from few base > images, say A, B, C the base images (backing file)

Greetings, I am developing a platform for test and debug use. The typical scenario I want to realize is the following: I run a .qcow2 image via QEMU-KVM, the running OS is not relevant. I want to take several snapshots of both Disk and RAM status; same file, separate files doesn't matter. I just need a way to have consistent information about them (better with XML description) and the data

On Fri, Mar 14, 2014 at 12:47:08PM +0500, Shumaila Naeem wrote: > Also i can't use the newest version of libguestfs as im on a production > system and i could not use the newest version due to some limitations. You can use the new version without installing it. However you would need to be able to install a compiler and other dependencies, which may not be possible on a production

Hello everybody, I would like to be able to spawn several domains from a given snapshot. Here's a possible scenario: - I start from disk image A.qcow2. - I made some changes to A and I take different snapshots: 1 - 2 - 3 - While A is still running I would like to run domains B and C from snapshot 2 I don't want to revert a domain, I want to create new ones. The original should be

Hi guys, I had to move to the new laptop week ago and I screw migration of my virtual machines. I recovered my virtual machines on the new laptop (virsh define) using the backed up xml files, but I am missing any file with metadata about snapshots. The original storage is cleaned so I cannot take these files anymore. Using qemu-info I can see my snapshots inside the qcow images, but libvirt

2015-05-28 11:10 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > On Thu, May 28, 2015 at 10:57:51AM +0300, NoxDaFox wrote: > > 2015-05-28 10:40 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > > > > > On Thu, May 28, 2015 at 10:33:48AM +0300, NoxDaFox wrote: > > > > To create the snapshots I'm using the libvirt command >