search for: snap1

Hi (Eric?), A couple of questions while using the 'virsh blockpull' Summary: 1] Created snapshots this way: base<-snap1<-snap2<-snap3 (online, external snapshot --disk-only) 2] I did a 'virsh blockpull' from snap2 into snap3 3] Next, did another 'virsh blockpull' from snap1 into snap3 - Here, 'qemu-img info /path/to/snap3' shows its backing file correctly as snap1. But not 'virsh...

Hi, I have a server, snap1 10.8.5.10, that runs samba, and have users created by using useradd (but not added them to snap1's smbpasswd). I'd like for users on our primary samba server, archives1 10.8.5.2, to be able to type in \\snap1\username in windows and have the snap1 server take them to their home direct...

Versions -------- (Libvirt locally built from a recent git commit -ec7b922): $ rpm -q libvirt-daemon-kvm qemu-system-x86 libvirt-daemon-kvm-1.2.6-1.fc20.x86_64 qemu-system-x86-2.0.0-1.fc21.x86_64 Test ---- [All images are qcow2 files.] We have this simple chain: base <- snap1 Let's quickly examine the contents of 'base' and 'snap1' images: 'base' has just a single file: foo $ guestfish --ro -a base.qcow2 [. . .] ><fs> ls / ><fs> run ><fs> mount /dev/sda1 / ><fs> ls / foo...

...ed up via conventional backup systems. But the issue is first deleting the snapshot and my understanding of what its saying. So here is some basic info: # virsh snapshot-list host1 Name Creation Time State ------------------------------------------------------------ snap1-host1 2014-01-19 16:59:10 +1100 shutoff # # virsh snapshot-info host1 --current Name: snap1-host1 Domain: host1 Current: yes State: shutoff Location: internal Parent: - Children: 0 Descendants: 0 Metadata: yes So I try and...

...ng RHEL 6.5 is a bit worrisome, and I also understand > that RHEL 6.x tends to not support internal snapshots. [ … ] >> # virsh snapshot-list host1 >> Name Creation Time State >> ------------------------------------------------------------ >> snap1-host1 2014-01-19 16:59:10 +1100 shutoff >> >> # >> # virsh snapshot-info host1 --current >> Name: snap1-host1 >> Domain: host1 >> Current: yes >> State: shutoff >> Location: internal > > So th...

On 07/02/2014 01:12 PM, Kashyap Chamarthy wrote: > We have this simple chain: > > base <- snap1 > > Let's quickly examine the contents of 'base' and 'snap1' images: > > Now, let's do a live blockcopy (with a '--finish' to graecully finish > the mirroring): > > $ virsh blockcopy --domain testvm2 vda \ > /export/dst/copy.qc...

...ms. But the issue is first deleting the snapshot and my understanding of what its saying. > > So here is some basic info: > > # virsh snapshot-list host1 > Name Creation Time State > ------------------------------------------------------------ > snap1-host1 2014-01-19 16:59:10 +1100 shutoff > > # > # virsh snapshot-info host1 --current > Name: snap1-host1 > Domain: host1 > Current: yes > State: shutoff > Location: internal So the fact that you created an internal snapsh...

Hello. The Changelog of qemu-2.0.0 mentioned "Live snapshot merging". Someone has an idea what could be ment by this? I'm asking because i'm still struggling with finding a reliable backup solution for running kvm machines. Blockcopy is my current solution. best regards Thomas

I am not sure if it''s a xen bug or lvm bug, or just my bad hardware, but here''s how to reproduce: /dev/vg0/centos1 is lvm block used by a domainU, it''s 8G in size. #lvcreate -L8192M -s -n snap1 vg0 #mount /dev/vg0/snap1 /mnt do some copying files here #umount /mnt #lvremove /dev/vg0/snap1 not removed! it says can''t allocated memory #xm mem-set 0 512 #lvremove /dev/vg0/snap1 now it removed successfully #lvcreate -L4096M -n fedora1 vg0 System lockup at this point. I have to log...

...d easier to read (alas, many web mailers these days lack settings for automatic wrap, so I end up whacking the Enter key for manual wrap when I'm forced to use a web mail interface for sending to a technical list) >>> # virsh snapshot-info host1 --current >>> Name: snap1-host1 >>> Domain: host1 >>> Current: yes >>> State: shutoff >>> Location: internal >> > # virsh snapshot-dumpxml host1 snap1-host1 > <domainsnapshot> > <name>snap1-host1</name> > <descripti...

...ce revert will cause the VM to become unresponsive. Nothing would show in console after revert. My host OS environment is CentOS release 6.4 (Final) libvirt-0.10.2-29 qemu-kvm-0.12.1.2-2.415 virsh # suspend combo01 Domain combo01 suspended   virsh # snapshot-create-as --domain combo01 combo01-snap1 "snap1-desc" --atomic Domain snapshot combo01-snap1 created virsh # snapshot-list combo01  Name                 Creation Time             State ------------------------------------------------------------  combo01-snap1        2013-12-14 20:57:41 +0000 paused virsh # snapshot-revert com...

...ing a snapshot. Please see example below: =============================================================== root &gt;#virsh snapshot-create-as --domain $DOMAIN $SNAP $DESC --disk-only --diskspec vda,snapshot=external,file=/var/lib/libvirt/images/${SNAPFILE} --atomic Domain snapshot ballyclient-1.snap1 created root &gt;#virsh dumpxml $DOMAIN | grep 'source file' root &gt;#virsh snapshot-delete --metadata $DOMAIN $SNAP Domain snapshot ballyclient-1.snap1 deleted root &gt;#find /var/lib/libvirt/images/ -type f -name $SNAPFILE -delete root &gt;#virsh dumpxml $DOMAIN |grep &...

...we want to snapshot for VM , to obtain VM incremental data，and use virsh blockcommit，qemu-img commit，qemu-img rebase to shorten snapshot chain. Details are as follows（when VM running state， we perform the following operations）: (1) the host machine control VM test virsh snapshot-create-as mix snap1 --diskspec vda,file=/tmp/mul/loop-mix-commit-rebase/snap1-mix.img --disk-only --atomic --quiesce virsh snapshot-create-as mix snap2 --diskspec vda,file=/tmp/mul/loop-mix-commit-rebase/snap2-mix.img --disk-only --atomic --quiesce virsh snapshot-create-as mix snap3 --diskspec vda,file=/tmp/mul/loop-m...

...quot; and then later re-merge the images together using "virsh blockpull". I am wondering how I can do a couple of other operations on the images while the VM is running. For example, VM1 is running from the snap3 image, with the following snapshot history (backing files): [orig] <-- [snap1] <-- [snap2] <-- [snap3] 1. Can I revert VM1 to use snap2 while it is live, or must it be shutdown? After shutting it down, is the best way to revert to snap2 to just edit the xml file and change the block device to point to snap2? Afterwards, I believe snap3 would become unusable and should...

Firstly I'd like to learn where a snapshot is stored once it has been made. I understand that the principle is that when changes occur in the VM, the difference is written to the snapshot, thus recording the differences between the date/time of the snapshot and the current value of the VM. Is that a correct assessment of the process? If that is indeed so, can I take regular snapshots and

Hello, I am working on my PhD thesis and it would be really helpfull if someone could advise me, whether can Virsh create snapshots of VMs using copy-on-write. Thanks for reply. Juraj

Hello, I have a running transient domain with a storage volume that utilizes a backing file (both QCOW2 format). I'd like to capture the disk and memory state of the domain preferably to external file(s) (which I understand is an 'external checkpoint'), so that other independent domains can be instantiated and effectively "resumed" from this point-in-time profile. My

Hi Libvirt, Does libvirt-python currently support the creation of external snapshots? I ran domain.snapshotCreateXML(xml) where xml is <domainsnapshot> <name>snap1</name> <description>Snapshot of OS install and updates</description> <disks> <disk name='vda'> <source file='/home/potato/libvirt/backups/test-snap1.qcow2'/> </disk> </disks> </domainsnapshot> And got t...

...-snap creation and btrfsck # -Ian! D. Allen - idallen@idallen.ca - www.idallen.com BTRFS=/mnt/sdc1 BTRFSDEV=/dev/sdc1 echo "Using $BTRFS $BTRFSDEV" set -x mkfs.btrfs -L BTRFStest $BTRFSDEV || exit $? mount -o noatime $BTRFSDEV $BTRFS || exit $? btrfs subvolume snapshot $BTRFS $BTRFS/snap1 umount $BTRFSDEV btrfsck $BTRFSDEV ---------- cut script here ---------------------------------------- ---------- script output here ------------------------------------- # ./btrfstest.sh Using /mnt/sdc1 /dev/sdc1 + mkfs.btrfs -L BTRFStest /dev/sdc1 WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL...

.... Libvirt does not yet support this action, but we are getting closer with our work on tracking the entire backing chain in domain XML. Current libvirt is able to support some chain shortening operations with older qemu: libvirt can do snapshot merging of any backing file (taking "base <- snap1 <- snap2" to "base <- snap2" by committing snap1 into base), as well as pulling content into the active layer (going from "base <- snap1 <- snap2" to "base <- snap2" by pulling snap1 into snap2). And as you mentioned, using blockcopy also allows li...