search for: keystonenap

...cle https://kashyapc.fedorapeople.org/virt/lc-2012/snapshots-handout.html. According to the article it deletes the tracking metadata by libvirt. You can physically remove the snapshot now that there is no tracking stream data by libvirt On Wed, Aug 23, 2017 at 4:56 PM, Doug Hughes <doug.hughes@keystonenap.com> wrote: > THat did it! Can you esplain what was going on and how that fixed it? > Thanks > > On 8/23/2017 10:50 AM, Sakhi Hadebe wrote: > > Hi, > > Can you try this command: > virsh snapshot-delete serv1r2 snap --metadata > > > > > On Wed, Aug 23, 2...

On Fri, Jun 30, 2017 at 10:41:25 -0400, doug.hughes@keystonenap.com wrote: > sorry about top post, tablet mail client... > > brilliant! that did it! Any idea what happened to cause it to partially fail and get into this state? virsh blockcommit --pivot is actually 3 operations in sequence: 1) initiate the commit job 2) wait till it finishes 3) initia...

On Fri, Jun 30, 2017 at 09:23:29 -0400, Doug Hughes wrote: > On Jun 30, 2017 6:22 AM, "Peter Krempa" <pkrempa@redhat.com> wrote: > > On Fri, Jun 30, 2017 at 12:05:47 +0200, Peter Krempa wrote: > > > On Thu, Jun 22, 2017 at 11:02:41 -0400, Doug Hughes wrote: [...] > file or directory > > $ virsh blockcommit --active --pivot fedora23 vda > > >

...17 [root@vm1 ~]# ls -l /var/lib/libvirt/images/serv1r2.qcow2 -rw-r--r--. 1 qemu qemu 54200696832 Jun 30 10:40 /var/lib/libvirt/images/serv1r2.qcow2 [root@vm1 ~]# Sent from my android device. -----Original Message----- From: Peter Krempa <pkrempa@redhat.com> To: Doug Hughes <doug.hughes@keystonenap.com> Cc: libvirt-users@redhat.com Sent: Fri, 30 Jun 2017 9:38 Subject: Re: [libvirt-users] recovering from deleted snapshot On Fri, Jun 30, 2017 at 09:23:29 -0400, Doug Hughes wrote: > On Jun 30, 2017 6:22 AM, "Peter Krempa" <pkrempa@redhat.com> wrote: > > On Fri, Jun 3...

Hi, Can you try this command: virsh snapshot-delete serv1r2 snap --metadata On Wed, Aug 23, 2017 at 4:41 PM, Doug Hughes <doug.hughes@keystonenap.com> wrote: > I'm not sure how this snapshot got created, but, I cannot delete it, and > its presence prevents me from creating other snapshots. I don't know if it > was created by a command gone amok or something else. > > # virsh snapshot-list serv1r2 > Name...

Will snapshot-revert restore the processor and memory state of the VM as it was at the time of the snapshot? -- Gary Jackson On 9/19/17, 11:10 AM, "libvirt-users-bounces@redhat.com on behalf of Doug Hughes" <libvirt-users-bounces@redhat.com on behalf of doug.hughes@keystonenap.com> wrote: On 9/19/2017 9:56 AM, Martin Kletzander wrote: > On Tue, Sep 19, 2017 at 01:28:45PM +0000, Jackson, Gary L. wrote: >> >> I would like to make a snapshot of a running VM, let it continue to run >> after the shapshot, and then at some...

...snapshots. Is there any way to make the snapshot and restore faster, like maybe by a decimal order of magnitude? For example, will PXE booting the VM and running it entirely off of a RAM disk and also using a RAM disk for the backing store help? -- Gary Jackson From: Doug Hughes <doug.hughes@keystonenap.com> Date: Tuesday, September 19, 2017 at 11:25 AM To: "Jackson, Gary L." <Gary.Jackson@jhuapl.edu>, "libvirt-users@redhat.com" <libvirt-users@redhat.com> Subject: Re: [libvirt-users] Rollback to running VM According to this page: https://wiki.libvirt.org/page/Sn...

On 9/19/2017 9:56 AM, Martin Kletzander wrote: > On Tue, Sep 19, 2017 at 01:28:45PM +0000, Jackson, Gary L. wrote: >> >> I would like to make a snapshot of a running VM, let it continue to run >> after the shapshot, and then at some later time roll back the VM to >> that previous running state. Can I do that with libvirt? If so, how? I >> understand that this will

On Jun 30, 2017 6:22 AM, "Peter Krempa" <pkrempa@redhat.com> wrote: > > On Fri, Jun 30, 2017 at 12:05:47 +0200, Peter Krempa wrote: > > On Thu, Jun 22, 2017 at 11:02:41 -0400, Doug Hughes wrote: > > > > [...] > > > > > virsh blockcommit $vm $DISK --active --pivot > > > > > > Normally this works fine, though something went

There are several possibilities depending upon what you mean. Personally, I have a zpool on the host that I carve off individual zfs filesystems that each guest uses. I put one qcow2 or raw image per zfs filesystem. I do this for backup and replication purposes. Then I have a recursive replication from this host to another so that I can boot up any of the VMs should the primary VM server goes

I have an automatic process setup. It's still pretty new and obviously in need of better error handling because now I find myself in a bad state. I run snapshot-create-as across all my vms, then do zfs replication to the target backup system, then blockcommit everything. virsh snapshot-create-as --domain $vm snap --diskspec $DISK,file=$VMPREFIX/"$vm"-snap.qcow2 --disk-only --atomic