[libvirt] [glib 2/5] gconfig: DomainDevice now instantiable

We'll need to instatiate DomainDevice baseclass itself for unknown (think new devices added to libvirt XML) devices in a following patch. This change makes that possible. This doesn't break any API or ABI to the best of my knowledge and this assumption was confirmed by Emmanuele Bassi and

[libvirt] [glib 5/5] gconfig, tests: Add test case for unknown devices

--- tests/test-gconfig.c | 22 ++ 1 file changed, 22 insertions(+) diff --git a/tests/test-gconfig.c b/tests/test-gconfig.c index 5389a26..b91f5af 100644 --- a/tests/test-gconfig.c +++ b/tests/test-gconfig.c @@ -762,6 +762,26 @@ static void

[libvirt] [glib 3/5] gconfig: Create objects for all domain device nodes

Currently we can and do get into serious trouble with this kind of code: devices = gvir_config_domain_get_devices(domain); gvir_config_domain_set_devices(domain, domain); since the first call above won't return a complete list of objects present in the domain but only the ones we have specific

[libvirt] [glib 4/5] gconfig,tests: Separate XML loading function

We'll need to load XML from file in another function, that will be added in a following patch. --- tests/test-gconfig.c | 15 +-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/tests/test-gconfig.c b/tests/test-gconfig.c index a26bb5f..5389a26 100644 ---

[libvirt] [glib 1/5] gconfig: Allow schema to be NULL

Validation (if attempted) should just fail in this case instead of crashing. --- libvirt-gconfig/libvirt-gconfig-object.c | 8 1 file changed, 8 insertions(+) diff --git a/libvirt-gconfig/libvirt-gconfig-object.c b/libvirt-gconfig/libvirt-gconfig-object.c index 6225de2..851e35c 100644

[libvirt] [PATCH] loopback is not always just lo

On BSD family OSes (Free/Net/Open/DragonFlyBSD, Mac OS) and Solaris loopback interface is called 'lo0' instead of just 'lo'. --- src/network/bridge_driver.c | 5 + 1 file changed, 5 insertions(+) diff --git a/src/network/bridge_driver.c b/src/network/bridge_driver.c index a3ee3f3..9d94d65

Re: [libvirt] [PATCH v3 4/6] remote: expose a new libssh transport

On Wed, Oct 19, 2016 at 14:40:37 +0200, Pino Toscano wrote: > Implement in virtNetClient and VirNetSocket the needed functions to > expose a new libssh transport, providing all the options that the > libssh2 transport supports. > --- > docs/remote.html.in| 35 ++--- >

Re: [libvirt] libvirt label qemu process problem

On Tue, Nov 01, 2016 at 05:14:27PM +0800, zhun...@gmail.com wrote: I found that when using souce code to install libvirt,it labeled qemu process with label "unconfined_u:unconfined_r:svirt_t:s0:c53,c366" instead of "system_u:system_r:svirt_t:s0:c53,c366",is this a bug??can anyone explain it ??

Re: [libvirt] [PATCH v3 3/6] libssh_transport: add new libssh-based transport

On Wed, Oct 19, 2016 at 14:40:36 +0200, Pino Toscano wrote: > Implement a new libssh transport, which uses libssh to communicate with > remote hosts, and add all the build system stuff (search of libssh, > private symbols, etc) to built it. > > This new transport supports all the common ssh

[libvirt] [PATCH 2/3] Add support for preallocated fd memory

This second change introduces support for preallocated shared file descriptor based memory backing. It allows vhost-user to be used without hugepages. Also token memAccess in numa cell is used (if not present, default value from memoryBacking is used) Used xml elements: ---

[libvirt] [PATCH 3/3] Add support for preallocated fd memory - doc

Add html documentation for memoryBacking element. --- docs/formatdomain.html.in | 10 ++ 1 file changed, 10 insertions(+) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index c70377b..ed15eb5 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@

[libvirt] [PATCH 0/3] Add support for preallocated fd memory

Hi, we would like to introduce 3 new elements source,access and allocation in memoryBacking element. If allocation is immediate then -mem-prealloc should be added to the qemu commanline. If source is file then -object

[libvirt] [PATCH 1/3] Add support for preallocated fd memory

This first change introduces xml parsing support for preallocated shared file descriptor based memory backing. It allows vhost-user to be used without hugepages. New xml elements: --- docs/schemas/domaincommon.rng | 30 + src/conf/domain_conf.c

[libvirt] [PATCH 1/2] Add support for preallocated fd memory

This first change introduces xml parsing support for preallocated shared file descriptor based memory backing. It allows vhost-user to be used without hugepages. New xml elements: --- docs/schemas/domaincommon.rng | 30 + src/conf/domain_conf.c

