- Devel - libvirt List Archives

[libvirt] [PATCH 2/2] Add new elements source, access and allocation
by Safka, JaroslavX 21 Jun '16

21 Jun '16

This change introduces support for preallocated shared file descriptor based memory backing. It allows vhost-user to be used without hugepages. This is achieved by introducing 3 new sub elements to the memoryBacking element: source, access & allocation which will configure qemu commandline during VM startup accordingly. First patch adds parsing of elements and storing the values in mem structure. Second patch configures the qemu commandline on the base of values in mem structure. -------------------------------------------------------------- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

2 1

[libvirt] [PATCH 0/7] Add APIs for individual vCPU state modification using the guest agent
by Peter Krempa 21 Jun '16

21 Jun '16

As a first step, add the guest-agent part. The real hotplug stuff will follow shortly. Please note that the setter API will be used as template for the real stuff too. Peter Krempa (7): rpcgen: Add support for generating funcs returning alloc'd typed params lib: Add API to query guest vcpu info using guest agent lib: Add API to set individual vcpu usage in the guest via guest agent virsh: Add command 'guestvcpus' implementing virDomain(GS)etGuestVcpus qemu: agent: Make setting of vcpus more robust qemu: Implement virDomainGetGuestVcpus qemu: Implement virDomainSetGuestVcpus include/libvirt/libvirt-domain.h | 10 ++ src/driver-hypervisor.h | 14 +++ src/libvirt-domain.c | 105 ++++++++++++++++++++ src/libvirt_public.syms | 2 + src/qemu/qemu_agent.c | 83 +++++++++++++--- src/qemu/qemu_agent.h | 2 + src/qemu/qemu_driver.c | 210 ++++++++++++++++++++++++++++++++++++--- src/remote/remote_driver.c | 2 + src/remote/remote_protocol.x | 39 +++++++- src/remote_protocol-structs | 18 ++++ src/rpc/gendispatch.pl | 45 ++++++++- tests/qemuagenttest.c | 44 ++++---- tools/virsh-domain.c | 93 +++++++++++++++++ tools/virsh.pod | 10 ++ 14 files changed, 625 insertions(+), 52 deletions(-) -- 2.8.3

2 15

[libvirt] [PATCH v2] There are several cases where we do not handle transient pool destroy and cleanup correctly. For example:
by Jovanka Gulicoska 21 Jun '16

