similar to: Live Disk Snapshot Not Supported

Hi, The package installed is qemu-kvm-1.5.3-60.el7_0.10.x86_64 on CentOS 7. I have upgraded my libvirt and qemu also, still i am getting the same error ( Operation not supported: live disk snapshot not supported with this QEMU binary ) # virsh version Compiled against library: libvirt 1.2.10 Using library: libvirt 1.2.10 Using API: QEMU 1.2.10 Running hypervisor: QEMU 2.0.0 On Mon, Nov 24,

Hi everybody, I am having a problem with the use of domfsfreeze command. It is freezing all the filesystems present on the domain, instead of freezing just the mountpoints provided. I am issuing the command-- # virsh domfsfreeze <domain> --mountpoint <mountpoint> Output was-- Froze 3 filesystem(s) I want to freeze a particular mount point on the VM, so that i can take a

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

Hello Fairly new to libvirt. I’m hoping to both solve a problem with this question as well as learn more detail about how libvirt works. Using RHEL 6.4 and libvirt version is 0.10.2 and qemu-img version is 0.12.1.2 Using virt-manager I created a VM. Nothing unusual as far as I can see. I then added a disk. So I have a second virtio based volume which the guest then mounts as a separate

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

Hello Thanks heaps for your suggestions. responses inline. On 10 Apr 2014, at 10:34 pm, Eric Blake <eblake@rehost1hat.com> wrote: > > [ … ] > [Can you convince your mailer to wrap long lines? It makes it easier > for other readers] I’ll try and keep the lines short. I don’t see any obvious setting to change the wrap. >> >> Using RHEL 6.4 and libvirt version

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

From: Anand Jain <anand.jain@oracle.com> (This patch is for the review/test not yet for the integration). Here is an implementation of the feature to add label to the subvolume and snapshots. Which would help sysadmin to better manager the subvol and snapshots. This can be done in two ways, one - using attr which is user land only changes but drawback is able to change the label

Eric Blake <eblake@...> writes: > > On 05/27/2012 06:39 PM, xingxing gao wrote: > > Hi,all,i am using libvirt to manage my vm,in these days i am testing > > the libvirt snapshot ,but meet some problem: > > > > the snapshot was created from this command: > > snapshot-create-as win7 --disk-only --diskspec > > vda,snapshot=external --diskspec

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:

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

Versions: $ rpm -q libvirt-daemon-kvm qemu-system-x86 libvirt-daemon-kvm-1.2.9-3.fc21.x86_64 qemu-system-x86-2.1.2-4.fc21.x86_64 When I attempt to revert to an internal snapshot: $ virsh snapshot-list node1 Name Creation Time State ------------------------------------------------------------ snap1 2014-06-03 14:07:28 -0400 running $

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

Does anyone know if load balancing and DNAT work well together? I know that load balancing and NAT do not, but what about a simple port forward? I can''t apply Julian Anastasov''s patches, because they don''t work with PPTP patches. :/ Anyhow, a simple: iptables -t nat -A PREROUTING -i eth0 -p tcp --dport xxx -j DNAT --to yyy:xxx iptables -I FORWARD -i eth0 -d yyy -p

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 directory on the snap1 server, but athenticate the users against

Hello all, I'm trying to create an online internal snapshot to work with Cuckoo Sandbox. I keep receiving this -22 error below on my Ubuntu system and I'm out of ideas, been at it for a while so any help is appreciated. root@cuckoo-sec:~# virsh snapshot-create-as cuckoo cuckoo-snap1 "Cuckoo Snapshot" error: operation failed: Error -22 while writing VM $ uname -a Linux

If I want to go back to a snapshot, what is the difference between snapshot-current and snapshot-revert? What happens to disk sectors of the current state when reverting to another snapshot? I'm using qemu qcow2.

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

Hi, Is it possible to freeze windows guests for a consistent storage level snapshot. I am using openstack icehouse on centos 6.6 Hypervisor: KVM Libvirt: 0.10.2 Qemu: 0.10.2 Guest OS: Windows 7 and Windows Server 2008 I was able to freeze Centos guests by issuing the command: virsh qemu-agent-command <guest_ID> '{"execute":"guest-fsfreeze-freeze"}' For CentOS

So I notice that some operations by libvirt such as creating a snapshot actually change the source of the active disk image for a domain without requiring a restart of the vm. How can this be achieved manually? There are instances where I am manipulating files with qemu-img or virsh commands and afterward need to change what file the vm is using as its disk. One example is when deleting a