Re: [libvirt] [PATCH] docs: remove obsolete library.xen file

On Mon, Oct 31, 2016 at 08:42:46AM -0600, Jim Fehlig wrote: > On 10/31/2016 07:40 AM, Daniel P. Berrange wrote: > > The library.xen file contains a braindump of thoughts dating > > from the very first days of libvirt, when it was briefly > > called libxen. This is not useful and potentially

Re: [libvirt] [PATCH 0/2] Add support for preallocated fd memory

I forgot to add the updated documentation. I will send it in different patch. > -Original Message- > From: Safka, JaroslavX > Sent: Tuesday, November 01, 2016 12:45 PM > To: libvir-list@redhat.com > Cc: Ptacek, MichalX ; Mooney, Sean K >

[libvirt] [PATCH 2/2] Add support for preallocated fd memory

This second change introduces support for preallocated shared file descriptor based memory backing. It allows vhost-user to be used without hugepages. Also token memAccess in numa cell is used (if not present, default value from memoryBacking is used) Used xml elements: ---

[libvirt] [PATCH 0/2] Add support for preallocated fd memory

Hi, we would like to introduce 3 new elements source,access and allocation in memoryBacking element. If allocation is immediate then -mem-prealloc should be added to the qemu commanline. If source is file then -object

[libvirt] [PATCH 1/8] daemon: Introduce daemonSetLoggingDefaults

This patch moves the code responsible for setting up logging defaults to a separate function to enhance the readability a bit more. This code movement is also meant as a preparation phase for a future refactor of the affected hunks. Signed-off-by: Erik Skultety ---

[libvirt] [PATCH 7/8] admin: Introduce virAdmConnectSetLoggingFilters

Enable libvirt users to modify logging filters of a daemon from outside. Signed-off-by: Erik Skultety --- daemon/admin.c | 10 ++ include/libvirt/libvirt-admin.h | 4 src/admin/admin_protocol.x | 12 +++-

[libvirt] [PATCH 2/8] virlog: Introduce virLog{Get, Set}DefaultOutput

The reason why we need something like this lies in the daemon's config where we treat the @log_outputs variable (but not just this one) the very same way in cases where the variable was explicitly set to an empty string or wasn't set at all, using some default output in both. The selection of a

[libvirt] [PATCH 6/8] admin: Introduce virAdmConnectSetLoggingOutputs

Enable libvirt users to modify daemon's logging output settings from outside. If an empty set is passed, a default logging output will be used the same way as it would be in case writing an empty string to the libvirtd.conf Signed-off-by: Erik Skultety --- daemon/admin.c

[libvirt] [PATCH 4/8] admin: Introduce virAdmConnectGetLoggingOutputs

Enable libvirt users to query logging output settings. Signed-off-by: Erik Skultety --- daemon/admin.c | 52 + include/libvirt/libvirt-admin.h | 4 src/admin/admin_protocol.x | 16 -

[libvirt] [PATCH 5/8] admin: Introduce virAdmConnectGetLoggingFilters

Enable libvirt users to query logging filter settings. Signed-off-by: Erik Skultety --- daemon/admin.c | 52 + include/libvirt/libvirt-admin.h | 4 src/admin/admin_protocol.x | 16 -

[libvirt] [PATCH 8/8] virt-admin: Wire-up the logging APIs

Finally, now that all APIs have been introduced, wire them up to virt-admin and introduce dmn-log-info and dmn-log-define commands. Signed-off-by: Erik Skultety --- tools/virt-admin.c | 141 + 1 file changed, 141

[libvirt] [PATCH 3/8] daemon: Hook up the virLog{Get, Set}DefaultOutput to the daemon's init routine

Now that virLog{Get,Set}DefaultOutput routines are introduced we can wire them up to the daemon's logging initialization code. As part of this process, refactor the daemonSetupLoggingDefaults method, since the code isn't particularly easy to read (due to the condition below). However, this

[libvirt] [PATCH 0/8] admin: Introduce runtime logging APIs

Because all the necessary refactors to the logging code have been merged for some time already, now it's time to finally enable the logging APIs. Since there's been an effort to deprecate the concept of the log_level setting in the config (as per discussion [1]), I dropped patches introducing

[libvirt] libvirt label qemu process problem

I found that when using souce code to install libvirt,it labeled qemu process with label "unconfined_u:unconfined_r:svirt_t:s0:c53,c366" instead of "system_u:system_r:svirt_t:s0:c53,c366",is this a bug??can anyone explain it ?? thanks! zhun...@gmail.com -- libvir-list mailing list