similar to: [PATCH 1/2] lib: enable the libvirt code consistently everywhere

Displaying 20 results from an estimated 200 matches similar to: "[PATCH 1/2] lib: enable the libvirt code consistently everywhere"

2014 Apr 01
3
set keep alive
Can anyone explain what is happening. After call virConnectOpen virEventRegisterDefaultImpl() call virConnectSetKeepAlive returns VirtError(1): internal error: the caller doesn't support keepalive protocol; perhaps it's missing event loop implementation, but the next call this sequence of commands returns success. Why virConnectSetKeepAlive not work right the first time? -- Fl at sh
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
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 Dec 16
3
[v2v PATCH 0/2] Move libvirt-ocaml copy to v2v repo
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 |
2016 May 17
0
[PATCH 1/2] src: start unifying version handling
Introduce a new struct version with few helper functions for it: this allows to "atomically" represent a version number, without different variables to be used and checked together. Add a initialization function from a libvirt-style version number, and apply it for the qemu and libvirt versions in the direct and libvirt backends. --- src/Makefile.am | 1 +
2015 Oct 05
0
[PATCH 2/2] Fix whitespace.
Because of previous automated commits, such as changing 'guestfs___' -> 'guestfs_int_', several function calls no longer lined up with their parameters, and some lines were too long. The bulk of this commit was done using emacs batch mode and the technique described here: http://www.cslab.pepperdine.edu/warford/BatchIndentationEmacs.html The changes suggested by emacs were
2010 Mar 26
1
[PATCH] appliance: Set $PATH instead of hard-coding paths to binaries everywhere.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -------------- next part -------------- >From 0420307349a71b7b9af58003c2591fc33b7939af Mon Sep 17 00:00:00 2001 From: Richard
2011 Nov 08
1
[PATCH] NFC: Update FSF address everywhere it's used
The FSF is now at 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. --- Makefile.am | 2 +- align/Makefile.am | 2 +- align/scan.c | 2 +- align/virt-alignment-scan.pod | 2 +- appliance/Makefile.am | 2 +-
2015 Aug 04
1
[PATCH] Simplify and generalize implementation of align(). Should be very efficient on sensible platforms, and correct everywhere.
--- src/opus_private.h | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/src/opus_private.h b/src/opus_private.h index 63338fe..5bbd7dc 100644 --- a/src/opus_private.h +++ b/src/opus_private.h @@ -33,6 +33,8 @@ #include "opus.h" #include "celt.h" +#include <stddef.h> /* offsetof */ + struct OpusRepacketizer { unsigned char
2018 Nov 12
0
[PATCH 2/2] drm/atomic: Create and use __drm_atomic_helper_crtc_reset() everywhere
Am Montag, 12. November 2018, 16:01:14 CET schrieb Maarten Lankhorst: > We already have __drm_atomic_helper_connector_reset() and > __drm_atomic_helper_plane_reset(), extend this to crtc as well. > > Most drivers already have a gpu reset hook, correct it. > Nouveau already implemented its own __drm_atomic_helper_crtc_reset(), > convert it to the common one. > >
2019 Jun 17
0
[PATCH 06/59] drm/prime: Actually remove DRIVER_PRIME everywhere
On 2019/06/14, Daniel Vetter wrote: > Split out to make the functional changes stick out more. > Since this patch flew-by, as standalone one (intentionally or not) I'd add, anything vaguely like: "Core users of DRIVER_PRIME were removed from core with prior patches." HTH Emil
2016 Feb 23
0
Re: [PATCH 1/2] lib: Allow the COMPILE_REGEXP macro to be used everywhere.
On Tuesday 23 February 2016 09:17:42 Richard W.M. Jones wrote: > Since the daemon links to pcre and use regular expressions, and since > the COMPILE_REGEXP macro doesn't depend on any aspects of the > library-side code (eg. the guestfs_h handle etc), we can allow the > daemon to use the COMPILE_REGEXP macro. Move the macro to > "guestfs-internal-all.h" to permit this.
2006 Sep 02
1
Access email and addressbook from everywhere
Hello. I using evolution for email, and runs well, now the next that I would like is access to my email and evolution addressbook from everywhere. What should I install? there is any webmail that can use evolution settings? Or better a program for control that computer that I can access from any computer with a web browser? There is anything as this? Josep
2015 May 15
2
https everywhere.
What are the plans for the CentOS repos with respect to authentication and https everywhere? At the moment it is a trivial exercise to perform a MTM attack during a yum update over http. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited
2015 May 15
0
https everywhere.
On Fri, May 15, 2015 at 03:44:39PM -0400, James B. Byrne wrote: > What are the plans for the CentOS repos with respect to authentication > and https everywhere? At the moment it is a trivial exercise to > perform a MTM attack during a yum update over http. Since the packages themselves are signed, what risk are you concerned about? -- Matthew Miller <mattdm at fedoraproject.org>
2015 May 15
2
https everywhere.
On 05/15/2015 02:49 PM, Matthew Miller wrote: > On Fri, May 15, 2015 at 03:44:39PM -0400, James B. Byrne wrote: >> What are the plans for the CentOS repos with respect to authentication >> and https everywhere? At the moment it is a trivial exercise to >> perform a MTM attack during a yum update over http. > > Since the packages themselves are signed, what risk are you
2015 May 16
0
https everywhere.
On 16/05/15 08:36, Jim Perrin wrote: > > > On 05/15/2015 02:49 PM, Matthew Miller wrote: >> On Fri, May 15, 2015 at 03:44:39PM -0400, James B. Byrne wrote: >>> What are the plans for the CentOS repos with respect to authentication >>> and https everywhere? At the moment it is a trivial exercise to >>> perform a MTM attack during a yum update over http.