search for: virdomainreboot

I am trying to reboot my virtual machines, running virsh reboot. Then I get the following error: error: this function is not supported by the connection driver: virDomainReboot Searching around I get the impression this should be fixed by now, since the bugs I find are old and resolved. These are the versions I'm running. Linux 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux libvirt-0.8.7-18.el6.x86_64 qemu-kvm-0.12.1.2-...

Hi, Eric: I want to reboot vm using libvirt reboot api virDomainReboot(). but it occured error like following: "error: Failed to reboot domain abc" "error: Requested operation is not valid: Reboot is not supported without the JSON monitor". I updated qemu version,such as "qemu-kvm-1.2.0", it still like that. can you give me any ideas?...

...y the most popular virtualization solution that libvirt can control is KVM, but it can also manage Xen, VMware ESX, LXC (linux containers), UML, etc. Libvirt provides both tools (like virsh and libvirtd) and APIs for interacting with virtual machines. The APIs are things like virDomainShutdown(), virDomainReboot(), etc. The ruby-libvirt package is a thin wrapper around these APIs, so that you can use this functionality from ruby programs. That is, you would be able to do something like: dom.reboot dom.shutdown from your ruby programs. There are also bindings for other languages such as python, php, an...

...ect.py", line 83, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1378, in reboot self._backend.reboot(0) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2024, in reboot if ret == -1: raise libvirtError ('virDomainReboot() failed', dom=self) libvirtError: Timed out during operation: cannot acquire state change lock (held by qemuProcessReconnect) Whereby VMM loads, showing my VM in the "Paused" state and will not start, restart, shout down, etc. Restarting libvirt did not seem to have an effect o...

...ring, 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" }, + { name => "virDomainUndefine", sig => "dom : unit" }, + { name => "virDomainCreate", sig => "dom : unit&...

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