search for: virdomainresume

...(virDomainFSFreeze) only works on a live guest. So > what you will have to do is: > > virDomainFSFreeze(vm1, ...) > virDomainFSFreeze(vm2, ...) > virDomainSuspend(vm1) > virDomainSuspend(vm2) > virDomainSnapshotCreateXML(vm1, ...) > virDomainSnapshotCreateXML(vm2, ...) > virDomainResume(vm1) > virDomainResume(vm2) > virDomainFSThaw(vm1, ...) > virDOmainFSThaw(vm2, ...) > I see, thanks. > > However, I honestly don't know why you think you need disk snapshots > from the same point in time across multiple VMs, though. you suggested that external di...

yes, I got your point, thanks very much Eric. If I want to take a distributed snapshot, which need pause all the VMs and then take snapshot, how can I control the pause for all the VMs? Is there only way that I turn to freeze/thaw functions? and freeze/thaw only for file systems, not for the whole guest, am I right? Thanks a lot! Best, Yuanzhen On Wed, Aug 6, 2014 at 11:35 AM, Eric Blake

...o freeze/thaw functions? Guest freeze/thaw (virDomainFSFreeze) only works on a live guest. So what you will have to do is: virDomainFSFreeze(vm1, ...) virDomainFSFreeze(vm2, ...) virDomainSuspend(vm1) virDomainSuspend(vm2) virDomainSnapshotCreateXML(vm1, ...) virDomainSnapshotCreateXML(vm2, ...) virDomainResume(vm1) virDomainResume(vm2) virDomainFSThaw(vm1, ...) virDOmainFSThaw(vm2, ...) However, I honestly don't know why you think you need disk snapshots from the same point in time across multiple VMs, though. Compare it to bare metal - how would you take a snapshot of multiple hosts? Either they...

...live guest. So >> what you will have to do is: >> >> virDomainFSFreeze(vm1, ...) >> virDomainFSFreeze(vm2, ...) >> virDomainSuspend(vm1) >> virDomainSuspend(vm2) >> virDomainSnapshotCreateXML(vm1, ...) >> virDomainSnapshotCreateXML(vm2, ...) >> virDomainResume(vm1) >> virDomainResume(vm2) >> virDomainFSThaw(vm1, ...) >> virDOmainFSThaw(vm2, ...) >> > > I see, thanks. > >> >> However, I honestly don't know why you think you need disk snapshots >> from the same point in time across multiple VMs,...

...ine 66, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in resume self._backend.resume() File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self) libvirt.libvirtError: internal error: unable to execute QEMU command 'cont': Resetting the Virtual Machine is required Ubuntu: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux libvirt: libvirtd (libvirt) 6.0.0 Thanks in a...

...}, + { name => "virDomainRestore", sig => "conn, string : unit" }, + { name => "virDomainCoreDump", sig => "dom, string, 0 : unit" }, + { name => "virDomainSuspend", sig => "dom : unit" }, + { name => "virDomainResume", sig => "dom : unit" }, + { name => "virDomainShutdown", sig => "dom : unit" }, + { name => "virDomainReboot", sig => "dom, 0 : unit" }, + { name => "virDomainDefineXML", sig => "conn, string : dom&...

libvirt-ocaml is used only by virt-v2v, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): common: Bundle the libvirt-ocaml library for use by virt-v2v build: switch embedded copy of libvirt-ocaml .gitignore | 2 + 3rdparty/libvirt-ocaml/Makefile.am |

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all