similar to: Re: [Qemu-devel] About VM fork in QEMU

On 10/28/2013 12:12 PM, Xinyang Ge wrote: >>> That's odd, because we have supported --live since 1.0.5. Are you sure >>> you are running the right libvirtd version and not just reporting the >>> version of your virsh? >> >> You are right. I am running an old libvirtd but with a new virsh. It >> works now! Thank you so much! > > Another

[dropping qemu-devel] On 10/28/2013 11:30 AM, Xinyang Ge wrote: >> virsh snapshot-create-as $dom $name --live --memspec /path/to/memoryfile > > I have tried this command on libvirt v1.1.3 and it returns "error: > invalid argument: qemuDomainSnapshotCreateXML: unsupported flags > (0x100)". Looks like --live is not supported yet. Could you let us > know which version

> That's odd, because we have supported --live since 1.0.5. Are you sure > you are running the right libvirtd version and not just reporting the > version of your virsh? You are right. I am running an old libvirtd but with a new virsh. It works now! Thank you so much! Xinyang -- Xinyang GE Department of Computer Science & Engineering The Pennsylvania State University

>> That's odd, because we have supported --live since 1.0.5. Are you sure >> you are running the right libvirtd version and not just reporting the >> version of your virsh? > > You are right. I am running an old libvirtd but with a new virsh. It > works now! Thank you so much! Another question is about snapshot reversion. I am trying to use "virsh

----- Original Message ----- > From: "Eric Blake" <eblake@redhat.com> To: "Andrew Martin" > <amartin@xes-inc.com>, libvirt-users@redhat.com Sent: Thursday, May 22, 2014 > 5:44:54 PM Subject: Re: [libvirt-users] Live snapshots of a single block > device > > On 05/22/2014 04:31 PM, Andrew Martin wrote: > > Hello, > > > > [Can you

> >> --live only makes sense when mixed with memory snapshots (with --memspec); > >> but > >> as you are doing a --disk-only snapshot, it doesn't help (I'm not sure if > >> it > >> will error out as mutually exclusive or just be silently ignored, > >> without reading the code). > > I'm using this code in a script for creating

Hi all, I was trying to take live snapshot of VMs, but I got the following error: [root@localhost ~]# virsh snapshot-create-as 1 test desc --live --memspec file=mem.bak,snapshot=external --diskspec vda,snapshot=external,file=/root/root.bak.qcow2 error: Operation not supported: live disk snapshot not supported with this QEMU binary I upgraded my qemu-kvm 0.12.1 to qemu 1.2, the error still

Hi Kashyap, Thanks for your answer! Unfortunately my use case requires cloning the exact memory state, so I won't be able to use virt-sysprep. But the snapshot command looks like something I could use. Could you suggest how to proceed and create/start a new vm from that snapshot? Thanks, Michael On Tue, Apr 12, 2016 at 2:37 PM, Kashyap Chamarthy <kchamart@redhat.com> wrote: > On

On 05/23/2014 08:41 AM, Andrew Martin wrote: >> >> Any reason you aren't upgrading to newer versions? Although these seem >> sufficient for what you are trying. > The VM hosts I'm using all run Ubuntu 12.04 and I haven't had time to backport > and test newer versions yet. I've published the latest versions I built in this > PPA:

Hi, I have a win10 guest on a fedora32 system and have some questions as I explore using external snapshots as a form of backup in case of a Windows failure (as in, it won't boot or is completely irrecoverable) as well as revision control (to be able to rollback changes after a failed app install, etc). The first hit on Google for external snapshots involves a RHEL7 document that talks

On Thu, Mar 10, 2016 at 9:14 AM, Hans de Goede <hdegoede at redhat.com> wrote: > Extend the MEMORY file support to differentiate between global, local > and shared memory, as well as "input" memory. > > "MEMORY[x], INPUT" is intended to access OpenCL kernel parameters, a > special memory type is added for this, since the actual storage of these > (e.g.

Hi, Here are patches which implement the support for OpenCL kernel input parameters we discussed. They also add the tgsi parsing bits for adding support for global / local mem, but no implementation yet. Regards, Hans

Hello, I am working on a script to automatically create live snapshots of running VMs using qemu-kvm 1.4.0 and libvirt 1.0.2. If a VM has multiple disks, I'd like to back them up individually with separate calls to snapshot-create-as, so I can more easily manage the disk images. The code I have now is essentially as follows: virsh snapshot-create-as --domain "vmname" --name

When support for decl.Atomic and .Shared was added, tgsi_build_declaration was not updated to propagate these properly. Signed-off-by: Hans de Goede <hdegoede at redhat.com> Reviewed-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Changes in v2: -Add Reviewed-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/auxiliary/tgsi/tgsi_build.c | 6 ++++++ 1 file changed, 6

Hi, My use case involves creating duplicates of saved virtual machines. Tried with virt-manager and with virsh but so far it seems like this case is not supported by these tools. Does anyone know how I could achieve the above? Thanks, Michael

Thanks for your answer, I am trying to make a snapshot of whole virtual machine (disk, CPU state, memory). But I need to make this snapshot in matter of seconds. I have already try to create snapshot of disk, which is not problem. I use qcow2 format, and create new disk image using original disk image as backing file. But still I am not able to assign state of vm with new disk. I have found

On 03/16/2016 10:23 AM, Hans de Goede wrote: > Commit c3083c7082 ("nv50/ir: add support for BUFFER accesses") disabled / > commented out some of the old resource handling code, but not all of it. > > Effectively all of it is dead already, if we ever enter the old code > paths in handeLOAD / handleSTORE / handleATOM we will get an exception > due to trying to access the

Commit c3083c7082 ("nv50/ir: add support for BUFFER accesses") disabled / commented out some of the old resource handling code, but not all of it. Effectively all of it is dead already, if we ever enter the old code paths in handeLOAD / handleSTORE / handleATOM we will get an exception due to trying to access the now always zero-sized resources vector. Disable all the dead code.

what the difference between ` virsh save ` and `virsh snapshot`? are they all used for backup for vm?have any details articles to introduce vm bakcup or image bakcup with libvirt? thanks in advance. liuzhijun -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20121112/931d27a2/attachment.htm>

Everyone, I am trying to create external snapshots of a kvm guest machine and have not been able to do so. In accordance with : https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-troubleshooting-workaround_for_creating_external_snapshots_with_libvirt I have used the command line : snapshot-create-as --diskspec