21 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1227475 Move the pool cleanup logic to a new function storagePoolSetInactive and use it consistently. --- src/storage/storage_driver.c | 43 +++++++++++++++++++++++-------------------- 1 file changed, 23 insertions(+), 20 deletions(-) diff --git a/src/storage/storage_driver.c b/src/storage/storage_driver.c index e2d729f..2f29292 100644 --- a/src/storage/storage_driver.c +++ b/src/storage/storage_driver.c @@ -77,6 +77,21 @@ static void storageDriverUnlock(void) } static void +storagePoolSetInactive(virStoragePoolObjPtr *pool) +{ + (*pool)->active = false; + + if ((*pool)->configFile == NULL) { + virStoragePoolObjRemove(&driver->pools, (*pool)); + *pool = NULL; + } else if ((*pool)->newDef) { + virStoragePoolDefFree((*pool)->def); + (*pool)->def = (*pool)->newDef; + (*pool)->newDef = NULL; + } +} + +static void storagePoolUpdateState(virStoragePoolObjPtr pool) { bool active; @@ -115,16 +130,19 @@ storagePoolUpdateState(virStoragePoolObjPtr pool) if (backend->refreshPool(NULL, pool) < 0) { if (backend->stopPool) backend->stopPool(NULL, pool); + active = false; virReportError(VIR_ERR_INTERNAL_ERROR, _("Failed to restart storage pool '%s': %s"), pool->def->name, virGetLastErrorMessage()); goto error; } + active = true; } - pool->active = active; ret = 0; error: + if (!active) + storagePoolSetInactive(&pool); if (ret < 0) { if (stateFile) unlink(stateFile); @@ -198,6 +216,7 @@ storageDriverAutostart(void) unlink(stateFile); if (backend->stopPool) backend->stopPool(conn, pool); + storagePoolSetInactive(&pool); virReportError(VIR_ERR_INTERNAL_ERROR, _("Failed to autostart storage pool '%s': %s"), pool->def->name, virGetLastErrorMessage()); @@ -737,8 +756,7 @@ storagePoolCreateXML(virConnectPtr conn, unlink(stateFile); if (backend->stopPool) backend->stopPool(conn, pool); - virStoragePoolObjRemove(&driver->pools, pool); - pool = NULL; + storagePoolSetInactive(&pool); goto cleanup; } @@ -1068,16 +1086,7 @@ storagePoolDestroy(virStoragePoolPtr obj) VIR_STORAGE_POOL_EVENT_STOPPED, 0); - pool->active = false; - - if (pool->configFile == NULL) { - virStoragePoolObjRemove(&driver->pools, pool); - pool = NULL; - } else if (pool->newDef) { - virStoragePoolDefFree(pool->def); - pool->def = pool->newDef; - pool->newDef = NULL; - } + storagePoolSetInactive(&pool); ret = 0; @@ -1197,13 +1206,7 @@ storagePoolRefresh(virStoragePoolPtr obj, pool->def->uuid, VIR_STORAGE_POOL_EVENT_STOPPED, 0); - pool->active = false; - - if (pool->configFile == NULL) { - virStoragePoolObjRemove(&driver->pools, pool); - pool = NULL; - } - goto cleanup; + storagePoolSetInactive(&pool); } event = virStoragePoolEventLifecycleNew(pool->def->name, -- 2.5.5

2 1

[libvirt] [PATCH 0/8] Add --in-place and --check to test-wrap-argv
by Ján Tomko 21 Jun '16

21 Jun '16

The --in-place parameter makes the invocation in testutils slightly nicer and --check makes syntax-check faster. Ján Tomko (8): test-wrap-argv: split out rewrap_line test-wrap-argv: split out rewrap_arg test-wrap-argv: return a string in rewrap_arg test-wrap-argv: use map and join instead of a for cycle test-wrap-argv: return a string in rewrap_line test-wrap-argv: hold a copy of the original file in an array test-wrap-argv: add --in-place parameter test-wrap-argv: add --check parameter cfg.mk | 12 +--- tests/test-wrap-argv.pl | 170 ++++++++++++++++++++++++++++++------------------ tests/testutils.c | 8 +-- 3 files changed, 108 insertions(+), 82 deletions(-) -- 2.7.3

2 10

[libvirt] libvirt and VIR_WARN("cannot parse process status data")
by Vasiliy Tolstov 21 Jun '16

21 Jun '16

I have system with 3.19.3 kernel and libvirt 1.3.3 (version not matter because part of code not changed). When i'm try to get cpu stats via libvirt i have error in libvirt log, that says "cannot parse process status data" relevant code in src/qemu/qemu_driver.c in function qemuGetProcessInfo i'm add debut test to this function and in my case i have always fscanf != 4 qemu pid 7977 cat /proc/7977/stat 7977 (qemu-system-x86) S 1 7976 7976 0 -1 138420608 12728 0 0 0 4819 8249 0 0 20 0 7 0 51378692 4783886336 75779 18446744073709551615 139849472311296 139849478294132 140732912418880 140732912417952 139849400618495 0 268444224 4096 16963 18446744073709551615 0 0 17 5 0 0 15624 744 0 139849480394624 139849482248448 139849496641536 140732912421083 140732912422775 140732912422775 140732912422876 0 cat /proc/7977/task/7977/stat 7977 (qemu-system-x86) S 1 7976 7976 0 -1 138420608 12537 0 0 0 3917 7799 0 0 20 0 7 0 51378692 4783886336 75779 18446744073709551615 139849472311296 139849478294132 140732912418880 140732912417952 139849400618495 0 268444224 4096 16963 0 0 0 17 3 0 0 15624 0 0 139849480394624 139849482248448 139849496641536 140732912421083 140732912422775 140732912422775 140732912422876 0 cat /proc/7977/task/7979/stat 7979 (qemu-system-x86) S 1 7976 7976 0 -1 1077944384 20 0 0 0 0 0 0 0 20 0 7 0 51378696 4783886336 75779 18446744073709551615 139849472311296 139849478294132 140732912418880 139849260591832 139849400637449 0 2147221247 4096 16963 0 0 0 -1 6 0 0 0 0 0 139849480394624 139849482248448 139849496641536 140732912421083 140732912422775 140732912422775 140732912422876 0 cat /proc/7977/task/7982/stat 7982 (CPU 0/KVM) S 1 7976 7976 0 -1 138420416 22 0 0 0 226 118 0 0 20 0 7 0 51378697 4783886336 75779 18446744073709551615 139849472311296 139849478294132 140732912418880 139849222842936 139849400624151 0 2147220671 4096 16963 0 0 0 -1 5 0 0 0 196 0 139849480394624 139849482248448 139849496641536 140732912421083 140732912422775 140732912422775 140732912422876 0 Does somebody have time to fix this ? -- Vasiliy Tolstov, e-mail: v.tolstov(a)yoctocloud.net

2 1

[libvirt] [PATCH 0/3] Remove unused macros
by Ján Tomko 21 Jun '16

21 Jun '16

Ján Tomko (3): Remove unused SOL_NETLINK macro vbox: remove duplicate macros vsh: remove namespace poisoning src/util/virnetlink.c | 4 ---- src/vbox/vbox_driver.c | 2 -- src/vbox/vbox_network.c | 43 ------------------------------------------- tools/vsh.c | 6 ------ tools/vsh.h | 10 ---------- 5 files changed, 65 deletions(-) -- 2.7.3

2 8

[libvirt] [PATCH v5 0/3] qemu: expand domain memory statistics
by Maxim Nestratov 21 Jun '16

21 Jun '16

Changes since v1: * Enum numeration fixed * Macro getting "usage" field fixed Changes since v2: * previous patches were on wrong branch * qemu's stat name was "stat-available-memory" Changes since v3: * 3rd patch added Changes since v4: * Formatted and rephrased commit messages * fixed libvirt crash, caused by simultaneous incorrect QUERY job execution Derbyshev Dmitry (3): qemu: expand domain memory statistics with 'usable' qemu: expand domain memory statistics with 'last-update' timestamp qemu: return balloon statistics when all domain statistics reported include/libvirt/libvirt-domain.h | 11 ++++- src/libvirt-domain.c | 5 +++ src/qemu/qemu_driver.c | 95 +++++++++++++++++++++++++++++++--------- src/qemu/qemu_monitor_json.c | 24 ++++++---- tools/virsh-domain-monitor.c | 4 ++ 5 files changed, 108 insertions(+), 31 deletions(-) -- 2.4.3

2 6

[libvirt] qemu: cpu model definition problem
by Maxim Nestratov 21 Jun '16

21 Jun '16

Hi all, I've just encountered a problem with ability to live migrate a VM between hosts using the following cpu section in VM's xml: <cpu mode='custom' match='exact'> <model fallback='allow'>Haswell-noTSX</model> ... <feature policy='disable' name='rdrand'/> </cpu> The problem is that a VM with such a config crashes when it migrates from a host where 'rdrand' presents to a host where it is absent. This happens due to the fact that QEMU and libvirt have pretty different view on what 'Haswell-noTSX' is. Libvirt's description lacks some features, which present in QEMU description of this cpu model (e.g. 'rdrand'). It is impossible to disable features present on the host and different from QEMU's ones by current libvirt code, i.e. libvirt thinks that no use to disable something that doesn't exist. Of course, the problem in this case can be fixed just by adding missed features to 'Haswell-noTSX' model in cpu_map.xml to match what QEMU has, but it doesn't seem right because it will help just in this particular case, and in general, it will not be a solution because QEMU can change its cpu model definitions at any time and it does this from time to time. What libvirt might have done is: - either ask QEMU for cpu model definition and work with it, - or construct a command line for QEMU with required and disabled features without taking into account libvirt cpu_map.xml, i.e. always add '+xx' and '-yy' for features mentioned explicitly in domain xml. What do you think? Maxim

2 2

[libvirt] [PATCH] qemu: Fix typo pci-extender-bus -> pci-expander-bus
by Andrea Bolognani 21 Jun '16

21 Jun '16

--- Pushed as trivial. src/qemu/qemu_domain_address.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/qemu/qemu_domain_address.c b/src/qemu/qemu_domain_address.c index 883264a..f42e7c0 100644 --- a/src/qemu/qemu_domain_address.c +++ b/src/qemu/qemu_domain_address.c @@ -1382,7 +1382,7 @@ qemuDomainAddressFindNewBusNr(virDomainDefPtr def) * bus and busNr of the next highest bus for the guest to assign a * unique bus number to each PCI bus that is a child of this * bus. Each PCI controller. On top of this, the pxb device (which - * implements the pci-extender-bus) includes a pci-bridge within + * implements the pci-expander-bus) includes a pci-bridge within * it, and that bridge also uses one bus number (so each pxb device * requires at least 2 bus numbers). * -- 2.7.4

