Re: [libvirt] [PATCH 2/2] virDomainGetBlockJobInfo: Fix corner case when qemu reports no info

On 09/05/2016 07:48 AM, Michal Privoznik wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1372613 > > Apparently, some management applications use the following code > pattern when waiting for a block job to finish: > > while (1) { > virDomainGetBlockJobInfo(dom, disk, info, flags);

[libvirt] [PATCH v6 3/5] qemu: Introduce qemuDomainChardevPrivatePtr

Modeled after the qemuDomainHostdevPrivatePtr (commit id '27726d8c'), create a privateData pointer in the _virDomainChardevDef to allow storage of private data for a hypervisor in order to at least temporarily store secret data for usage during qemuBuildCommandLine. NB: Since the

[libvirt] [PATCH v6 5/5] qemu: Add the ability to hotplug a secret object for TCP chardev TLS

https://bugzilla.redhat.com/show_bug.cgi?id=1300776 Complete the implementation of support for TLS encryption on chardev TCP transports by adding the hotplug ability of a secret to generate the passwordid for the TLS object Likewise, add the ability to hot unplug that secret object as well

[libvirt] [PATCH v6 1/5] domain: Add optional 'disableTLS' attribute for TCP chardev

Add an optional "disableTLS='yes'" option for a TCP chardev for the express purpose to not enable setting up TLS for the chardev Signed-off-by: John Ferlan --- docs/formatdomain.html.in | 20 + docs/schemas/domaincommon.rng

[libvirt] [PATCH v6 2/5] conf: Introduce {default|chardev}_tls_x509_secret_uuid

Add a new qemu.conf variables to store the UUID for the secret that could be used to present credentials to access the TLS chardev. Since this will be a server level and it's possible to use some sort of default, introduce both the default and chardev logic at the same time making the setting of

[libvirt] [PATCH v6 0/5] Add native TLS encrypted chardev TCP support

v5: http://www.redhat.com/archives/libvir-list/2016-August/msg00282.html Patches 1-5 from that series already pushed Patch 6 from that series is removed Patch 7 is untouched and is patch 3 in this series Patches 8-9 modified for new paradigm (patches 4-5 of this series) Patch 1 [NEW] From patch

[libvirt] [PATCH v6 4/5] qemu: Add a secret object to/for a chardev tcp with secret

Add the secret object prior to the chardev tcp so the 'passwordid=' can be added if the domain XML has a for the chardev TLS. Signed-off-by: John Ferlan --- src/qemu/qemu_command.c| 32 ++- src/qemu/qemu_command.h|

[libvirt] [PATCH] conf: allow hotplugging "legacy PCI" device to manually addressed PCIe slot

In a full domain config, libvirt allows overriding the normal PCI vs. PCI Express rules when a device address is explicitly provided (so, e.g., you can force a legacy PCI device to plug into a PCIe port, although libvirt would never do that on its own). However, due to a bug libvirt doesn't give

[libvirt] [libvirt-perl PATCH 1/2] Add support for VIR_SECRET_USAGE_TYPE_TLS

Allows libvirt-perl to build with upstream libvirt. Signed-off-by: John Ferlan --- Changes| 1 + Virt.xs| 1 + lib/Sys/Virt/Secret.pm | 7 +++ 3 files changed, 9 insertions(+) diff --git a/Changes b/Changes index 650b40c..8eb298a 100644

[libvirt] [libvirt-perl PATCH 2/2] Add support for ERR_AGENT_UNSYNCED

Allows libvirt-perl to build with upstream libvirt. Signed-off-by: John Ferlan --- Changes | 1 + Virt.xs | 1 + lib/Sys/Virt/Error.pm | 4 3 files changed, 6 insertions(+) diff --git a/Changes b/Changes index 8eb298a..c346ad1 100644 ---

[libvirt] [libvirt-perl PATCH 0/2] Updates to support recent upstream changes

Couple of patches to allow build/test to work with upstream top John Ferlan (2): Add support for VIR_SECRET_USAGE_TYPE_TLS Add support for ERR_AGENT_UNSYNCED Changes| 2 ++ Virt.xs| 2 ++ lib/Sys/Virt/Error.pm | 4 lib/Sys/Virt/Secret.pm | 7 +++ 4

Re: [libvirt] xen/libvirt freeze while attching network-device to vm´s - question about provided patches

On Thu, 2016-09-08 at 14:04 +, guido.rossmuel...@gdata.de wrote: > Hello everybody, > > a colleague of me described last november a problem that we have with libvirt > and xen > > https://www.redhat.com/archives/libvir-list/2015-November/msg00130.html > > Jim Fehlig provided for this

Re: [libvirt] [PATCH v2 01/10] Introduce NVDIMM memory model

On Fri, Sep 09, 2016 at 11:31:07AM +0200, Michal Privoznik wrote: > On 08.09.2016 16:15, Peter Krempa wrote: > > On Thu, Sep 08, 2016 at 14:59:07 +0100, Daniel Berrange wrote: > >> On Thu, Sep 08, 2016 at 03:50:40PM +0200, Michal Privoznik wrote: > > > > [...] > > > >> This is very different to

Re: [libvirt] [PATCH v2 01/10] Introduce NVDIMM memory model

On 08.09.2016 16:15, Peter Krempa wrote: > On Thu, Sep 08, 2016 at 14:59:07 +0100, Daniel Berrange wrote: >> On Thu, Sep 08, 2016 at 03:50:40PM +0200, Michal Privoznik wrote: > > [...] > >> This is very different to how we deal with addressing for all other >> types of device in libvirt, where

Re: [libvirt] [PATCH v5 6/9] conf: Add new secret element for tcp chardev

On Tue, Sep 06, 2016 at 06:29:38PM -0400, John Ferlan wrote: > > > On 08/05/2016 04:25 AM, Daniel P. Berrange wrote: > > On Thu, Aug 04, 2016 at 11:21:24AM -0400, John Ferlan wrote: > >> Define, parse, and format a key secret element for a chardev tcp backend. > >> This secret will be used in

Re: [libvirt] [PATCH 0/3] add option to keep nvram file on undefine

27-May-16 11:05, Nikolay Shirokovskiy пишет: There is already a patch [1] on this topic with a different approach - keep nvram file by default. There is also some discussion there. To sum up keeping nvram on undefine could be useful in some usecases so there should be an option to do it. On

Re: [libvirt] [PATCH 0/3] add option to keep nvram file on undefine

ping On 27.05.2016 11:05, Nikolay Shirokovskiy wrote: > There is already a patch [1] on this topic with a different approach - keep > nvram file by default. There is also some discussion there. To sum up keeping > nvram on undefine could be useful in some usecases so there should be an >