- Devel - libvirt List Archives

[libvirt] [PATCH] A word error about net-dumpxml --inactive
by sannyshao 16 Jun '16

16 Jun '16

--- tools/virsh-network.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/virsh-network.c b/tools/virsh-network.c index 5abcda3..fcf1f0b 100644 --- a/tools/virsh-network.c +++ b/tools/virsh-network.c @@ -282,7 +282,7 @@ static const vshCmdOptDef opts_network_dumpxml[] = { VIRSH_COMMON_OPT_NETWORK, {.name = "inactive", .type = VSH_OT_BOOL, - .help = N_("network information of an inactive domain") + .help = N_("network information of an inactive network") }, {.name = NULL} }; -- 1.8.3.1

2 1

[libvirt] [PATCH v2 0/6] Some patches for native TLS encrypted chardev TCP support
by John Ferlan 16 Jun '16

16 Jun '16

v1: http://www.redhat.com/archives/libvir-list/2016-June/msg00824.html Based on Dan's review from patch 4, alter the methodology to use the libvirt qemu config file to add support for a 'default' and (at first) a 'chartcp' (I could use chardev, but I was concerned that would imply more options - udp, unix, etc.). I have started on the authentication portion of this (e.g. a passwordid= parameter pointing at a secret object), but I'm a bit held up by the need to have the secret key patches. I've separated those out and will post a separate set shortly as well to hopefully get some traction. For the chartcp, I went with the 'default' location for the /etc/pki path - that will at least test patch 1. I also tested those locally by removing the code in qemuxml2xmltest.c to specify the specific -vnc or -spice paths as the test has. John Ferlan (6): conf: Add new default TLS X.509 certificate default directory conf: Introduce chartcp_tls_x509_cert_dir qemu: Make qemuBuildShmemBackendStr private qemu: Add cfg pointer to various command line helpers qemu: Add support for TLS X.509 path to TCP chardev backend qemu: Add the ability to hotplug the TLS X.509 environment src/conf/domain_conf.h | 1 + src/qemu/libvirtd_qemu.aug | 9 +- src/qemu/qemu.conf | 52 ++++--- src/qemu/qemu_command.c | 158 ++++++++++++++++++--- src/qemu/qemu_command.h | 12 +- src/qemu/qemu_conf.c | 45 +++++- src/qemu/qemu_conf.h | 5 + src/qemu/qemu_hotplug.c | 29 +++- src/qemu/qemu_monitor_json.c | 9 ++ src/qemu/test_libvirtd_qemu.aug.in | 3 + .../qemuxml2argv-serial-tcp-tlsx509-chardev.args | 33 +++++ .../qemuxml2argv-serial-tcp-tlsx509-chardev.xml | 41 ++++++ tests/qemuxml2argvtest.c | 6 + .../qemuxml2xmlout-serial-tcp-tlsx509-chardev.xml | 50 +++++++ tests/qemuxml2xmltest.c | 1 + 15 files changed, 399 insertions(+), 55 deletions(-) create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-serial-tcp-tlsx509-chardev.args create mode 100644 tests/qemuxml2argvdata/qemuxml2argv-serial-tcp-tlsx509-chardev.xml create mode 100644 tests/qemuxml2xmloutdata/qemuxml2xmlout-serial-tcp-tlsx509-chardev.xml -- 2.5.5

2 13

[libvirt] [PATCH 0/2] qemu: active blockjob error tweaks
by Cole Robinson 16 Jun '16

16 Jun '16

Just a couple error message tweaks/cleanups regarding active block jobs, noticed while looking at https://bugzilla.redhat.com/show_bug.cgi?id=1342276 Cole Robinson (2): qemu: More usage of qemuDomainDiskBlockJobIsActive qemu: migration: use consistent error message src/qemu/qemu_driver.c | 7 +------ src/qemu/qemu_hotplug.c | 6 +----- src/qemu/qemu_migration.c | 2 +- 3 files changed, 3 insertions(+), 12 deletions(-) -- 2.7.4

2 5

[libvirt] [PATCH 0/2] Don't add a pci-bridge unless needed on Q35/aarch64
by Laine Stump 16 Jun '16

16 Jun '16

I had these in a branch waiting for further work to make them more useful, and abologna asked about this topic, so I'm posting these two patches. Note that in most cases we'll still get a pci-bridge device added (since most devices are legacy PCI) but at least if the config doesn't have any unaddressed PCI devices, that won't happen. As patch 1 states, the dmi-to-pci-bridge will still be there in all cases for Q35/aarch64. That needs more work to eliminate. Laine Stump (2): qemu: don't be as insistent about adding dmi-to-pci-bridge or pci-bridge qemu: don't add pci-bridge to Q35/arm domains unless it's needed src/qemu/qemu_domain.c | 14 +++++++------- .../qemuxml2argv-aarch64-virt-2.6-virtio-pci-default.args | 1 - .../qemuxml2argv-aarch64-virtio-pci-default.args | 1 - tests/qemuxml2argvdata/qemuxml2argv-pcie-root.args | 3 +-- .../qemuxml2xmlout-aarch64-virtio-pci-default.xml | 5 ----- tests/qemuxml2xmloutdata/qemuxml2xmlout-pcie-root.xml | 5 ----- 6 files changed, 8 insertions(+), 21 deletions(-) -- 2.5.5