1 0

[libvirt] [PATCH] virsh migrate: Fix positional parameters
by Jiri Denemark 21 Jun '16

21 Jun '16

Thanks to our smart option parser which automatically assigns positional parameters the following (previously working) command fails: virsh migrate test qemu+ssh://1.2.3.4/system tcp://1.2.3.4/ error: invalid argument: Unsupported compression method 'tcp://1.2.3.4/' We need to make sure new options are added at the end of the list rather than where they logically belong. Reported by Brian Rak. Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com> --- tools/virsh-domain.c | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/tools/virsh-domain.c b/tools/virsh-domain.c index 02be58f..19c40b3 100644 --- a/tools/virsh-domain.c +++ b/tools/virsh-domain.c @@ -9792,26 +9792,6 @@ static const vshCmdOptDef opts_migrate[] = { .type = VSH_OT_BOOL, .help = N_("compress repeated pages during live migration") }, - {.name = "comp-methods", - .type = VSH_OT_STRING, - .help = N_("comma separated list of compression methods to be used") - }, - {.name = "comp-mt-level", - .type = VSH_OT_INT, - .help = N_("compress level for multithread compression") - }, - {.name = "comp-mt-threads", - .type = VSH_OT_INT, - .help = N_("number of compression threads for multithread compression") - }, - {.name = "comp-mt-dthreads", - .type = VSH_OT_INT, - .help = N_("number of decompression threads for multithread compression") - }, - {.name = "comp-xbzrle-cache", - .type = VSH_OT_INT, - .help = N_("page cache size for xbzrle compression") - }, {.name = "auto-converge", .type = VSH_OT_BOOL, .help = N_("force convergence during live migration") @@ -9873,6 +9853,26 @@ static const vshCmdOptDef opts_migrate[] = { .type = VSH_OT_INT, .help = N_("port to use by target server for incoming disks migration") }, + {.name = "comp-methods", + .type = VSH_OT_STRING, + .help = N_("comma separated list of compression methods to be used") + }, + {.name = "comp-mt-level", + .type = VSH_OT_INT, + .help = N_("compress level for multithread compression") + }, + {.name = "comp-mt-threads", + .type = VSH_OT_INT, + .help = N_("number of compression threads for multithread compression") + }, + {.name = "comp-mt-dthreads", + .type = VSH_OT_INT, + .help = N_("number of decompression threads for multithread compression") + }, + {.name = "comp-xbzrle-cache", + .type = VSH_OT_INT, + .help = N_("page cache size for xbzrle compression") + }, {.name = NULL} }; -- 2.9.0

3 3