search for: virdomaingetst

Displaying 10 results from an estimated 10 matches for "virdomaingetst".

Did you mean: virdomaingetid
2017 Aug 09
2
libvirt: XML-RPC error : Cannot write data: Broken pipe
Hi all, I think it's a bug, when call virDomainGetState after "service libvirtd stop", I receive signal SIGPIPE. I want to know how to avoid this problem? And Other interfaces will also encounter this problem? Below the bt information: Below some information about my hypervisor: root@ubuntu-05:/datapool/zhuohf# virsh -v 3.4.0 root@ubuntu-05...
2011 Jun 06
0
Release of libvirt-0.9.2
...top other concurrent operations (like virsh list). See below for a number of new features, improvement and bug fixes: Features: - Framework for lock manager plugins (Daniel P. Berrange) - API for network config change transactions (Michal Privoznik) - flags for setting memory parameters (Hu Tao) - virDomainGetState public API (Jiri Denemark) - qemu: allow blkstat/blkinfo calls during migration (Federico Simoncelli) - Introduce migration v3 API (Daniel P. Berrange) - Defining the Screenshot public API (Michal Privoznik) - public API for NMI injection (Lai Jiangshan) Documentation: - esx: Fix driver method...
2017 Aug 09
0
Re: libvirt: XML-RPC error : Cannot write data: Broken pipe
On Wed, Aug 09, 2017 at 11:53:54AM +0800, netsurfed wrote: > Hi all, > I think it's a bug, when call virDomainGetState after "service libvirtd stop" > , I receive signal SIGPIPE. For the QEMU driver, the libvirt library just talks to libvirtd over an RPC layer. You killed libvirtd, so the libvirt library gets SIGPIPE. > I want to know how to avoid this problem? And Other interfaces will also I...
2017 Aug 09
2
Re: libvirt: XML-RPC error : Cannot write data: Broken pipe
...ould sax that it is impossible to talk to libvirtd and that it might be stopped. On 9 Aug 2017 2:19 p.m., "Daniel P. Berrange" <berrange@redhat.com> wrote: > On Wed, Aug 09, 2017 at 11:53:54AM +0800, netsurfed wrote: > > Hi all, > > I think it's a bug, when call virDomainGetState after "service libvirtd > stop" > > , I receive signal SIGPIPE. > > For the QEMU driver, the libvirt library just talks to libvirtd over an > RPC layer. You killed libvirtd, so the libvirt library gets SIGPIPE. > > > I want to know how to avoid this problem?...
2019 Apr 08
0
[PATCH v4 3/7] v2v: switch to ocaml-libvirt
...ot;guestfs.h" -#include "guestfs-utils.h" - -#pragma GCC diagnostic ignored "-Wmissing-prototypes" - -#define ERROR_MESSAGE_LEN 512 - -static void -ignore_errors (void *ignore, virErrorPtr ignore2) -{ - /* empty */ -} - -/* Get the remote domain state (running, etc.). Use virDomainGetState - * which is most efficient, but if it's not implemented, fall back to - * virDomainGetInfo. See equivalent code in virsh. - */ -static int -get_dom_state (virDomainPtr dom) -{ - int state, reason; - virErrorPtr err; - virDomainInfo info; - - if (virDomainGetState (dom, &state, &amp...
2018 Aug 30
8
[PATCH 0/7] RFC: switch v2v to ocaml-libvirt
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
2018 Nov 27
8
[PATCH v2 0/7] RFC: switch v2v to ocaml-libvirt
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
2019 Jan 30
8
[PATCH v3 0/7] RFC: switch v2v to ocaml-libvirt
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
2019 May 20
8
[PATCH v5 0/7] v2v: switch to ocaml-libvirt
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
2019 Apr 08
12
[PATCH 43 0/7] v2v: switch to ocaml-libvirt
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