2 4

[libvirt] [PATCH] util: Fix broken syntax-check
by John Ferlan 16 Jun '16

16 Jun '16

Commit id '743db933' broke at least one syntax check rule regard open/close braces and perhaps more with spacing. Just remove the braces Signed-off-by: John Ferlan <jferlan(a)redhat.com> --- Pushed as build breaker src/util/virauthconfig.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/util/virauthconfig.c b/src/util/virauthconfig.c index b58937c..91c9c0c 100644 --- a/src/util/virauthconfig.c +++ b/src/util/virauthconfig.c @@ -123,9 +123,8 @@ int virAuthConfigLookup(virAuthConfigPtr auth, if (!virKeyFileHasGroup(auth->keyfile, authgroup)) { VIR_FREE(authgroup); - if (virAsprintf(&authgroup, "auth-%s-%s", service, "default") < 0){ + if (virAsprintf(&authgroup, "auth-%s-%s", service, "default") < 0) goto cleanup; - } } if (!virKeyFileHasGroup(auth->keyfile, authgroup)) { -- 2.5.5

1 0

[libvirt] RFC: New CPU hot(un)plug API and XML
by Peter Krempa 16 Jun '16

16 Jun '16

Hi list, I'm planing on adding API that will be used instead of virDomainSetVcpus and will allow a more granular control of which virtual CPUs are enabled for a guest. The new approach will allow to use cpu hotplug properly with NUMA guests as the old APIs would not allow adding CPUs to very specific cgroups. The old APIs should still work fine with the current approach although the final implementation should also allow to unplug vcpus from the guest by using new qemu features. I'm still not sure though whether it will be possible to use this in a backward compatible fashion though depending how this stuff will exactly need to be set up in qemu. # API # As for the new API I'm thinking of the following design: int virDomainVcpu(virDomainPtr domain, unsigned int id, unsigned int flags); The flags for this API would be following: - usual domain modification impact: * VIR_DOMAIN_SET_VCPU_CURRENT * VIR_DOMAIN_SET_VCPU_LIVE * VIR_DOMAIN_SET_VCPU_CONFIG - for specifying the operation as the default operation would query the cpu state: * VIR_DOMAIN_SET_VCPU_ENABLE * VIR_DOMAIN_SET_VCPU_DISABLE - misc: * VIR_DOMAIN_SET_VCPU_GUEST - use the guest agent instead of ACPI hotplug * VIR_DOMAIN_SET_VCPU_NUMA_NODE - 'id' is the ID of a numa node where the cpu should be enabled/disabled rather than CPU id. This is a convenience flag that will allow to add cpu to a given numa node rather than having to find the correct ID. * VIR_DOMAIN_SET_VCPU_CORE - use thread level hotplug (see [1]). This makes sure that the CPU will be plugged in on platforms that require to plug in multiple threads at once. VIR_DOMAIN_SET_VCPU_NUMA_NODE and VIR_DOMAIN_SET_VCPU_GUEST are mutually exclusive as the guest agent doesn't report the guest numa node the CPU is belonging to . If the idea of one API that will both query and set is too nonconformist to our existing API design I have no problem adding Get/Set versions and/or explode the ADD/REMOVE flags into a separate parameter. # XML # The new API will require us to add new XML that will allow to track the state of VCPUs individually. Internally we now have a data structure allowing to keep the relevant data in one place. Currently we are setting data relevant to VCPUs in many places. <domain> [...] <vcpu current='1'>3</vcpu> [...] <cputune> <cpupin ... /> </cputune> [...] <cpu> <numa> <cell id='0' cpus='0' memory='102400' unit='KiB/> <cell id='1' cpus='1-2' memory='102400' unit='KiB/> </numa> As we'll be required to keep the state for every single cpu I'm thinking of adding a new subelement called '<vcpus>' to <domain>. This will have a '<vcpu>' subelement for every configured cpu. I'm specifically not going to add any of the cpupin or numa node ids to the /domain/vcpus/vcpu as input parameters to avoid introducing very compicated checking code that would be required to keep the data in sync. I'm thinking of adding the numa node id as an output only attribute since it's relevant to the hotplug case and it's misplaced otherwise. I certainly can add the duplicated data as output-only attributes. The XML with the new elements should look like: <domain> [...] <vcpu current='1'>3</vcpu> <vcpus> <vcpu id='0' state='enabled'/> <-- option 1, no extra data <vcpu id='1' state='disabled' cell='1'/> <--- option 2, just numa node, since it's non-obvious <vcpu id='2' state='disabled' cell='1' pin='1-2' scheduler='...'/>  </vcpus> [...] <cputune> <cpupin ... /> </cputune> [...] <cpu> <numa> <cell id='0' cpus='0' memory='102400' unit='KiB/> <cell id='1' cpus='1-2' memory='102400' unit='KiB/> </numa> # migration # To ensure migration compatibility a new libvirt will set a new migration feature flag in cases where a sparse topology was created by any means. Older versions of libvirt will reject it. As the new cpu data will be ignored by the parser of older libvirt we don't need to stop formatting them on migration. (fortunately schemas are not validated during migration) # qemu/platform implementation caveats # When starting the VM for the first time it might be necessary to start a throw-away qemu process to query some details that we'll need to pass in on a command line. I'm not sure if this is still necessary and I'll try to avoid it at all cost. [1] Some architectures (ppc64) don't directly support thread-level hotplug and thus require us to plug in a core which translates into multiple threads (8 in case of power 8). Possibly other yet unknown problems. Thanks for your feedback. Peter

3 4

[libvirt] [PATCH] syntax-check: drop prohibit_undesirable_word_seq
by Ján Tomko 16 Jun '16

16 Jun '16

This checks forbids using "can not" and checks the placement of some texinfo tags. Drop it since we do not use texinfo and the check takes almost twice as much as the rest of the checks. --- cfg.mk | 1 + 1 file changed, 1 insertion(+) diff --git a/cfg.mk b/cfg.mk index 297ca3a..d82070d 100644 --- a/cfg.mk +++ b/cfg.mk @@ -64,6 +64,7 @@ local-checks-to-skip = \ sc_prohibit_quote_without_use \ sc_prohibit_quotearg_without_use \ sc_prohibit_stat_st_blocks \ + sc_prohibit_undesirable_word_seq \ sc_root_tests \ sc_space_tab \ sc_sun_os_names \ -- 2.7.3

2 1

[libvirt] Patch review request for Red Hat Bugzilla Bug 1341866
by Ashish Mittal 15 Jun '16

15 Jun '16

Hi, This is a patch review request in response to the following bugzilla: Bug 1341866 RFE: Request to upstream libvirt dependencies for qemu based network block driver from Veritas (1) This patch is required to enable Veritas OpenFlame functionality on RedHat OSP8 platform. (2) Patch has been created on top of libvirt-1.2.17-13.el7.x86_64. Please let me know in case patch has to be rebased on top of the latest libvirt git master branch instead. Regards, Ashish

2 5

[libvirt] [PATCH v3 0/7] Introducing storage pool lifecycle event APIs
by Jovanka Gulicoska 15 Jun '16

15 Jun '16

Changes since v2 listed in every commit separately Introducing implementation of storage pool event APIs. Code changes follow network event APIs. Implemented functions: virStoragePoolEventRegisterAny(), virStoragePoolEventDeregisterAny(), virStoragePoolLifeCycleEventNew(), introduced STARTED, STOPPED, DEFINE, UNDEFINE and REFRESHED. STARTED signal is emiited in storagePoolCreateXML() and storagePoolCreate() DEFINED signal is emitted in storagePoolDefineXML() UNDEFINED signal is emitted in storagePoolUndefine() STOPPED signal is emitted in storagePoolDestroy() and storagePoolRefresh() REFRESHED signal is emitted in storagePoolRefresh() There are also test as well as unittests for the new functions and signals. This is part of a GSOC project: Asynchronous lifecycle events for storage objects As part of the project there should also be implementation for storage volume events. For now there's no signal when volumes are created or deleted, they can also be implemented, but probably the easiest way is to have apps watch for REFRESH signal, and later extend storage driver code to refresh a pool after volume APIs are called. Jovanka Gulicoska (7): Introduce storage lifecycle event APIs conf: add storage_event handling test: implement storage lifecycle event APIs remote: implement storage lifecycle event APIs storage: implement storage lifecycle event APIs event-test: support storage lifecycle event APIs virsh: Introduce virsh-pool command daemon/libvirtd.h | 2 + daemon/remote.c | 207 ++++++++++++++++++++++++++++++- examples/object-events/event-test.c | 73 +++++++++++ include/libvirt/libvirt-storage.h | 93 ++++++++++++++ src/Makefile.am | 5 + src/conf/storage_conf.h | 4 + src/conf/storage_event.c | 235 ++++++++++++++++++++++++++++++++++++ src/conf/storage_event.h | 58 +++++++++ src/datatypes.h | 13 ++ src/driver-storage.h | 13 ++ src/libvirt-storage.c | 125 +++++++++++++++++++ src/libvirt_private.syms | 5 + src/libvirt_public.syms | 6 + src/remote/remote_driver.c | 128 ++++++++++++++++++++ src/remote/remote_protocol.x | 43 ++++++- src/remote_protocol-structs | 16 +++ src/storage/storage_driver.c | 110 +++++++++++++++++ src/test/test_driver.c | 71 +++++++++++ tests/objecteventtest.c | 177 +++++++++++++++++++++++++++ tools/virsh-pool.c | 184 ++++++++++++++++++++++++++++ 20 files changed, 1564 insertions(+), 4 deletions(-) create mode 100644 src/conf/storage_event.c create mode 100644 src/conf/storage_event.h -- 2.5.5

5 16

[libvirt] esx: What does "No storage volume with key or path" mean?
by Richard W.M. Jones 15 Jun '16

15 Jun '16

We've had a report of a particular vCenter server (using VMware clustering, we think) where virStorageVolInfo of a guest volume fails with: Storage volume not found: No storage volume with key or path '[...] ...' The error comes from esxVI_LookupFileInfoByDatastorePath: https://libvirt.org/git/?p=libvirt.git;a=blob;f=src/esx/esx_vi.c;h=f7eeeb5c… What does it mean? The reporter also said they could do some (frankly voodoo) moving guests around and then the error went away. We're not sure if that was just coincidence. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v

1 1

[libvirt] [PATCH] vz: get rid of unused home state variable in private domain obj
by Nikolay Shirokovskiy 15 Jun '16

15 Jun '16

Signed-off-by: Nikolay Shirokovskiy <nshirokovskiy(a)virtuozzo.com> --- src/vz/vz_sdk.c | 16 ---------------- src/vz/vz_utils.h | 1 - 2 files changed, 17 deletions(-) diff --git a/src/vz/vz_sdk.c b/src/vz/vz_sdk.c index 2275572..3fe17e0 100644 --- a/src/vz/vz_sdk.c +++ b/src/vz/vz_sdk.c @@ -447,7 +447,6 @@ prlsdkDomObjFreePrivate(void *p) PrlHandle_Free(pdom->sdkdom); PrlHandle_Free(pdom->cache.stats); virCondDestroy(&pdom->cache.cond); - VIR_FREE(pdom->home); VIR_FREE(p); }; @@ -1484,7 +1483,6 @@ prlsdkLoadDomain(vzDriverPtr driver, virDomainObjPtr dom) virDomainDefPtr def = NULL; vzDomObjPtr pdom = NULL; VIRTUAL_MACHINE_STATE domainState; - char *home = NULL; PRL_RESULT pret; PRL_UINT32 ram; @@ -1541,17 +1539,6 @@ prlsdkLoadDomain(vzDriverPtr driver, virDomainObjPtr dom) pret = PrlVmCfg_GetEnvId(sdkdom, &envId); prlsdkCheckRetGoto(pret, error); - if (!(home = prlsdkGetStringParamVar(PrlVmCfg_GetHomePath, sdkdom))) - goto error; - - /* For VMs home is actually /directory/config.pvs */ - if (!IS_CT(def)) { - /* Get rid of /config.pvs in path string */ - char *s = strrchr(home, '/'); - if (s) - *s = '\0'; - } - pret = PrlVmCfg_GetAutoStart(sdkdom, &autostart); prlsdkCheckRetGoto(pret, error); if (autostart != PAO_VM_START_ON_LOAD && @@ -1588,8 +1575,6 @@ prlsdkLoadDomain(vzDriverPtr driver, virDomainObjPtr dom) virDomainDefFree(dom->def); dom->def = def; pdom->id = envId; - VIR_FREE(pdom->home); - pdom->home = home; prlsdkConvertDomainState(domainState, envId, dom); @@ -1607,7 +1592,6 @@ prlsdkLoadDomain(vzDriverPtr driver, virDomainObjPtr dom) return 0; error: PrlHandle_Free(sdkdom); - VIR_FREE(home); virDomainDefFree(def); return -1; } diff --git a/src/vz/vz_utils.h b/src/vz/vz_utils.h index ba4d3c5..1e2ed30 100644 --- a/src/vz/vz_utils.h +++ b/src/vz/vz_utils.h @@ -103,7 +103,6 @@ typedef struct _vzCountersCache vzCountersCache; struct vzDomObj { int id; - char *home; PRL_HANDLE sdkdom; vzCountersCache cache; }; -- 1.8.3.1

2 1

[libvirt] [PATCH] check-spacing: fix error message
by Ján Tomko 15 Jun '16

15 Jun '16

The check for whitespace before comma or semicolon referred to comma as colon. --- build-aux/check-spacing.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Pushed as trivial. diff --git a/build-aux/check-spacing.pl b/build-aux/check-spacing.pl index f4fedbc..448acf2 100755 --- a/build-aux/check-spacing.pl +++ b/build-aux/check-spacing.pl @@ -138,7 +138,7 @@ foreach my $file (@ARGV) { if ($data =~ /\s[;,]/) { unless ($data =~ /\S; ; / || $data =~ /^\s+;/) { - print "Whitespace before (semi)colon:\n"; + print "Whitespace before semicolon or comma:\n"; print "$file:$.: $line"; $ret = 1; } -- 2.7.3

1 0

[libvirt] [PATCH 0/9] syntax-check: make spacing check faster
by Ján Tomko 15 Jun '16

15 Jun '16

Simplify some regexes to increase coverage and speed up the execution. Reduces (git ls-files "*.c" | xargs build-aux/bracket-spacing.pl) by half a second (from 1.9s to 1.33s), the effect on complete syntax-check is only ~150 ms. Ján Tomko (9): vbox: reformat multi-line error reports maint: remove whitespace from closing parentheses Rename virAssertCmpInt to testAssertEq Rename bracket-spacing.pl to check-spacing.pl check-spacing: rewrite whitespace check before (semi)colon check-spacing: rewrite regex for checking the closing parenthesis check-spacing: simplify keyword spacing check check-spacing: remove virAssertCmpInt exception check-spacing: use non-capturing groups build-aux/bracket-spacing.pl | 204 ------------------------------------------ build-aux/check-spacing.pl | 204 ++++++++++++++++++++++++++++++++++++++++++ cfg.mk | 6 +- src/qemu/qemu_command.c | 3 +- src/vbox/vbox_common.c | 8 +- src/vbox/vbox_snapshot_conf.c | 68 +++++++------- src/vz/vz_driver.c | 3 +- src/vz/vz_sdk.c | 3 +- tests/viratomictest.c | 52 +++++------ 9 files changed, 274 insertions(+), 277 deletions(-) delete mode 100755 build-aux/bracket-spacing.pl create mode 100755 build-aux/check-spacing.pl -- 2.7.3

2 18

[libvirt] [PATCH] maint: Switch to xz compressed PAX release archives
by Andrea Bolognani 15 Jun '16

15 Jun '16

This allows us to produce releases that are roughly a third in size, have no limitation on path lenght, and are still readable by all supported platforms. --- And what better time to switch than the 2.0.0 release? :) configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 0114149..7d16e5a 100644 --- a/configure.ac +++ b/configure.ac @@ -24,7 +24,7 @@ AH_BOTTOM([#include <config-post.h>]) AC_CONFIG_MACRO_DIR([m4]) dnl Make automake keep quiet about wildcards & other GNUmake-isms; also keep dnl quiet about the fact that we intentionally cater to automake 1.9 -AM_INIT_AUTOMAKE([-Wno-portability -Wno-obsolete tar-ustar subdir-objects]) +AM_INIT_AUTOMAKE([-Wno-portability -Wno-obsolete tar-pax no-dist-gzip dist-xz subdir-objects]) dnl older automake's default of ARFLAGS=cru is noisy on newer binutils; dnl we don't really need the 'u' even in older toolchains. Then there is dnl older libtool, which spelled it AR_FLAGS -- 2.5.5

2 1

[libvirt] Bump tar format?
by Andrea Bolognani 15 Jun '16

15 Jun '16

Hi everyone, commit cc3d52e[1] has apparently broken 'make dist' for at least some platforms: Fedora 20 is fine[2], but both Fedora 21 and rawhide[3][4] are currently failing. My laptop is running Fedora 22 and can make dist just fine, which is of course very confusing. The issue is caused by the following tar error: tar: libvirt-1.2.18/tests/nodeinfodata/linux-deconfigured-cpus/ \ node/node0/cpu16/topology/core_siblings_list: \ link name is too long; not dumped There seem to be basically two ways to solve the failure: 1. rename the test case, making it shorter; 2. bump tar format from ustar, which has limitations on the length of file names, to posix/pax, which has no such limitations. I'm not a fan of the former option because short names are usually very opaque, see tests/nodeinfodata/linux-test[0-8] for some perfect examples. On the other hand, I'm not sure whether bumping the tar version would affect portability in a significant way: the automake documentation[5] reports that this format is very young and should probably be restricted to packages that target only very modern platforms but the GNU tar documentation[6], while containing some warnings as well, suggest that this format is going to become the default. Any suggestions on how to proceed? Cheers. [1] https://www.redhat.com/archives/libvir-list/2015-July/msg00662.html [2] https://ci.centos.org/view/libvirt-project/job/libvirt-daemon -rpm/systems=libvirt-fedora-20/327/ [3] https://ci.centos.org/view/libvirt-project/job/libvirt-daemon -rpm/systems=libvirt-fedora-21/327/ [4] https://ci.centos.org/view/libvirt-project/job/libvirt-daemon -rpm/systems=libvirt-fedora-rawhide/327/ [5] https://www.gnu.org/software/automake/manual/html_node/List-of -Automake-options.html [6] http://www.gnu.org/software/tar/manual/html_chapter/tar_8.html -- Andrea Bolognani Software Engineer - Virtualization Team

6 13

[libvirt] [PATCH] virHostCPUGetInfo: Fix build on non-Unix like systems
by Michal Privoznik 15 Jun '16

15 Jun '16

This function is plenty of ifdefs providing implementations for Linux, *BSD and OS-X. However, if we are being build for any other architecture, all that's left behind by preprocessor is just a error reporting call and return of -1. In that case, passed arguments are unused: ../../src/util/virhostcpu.c: In function 'virHostCPUGetInfo': ../../src/util/virhostcpu.c:966:33: error: unused parameter 'cpus' [-Werror=unused-parameter] unsigned int *cpus, ^~~~ Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> --- src/util/virhostcpu.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/util/virhostcpu.c b/src/util/virhostcpu.c index 00c09cd..a481be0 100644 --- a/src/util/virhostcpu.c +++ b/src/util/virhostcpu.c @@ -963,12 +963,12 @@ virHostCPUParseMapLinux(int max_cpuid, const char *path) int virHostCPUGetInfo(virArch hostarch ATTRIBUTE_UNUSED, - unsigned int *cpus, - unsigned int *mhz, - unsigned int *nodes, - unsigned int *sockets, - unsigned int *cores, - unsigned int *threads) + unsigned int *cpus ATTRIBUTE_UNUSED, + unsigned int *mhz ATTRIBUTE_UNUSED, + unsigned int *nodes ATTRIBUTE_UNUSED, + unsigned int *sockets ATTRIBUTE_UNUSED, + unsigned int *cores ATTRIBUTE_UNUSED, + unsigned int *threads ATTRIBUTE_UNUSED) { #ifdef __linux__ int ret = -1; -- 2.8.4

2 1

[libvirt] [PATCH 0/2] Speed up syntax-check
by Ján Tomko 15 Jun '16

15 Jun '16

Remove one inefficient regex not applicable to libvirt codebase and join non-reentrant functions into a single regex to reduce the time taken by the two slowest syntax-checks: 4.03 unmarked_diagnostics 4.03 vulnerable_makefile_CVE-2009-4029 4.03 size_of_brackets 4.03 spec_indentation 4.33 require_config_h_first 5.88 prohibit_nonreentrant 7.72 prohibit_undesirable_word_seq This reduces the overall 'make -j9 syntax-check' time for me from ~8s to ~4.5s. Ján Tomko (2): cfg.mk: override gnulib's undesirable_word_seq check cfg.mk: use a single regex for all non-reentrant functions Makefile.nonreentrant | 8 ++++++++ cfg.mk | 18 ++++++++---------- 2 files changed, 16 insertions(+), 10 deletions(-) -- 2.7.3

2 4

[libvirt] [PATCH] A word error about S3/S4 operations for guest
by sannyshao 15 Jun '16

15 Jun '16

--- docs/formatdomain.html.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 82b6aae..dd9f153 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -1462,7 +1462,7 @@ <dl> <dt><code>pm</code></dt> <dd>These elements enable ('yes') or disable ('no') BIOS support - for S3 (suspend-to-disk) and S4 (suspend-to-mem) ACPI sleep + for S3 (suspend-to-mem) and S4 (suspend-to-disk) ACPI sleep states. If nothing is specified, then the hypervisor will be left with its default value.</dd> </dl> -- 1.8.3.1

2 1

[libvirt] [RFC PATCH 0/4] Add new function about block backup
by Rudy Zhang 15 Jun '16

15 Jun '16

Add new function about block backup, it supports the drive-backup function in qemu, it supports three modes: full, top, incremental. How to use it? As usual, we must do the full backup at first, if it's successfull, next time, we can do the incremental backup, because it has the bitmap to trace the dirty io. The incermental backup is faster. If backup fail at some time, we must do the full backup again, only in this way, we can keep the backup data correctly. Rudy Zhang (4): Introduce virDomainBlockBackup API qemu drive support block backup. virsh: support blockbackup in virsh command libvirt-test: libvirt test supports drive-backup docs/apibuild.py | 3 +- include/libvirt/libvirt-domain.h | 15 ++ src/conf/domain_conf.h | 12 ++ src/driver-hypervisor.h | 9 + src/libvirt-domain.c | 56 ++++++ src/libvirt_public.syms | 5 + src/qemu/qemu_blockjob.c | 2 + src/qemu/qemu_capabilities.c | 4 + src/qemu/qemu_capabilities.h | 5 + src/qemu/qemu_driver.c | 197 +++++++++++++++++++++ src/qemu/qemu_monitor.c | 59 ++++++ src/qemu/qemu_monitor.h | 23 +++ src/qemu/qemu_monitor_json.c | 124 +++++++++++++ src/qemu/qemu_monitor_json.h | 23 +++ src/remote/remote_driver.c | 1 + src/remote/remote_protocol.x | 17 +- src/remote_protocol-structs | 9 + tests/qemucaps2xmldata/all_1.6.0-1.caps | 1 + tests/qemucaps2xmldata/nodisksnapshot_1.6.0-1.caps | 1 + tools/virsh-domain.c | 149 ++++++++++++++++ 20 files changed, 713 insertions(+), 2 deletions(-) -- 2.6.4

4 8

[libvirt] [PATCH 0/6] libxl: add support of pvusb controller
by Chunyan Liu 15 Jun '16

15 Jun '16

This patch series is to add pvusb controller support in libxl driver. It should be applied on previous pvusb device support patch series. Chunyan Liu (6): extend usb controller model to support xen pvusb libxl: support USB controllers in creation time libxl: support usb controller hotplug libxl: check available controller and port when hotplugging USB device xenconfig: add conversion of usb controller config to and from xml xlconfigtest: add test for usb controller conversion docs/formatdomain.html.in | 6 +- docs/schemas/domaincommon.rng | 4 + src/conf/domain_conf.c | 4 + src/conf/domain_conf.h | 4 + src/libxl/libxl_conf.c | 94 +++++++++++++++++ src/libxl/libxl_conf.h | 4 + src/libxl/libxl_driver.c | 176 +++++++++++++++++++++++++++++++ src/qemu/qemu_command.c | 4 + src/xenconfig/xen_xl.c | 203 ++++++++++++++++++++++++++++++++++++ tests/xlconfigdata/test-usbctrl.cfg | 13 +++ tests/xlconfigdata/test-usbctrl.xml | 32 ++++++ tests/xlconfigtest.c | 1 + 12 files changed, 544 insertions(+), 1 deletion(-) create mode 100644 tests/xlconfigdata/test-usbctrl.cfg create mode 100644 tests/xlconfigdata/test-usbctrl.xml -- 2.1.4

5 12

[libvirt] [PATCH V2 0/4] libxl: support pvusb
by Chunyan Liu 14 Jun '16

14 Jun '16

This patch series is to support pvusb in libxl driver. --- Changes in v2: * add LIBXL_HAVE_PVUSB check * add convertion of domxml USB config to/from xl.cfg * address other comments Chunyan Liu (4): libxl: support creating guest with USB hostdev libxl: support hotplug USB host device Add convertion domxml USB config to/from xl.cfg xlconfigtest: add test on USB convertion src/libxl/libxl_conf.c | 74 ++++++++++++++++++++ src/libxl/libxl_conf.h | 5 ++ src/libxl/libxl_domain.c | 16 ++++- src/libxl/libxl_driver.c | 144 +++++++++++++++++++++++++++++++++++++- src/xenconfig/xen_xl.c | 151 ++++++++++++++++++++++++++++++++++++++++ tests/xlconfigdata/test-usb.cfg | 13 ++++ tests/xlconfigdata/test-usb.xml | 35 ++++++++++ tests/xlconfigtest.c | 1 + 8 files changed, 435 insertions(+), 4 deletions(-) create mode 100644 tests/xlconfigdata/test-usb.cfg create mode 100644 tests/xlconfigdata/test-usb.xml -- 2.1.4

4 15

[libvirt] [PATCH V3 0/6] libxl: Add support for UEFI using OVMF
by Jim Fehlig 14 Jun '16

14 Jun '16

This is essentially a V3 of https://www.redhat.com/archives/libvir-list/2016-April/msg01358.html To avoid code duplication in that series, I proposed adding a virFirmware object that could be used by multiple drivers https://www.redhat.com/archives/libvir-list/2016-May/msg01370.html mprivozn ACK'ed that series, but I deferred committing it until 1.3.5 was released since it's not all that useful without accompanying use by another driver. Jim Fehlig (6): driver config: Introduce virFirmware object libxl: add default firmwares to driver config object libxl: introduce libxl_capabilities.{ch} libxl: implement connectGetDomainCapabilities xenconfig: support bios=ovmf xl.cfg libxl: Add support for ovmf firmware po/POTFILES.in | 2 + src/Makefile.am | 12 +- src/libvirt_private.syms | 6 + src/libxl/libxl_capabilities.c | 598 +++++++++++++++++++++++++++++ src/libxl/libxl_capabilities.h | 57 +++ src/libxl/libxl_conf.c | 460 ++-------------------- src/libxl/libxl_conf.h | 22 +- src/libxl/libxl_domain.c | 1 + src/libxl/libxl_driver.c | 75 ++++ src/qemu/qemu_capabilities.c | 22 +- src/qemu/qemu_capabilities.h | 5 +- src/qemu/qemu_conf.c | 127 +----- src/qemu/qemu_conf.h | 7 +- src/qemu/qemu_driver.c | 2 +- src/qemu/qemu_process.c | 6 +- src/util/virfirmware.c | 137 +++++++ src/util/virfirmware.h | 51 +++ src/xenconfig/xen_xl.c | 37 +- tests/Makefile.am | 5 + tests/domaincapsschemadata/libxl-xenfv.xml | 68 ++++ tests/domaincapsschemadata/libxl-xenpv.xml | 58 +++ tests/domaincapstest.c | 64 ++- tests/testutils.c | 16 + tests/testutils.h | 2 + tests/testutilsxen.h | 1 + tests/xlconfigdata/test-fullvirt-ovmf.cfg | 26 ++ tests/xlconfigdata/test-fullvirt-ovmf.xml | 58 +++ tests/xlconfigtest.c | 90 ++++- 28 files changed, 1415 insertions(+), 600 deletions(-) create mode 100644 src/libxl/libxl_capabilities.c create mode 100644 src/libxl/libxl_capabilities.h create mode 100644 src/util/virfirmware.c create mode 100644 src/util/virfirmware.h create mode 100644 tests/domaincapsschemadata/libxl-xenfv.xml create mode 100644 tests/domaincapsschemadata/libxl-xenpv.xml create mode 100644 tests/xlconfigdata/test-fullvirt-ovmf.cfg create mode 100644 tests/xlconfigdata/test-fullvirt-ovmf.xml -- 2.1.4

4 14

[libvirt] [PATCH python 0/2] Bindings for storage pool lifecycle events
by Jovanka Gulicoska 14 Jun '16

14 Jun '16

Python buindings and tests for storage pool lifecycle events API. Function storageDetailToString() is not implemented for now. Jovanka Gulicoska (2): Python binding for storage pool lifecycle events API event-test: Add storage pool lifecycle event tests examples/event-test.py | 18 +++++ generator.py | 2 + libvirt-override-virConnect.py | 35 ++++++++++ libvirt-override.c | 153 +++++++++++++++++++++++++++++++++++++++++ sanitytest.py | 3 +- 5 files changed, 210 insertions(+), 1 deletion(-) -- 2.5.5

3 7

[libvirt] [PATCH] virt-host-validate: improve tests for arm/aarch64
by Riku Voipio 14 Jun '16

14 Jun '16

ARM/Aarch64 /proc/cpuinfo has no virtualization related flags. Refactor the Qemu/KVM test a bit: 1) run the "for hardware virtualization" test only on plaforms with known cpuinfo flags (x86, s390) 2) test for /dev/kvm also on platforms where no cpu flags are set Finally Add a more generic error hint message for non-x86 plaforms when /dev/kvm is missing. Signed-off-by: Riku Voipio <riku.voipio(a)linaro.org> --- tools/virt-host-validate-qemu.c | 29 ++++++++++++++++++++--------- 1 file changed, 20 insertions(+), 9 deletions(-) diff --git a/tools/virt-host-validate-qemu.c b/tools/virt-host-validate-qemu.c index 56ec3c7..520c8ed 100644 --- a/tools/virt-host-validate-qemu.c +++ b/tools/virt-host-validate-qemu.c @@ -32,8 +32,9 @@ int virHostValidateQEMU(void) virBitmapPtr flags; int ret = 0; bool hasHwVirt = false; - - virHostMsgCheck("QEMU", "%s", _("for hardware virtualization")); + bool hasVirtFlag = false; + char *kvmhint = _("Check that CPU and firmware supports virtualization " + "and kvm module is loaded"); if (!(flags = virHostValidateGetCPUFlags())) return -1; @@ -41,12 +42,16 @@ int virHostValidateQEMU(void) switch (virArchFromHost()) { case VIR_ARCH_I686: case VIR_ARCH_X86_64: + hasVirtFlag = true; + kvmhint =_("Check that the 'kvm-intel' or 'kvm-amd' modules are " + "loaded & the BIOS has enabled virtualization"); if (virBitmapIsBitSet(flags, VIR_HOST_VALIDATE_CPU_FLAG_SVM) || virBitmapIsBitSet(flags, VIR_HOST_VALIDATE_CPU_FLAG_VMX)) hasHwVirt = true; break; case VIR_ARCH_S390: case VIR_ARCH_S390X: + hasVirtFlag = true; if (virBitmapIsBitSet(flags, VIR_HOST_VALIDATE_CPU_FLAG_SIE)) hasHwVirt = true; break; @@ -54,21 +59,27 @@ int virHostValidateQEMU(void) hasHwVirt = false; } - if (hasHwVirt) { - virHostMsgPass(); + if (hasVirtFlag) { + virHostMsgCheck("QEMU", "%s", _("for hardware virtualization")); + if (hasHwVirt) + virHostMsgPass(); + else { + virHostMsgFail(VIR_HOST_VALIDATE_FAIL, + _("Only emulated CPUs are available, performance will be significantly limited")); + ret = -1; + } + } + + if (hasHwVirt || !hasVirtFlag) { if (virHostValidateDeviceExists("QEMU", "/dev/kvm", VIR_HOST_VALIDATE_FAIL, - _("Check that the 'kvm-intel' or 'kvm-amd' modules are " - "loaded & the BIOS has enabled virtualization")) < 0) + kvmhint) <0) ret = -1; else if (virHostValidateDeviceAccessible("QEMU", "/dev/kvm", VIR_HOST_VALIDATE_FAIL, _("Check /dev/kvm is world writable or you are in " "a group that is allowed to access it")) < 0) ret = -1; - } else { - virHostMsgFail(VIR_HOST_VALIDATE_WARN, - _("Only emulated CPUs are available, performance will be significantly limited")); } virBitmapFree(flags); -- 2.1.4

3 5

[libvirt] [PATCH python] Post-release version bump to 2.0.0
by Daniel P. Berrange 14 Jun '16

14 Jun '16

Signed-off-by: Daniel P. Berrange <berrange(a)redhat.com> --- Pushed under trivial rule. setup.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup.py b/setup.py index 956609d..099b1e0 100755 --- a/setup.py +++ b/setup.py @@ -305,7 +305,7 @@ class my_clean(clean): _c_modules, _py_modules = get_module_lists() setup(name = 'libvirt-python', - version = '1.3.5', + version = '2.0.0', url = 'http://www.libvirt.org', maintainer = 'Libvirt Maintainers', maintainer_email = 'libvir-list(a)redhat.com', -- 2.5.5

1 0