search for: snap2

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 snapshot-l...

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

...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 be deleted? 2...

...oes 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 libvirt to piv...

Please can someone take a look at the attached file which shows the output on my machine of zfs list -r -t filesystem,snapshot -o space rpool/export/home/matt The USEDDS figure of ~2GB is what I would expect, and is the same figure reported by the Disk Usage Analyzer. Where is the remaining 13.8GB USEDSNAP figure coming from? If I total up the list of zfs-auto snapshots it adds up to about 4.8GB,

...apshot 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-mix-commit-rebase/snap3-mix.img --disk-only --atomic --quiesce virsh snapshot-create-as mix snap4 --diskspec vda,file=/tmp/mul/loop-m...

Hi all, I have a kvm virtual machine running (qemu version 2.0), and I had took several external snapshots of the disk( using "virsh snapshot-create-as"). Now, the existed disk files relationship look like: base <- snap1 <-snap2 <- current using disk file. Now I want to remove snap1 and snap2, and let current disk using the base image file as back file directly. Unfortunately, for some reason, I can not shutdown the vm, and exectue the "virsh blockpull" command. Can I execute the "virsh blockpull" wh...

...running virsh # domblklist vm-01 Target Source ------------------------------------------------ vda /home/ubuntu/vm-01.img hda /dev/sr0 snapshot-create-as --domain vm-01 snap1 --diskspec vda,file=/var/lib/libvirt/sn1.qcow2 --disk-only --atomic snapshot-create-as --domain vm-01 snap2 --diskspec vda,file=/var/lib/libvirt/sn2.qcow2 --disk-only --atomic virsh #snapshot-list vm-01 ------------------------------------------------------------ snap1 2015-12-07 11:51:51 -0800 disk-snapshot snap2 2015-12-07 11:52:28 -0800 disk-snapshot virsh # snapshot...

Hi everyone! I use the libvirt(version: 1.2.2) and QEMU(version: 2.2.1) to test qemu snapshot features: I tried virsh blockcommit when VM offline, the virsh blockcommit failed: the error messase as below: error: Requested operation is not valid: domain is not running when I start the VM, the virsh blockcommit work fine! my question is：we need

Am 10.06.13 10:40, schrieb Kashyap Chamarthy: > On 06/10/2013 01:20 PM, Thomas Stein wrote: >> Am 10.06.13 09:07, schrieb Kashyap Chamarthy: >>> On 06/09/2013 02:46 PM, Thomas Stein wrote: >>>> Hello. >>>> >>>> I just tried the following: >>>> >>>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml

What ''verbose information'' is reported by the "zfs send -v <snapshot>" contain? Also on Solaris 10u6 I don''t get any output at all - is this a bug? Regards, Nick -- This message posted from opensolaris.org

...are CIFS and remove iSCSI targets. For the iSCSI targets, seems like I can''t re-use them for Comstar and the reservations aren''t carried over for block devices? I may just destroy them before hand. Nothing important on them. 4. Create new snapshots -> zfs snapshot -r pool1 at snap2 5. Send incremental stream -> zfs send -Ri snap1 pool1 at snap2 | zfs receive -F -d test2 Repeat steps 4 and 5 as necessary. 6. Offline pool1... if I don''t plan on destroying it right away. Other than zfs list, is there anything I should check to make sure I received all the data to th...

All, Using Centos 6.4 with provided libvirt: [root@node1 ~]# rpm -q libvirt libvirt-1.0.1-2.el6.x86_64 Assume a VM with one or more live snapshots. In virsh the VM snapshots can be listed. With virsh: - Stop and undefine this VM. - Then define (and start) this VM. The new VM does not have the list of snapshots. Is there a way with virsh to rebuild the metadata such that

All, I have a service that takes new live KVM snapshots Si regularly, keeps a fixed number N (Si ,..,Si-N+1), and therefore needs to delete Si-N in this cycle. Until libvirt includes support for this capability that is said to be available in qemu, what is a safe workflow to delete old live KVM snapshots w/o losing data. Do I need to pause/shut down the VM? The development environment is

Morning, I have a KVM guest running Win 2012 with MS SQL 2012. In order to provide a quick method of restoring the service should the live server die, we've decided to clone it to a preserved state. Ideally, this clone should also be kept up to date and cloning should be done on a regular basis. Is there any reason not to do unattended cloning? As in, when I leave on a Friday afternoon,

Hello how i can use rsync whith mkdir -p for nackup dirs ? when i use rsync / /backup/month/day i need automatic creation month and day dirs. mkdir -p can do that, but rsync can't

On 08/06/2014 06:04 AM, chenyanqiu@keytonecloud.com wrote: > Hi all, [please configure your mailer to wrap long lines] > ...Now I want to remove snap1 and snap2, and let current disk using the base image file as back file directly. Unfortunately, for some reason, I can not shutdown the vm, and exectue the "virsh blockpull" command. Can I execute the "virsh blockpull" while the vm is power on, and the application in the vm is not affecte...

Hello fellas, Firstly, I would like to apologize for the post being long, but I would appreciate if someone with a good knowledge of the subject gave his opinion. I am working on a backup solution for a series of old and very specialized host computers in aviation industry. I need to do monthly backups of one or two logical volumes (non-OS) on each of the computers and keep the last 12 monthly

...ng on generating a diff between file system snapshots using the send receive code. The output of our utility looks like this- (I''ve tested it on a small subvol with minimal changes just to give an idea) root@nafisa-M-6319:/mnt/btrfs# btrfs sub diff -p /mnt/btrfs/snap1 /mnt/btrfs/snap2 Directory Deleted path = dir5 File Deleted path = 1.c File Written path = 3.c data written : "3.c was changed" File Moved path from = 4.c path to = dir1/4.c new files created = 0 new dir created = 0 files deleted = 1 changed links = 1 dirs deleted = 1 files written = 1 We w...

OK, so this may be a little off-topic, but here goes: The reason I switched to OpenSolaris was primarily to take advantage of ZFS''s features when storing my digital imaging collection. I switched from a pretty stock Linux setup, but it left me at one disadvantage. I had been using inotify under Linux to trigger a series of Ruby scripts that would do all the basic ingestion/setup for