similar to: Recover snapshots from qcow images

On Tue, Aug 13, 2019 at 15:15:11 +0200, Petr Stodulka wrote: > 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 >

Hi, I'm using libvirt(1.0.0) with python, for managing virtual machines.. but while taking multiple snapshot domain is crashing... Snapshot XML ------------------------- <domainsnapshot> <name>snp1</name> <creationTime></creationTime> <description>Description</description> <state></state> <domain>

Martin, Actually domain doesn't crash, but it state got changed to pause, till the snapshot action got complete. Its a time consuming process. so here is my requirement. I want to take snapshot of a Running Domain on every 3 hours,( at a later point of time It should be possible to revert to the actual domain state when I took the snapshot), I'm using libvirt APIs python bindings, there

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

Hi all, I'm using ZFS on Linux block volumes as my VM storage and want to do live migrations between hypervisors. If I create ZFS snapshot of used volume on source host, send it do destination host (zfs send/recv) and then run live migration with VIR_MIGRATE_NON_SHARED_DISK flag, the migration works OK. But this procedure copies the whole disk twice which is a huge downside. The best

Hi Martin, in the meantime, I've found a solution which I consider at least acceptable: 1. create zfs snapshot of domain disk (/dev/zstore/test-volume) 2. save original XML domain definition 3. create snapshot in libvirt like this: virsh snapshot-create --xmlfile snap.xml --disk-only --no-metadata test-domain snap.xml: <domainsnapshot> <disks> <disk

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

On Wed, Jun 7, 2023 at 10:46 AM TTT <lists at telium.io> wrote: > I’ve reread the documentation a few times, and what isn’t clear is whether > I need an app=X parameter in the url. In other words, can I only get > events for a single named statis app? Or can I get events for the entire > Asterisk server? > > > > The command below (without app= parameter) results in

Hey When I want to take a snapshot for a Domain by using virDomainSnapshotCreateXML. The Error as below happen: libvir: QEMU error : Requested operation is not valid: Disk '/var/lib/libvirt/images/fedora-qcow.qcow2' does not support snapshotting The snapshot Configuration is : <domainsnapshot> <description>Snapshot of OS install and updates</description>

I’ve reread the documentation a few times, and what isn’t clear is whether I need an app=X parameter in the url. In other words, can I only get events for a single named statis app? Or can I get events for the entire Asterisk server? The command below (without app= parameter) results in no events being shown, but no error either. Thanks Brian (Ast newbie) From: asterisk-users

For many months now we have been trying to create a file-backed qcow image with the qcow-create code. Each time we try to back a file with a qcow, it screams: *** buffer overflow detected ***: qcow-create terminated Below is the output from two different attempts and information about qcow-create. Any ideas/thoughts/help you can offer? Thank you for your help! -Eric [root@trogdor ~]#

Hi, Trying to understand the current state of affairs with QCOW support in Xen with the blktap driver. It''s been made clear that a deviation from QEMU''s implementation of QCOW has occurred and that the QCOW files used in Xen must be created with the associated Xen tools only (e.g. qcow-create) and that images between QEMU and Xen are not interchangeable. My first question is

Hi, I want to ask if anyone of you is familiar with QCOW and has used this with xen? I''ve googled a bit about and could''nt really find out if it''s a good choice or not. Has anyone experience with usage in xen and can say something about performance and snapshot usability? Thanks in advance, Alex _______________________________________________ Xen-users mailing

All, is it possible to create a new KVM machine from an existing qcow (v3) image with snapshots? snapshot-list doesn't show them, when using virt-manager 1:1.5.1-0ubuntu1.1 to create the machine. * t-ad5.img: QEMU QCOW Image (v3), 42949672960 bytes chris@cd:/data/md0$ qemu-img snapshot -l t-ad5.img Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1

Hello, This is a second post, with a trial which is different from the first one , in order to solve my blcok-attach problem. I tried the following two actions, according to the blktap readme: qcow-create 1000 qcowFile.img Creating file size 1048576000 Created cksum: 1813725440 then xm block-attach 0 tap:qcow:qcowFile.img /dev/xvda1 w 0 I see in the /var/log/xen/xend.log: [2007-03-13

I have a qcow file It shows correct size on one server Fdisk -l w.qcow 70 GB On the other server Fdisk w.qcow 0 MB stupid

Hi, i would like to use qcow2-sparse-images which point to a backup-file. After reading this: http://wiki.xensource.com/xenwiki/DmUserspace i figured out that this feature seems to be unsupported by the ubuntu 8.04 LTS kernel and xen-3.2.1. Is this a ubuntu-specific problem, or is it solved in Suse, Red Hat, XenSource, whatever? When i try to block-attach it, xm displays no error, but the

I have been messing with QCOW on Xen and I''ve come to the conclusion that nobody actually uses it otherwise it would work. Has anyone gotten QCOW2 and Xen to work reliably? I have 40 PV VMs that are identical (initially) and would like to move from separate disk images to one base image sitting in a ramdisk and the COW images hosted on an iSCSI storage device. The VMs would boot off the