[libvirt] [PATCH v2 0/8] libxl: domain statistics support

Hey, This series bring support for various statistics about domains regarding CPU, Memory, Network Interfaces, Block and Jobs. Not all of the statistics are implemented: qdisk support is missing in this series and some of the memory statistics aren't available. With this series we further

[libvirt] [PATCH v2 3/8] libxl: implement virDomainInterfaceStats

Introduce support for domainInterfaceStats API call for querying network interface statistics. Consequently it also enables the use of `virsh domifstat ` command. After succesful guest creation we fill the network interfaces names based on domain, device id and append suffix if it's emulated in

[libvirt] [PATCH v2] libxl: add p2p migration

Introduce support for VIR_MIGRATE_PEER2PEER in libxl driver for supporting migration in Openstack. Most of the changes occur at the source and no modifications at the receiver. In P2P mode there is only the Perform phase so we must handle the connection with the destination and actually perform

[libvirt] [PATCH v2 1/8] libxl: implement virDomainGetCPUStats

Introduce support for domainGetCPUStats API call and consequently allow us to use `virsh cpu-stats`. The latter returns a more brief output than the one provided by`virsh vcpuinfo`. Signed-off-by: Joao Martins --- Changes since v1: - Remove libxl_vcpuinfo_dispose() in

Re: [libvirt] [PATCH 1/2] conf: add crash to hyperv features

On 11/10/2015 06:55 PM, Dmitry Andreev wrote: Paolo, Jiri, can I do something more for this patch to be accepted? On 05.11.2015 17:32, Paolo Bonzini wrote: On 05/11/2015 14:54, Dmitry Andreev wrote: Add crash CPU feature for Hyper-V. Hyper-V crash MSR's can be used by Hyper-V based guests to

[libvirt] Issue with Parallel/VZ driver on Parallel Cloud Server 6.0

Hello, I've been tasked with integrating libvirt into a server running Parallel Cloud Server 6.0. However, it seems I've ran into some trouble getting the vz/parallel driver to compile. It appears there might be an issue with the version of parallels-virtualization-sdk thats installed

Re: [libvirt] [PATCH 1/2] conf: add crash to hyperv features

Paolo, Jiri, can I do something more for this patch to be accepted? On 05.11.2015 17:32, Paolo Bonzini wrote: On 05/11/2015 14:54, Dmitry Andreev wrote: Add crash CPU feature for Hyper-V. Hyper-V crash MSR's can be used by Hyper-V based guests to notify about occurred guest crash. XML:

[libvirt] [PATCH v2 0/7] Allow memory hotplug without NUMA on ppc64

This fixes most of the stuff pointed out in the review. Peter Krempa (7): qemu: command: Make qemuBuildMemoryBackendStr usable without NUMA qemu: command: Always execute memory device formatter qemu: domain: Add common function to perform memory hotplug checks qemu: command: Move dimm

[libvirt] [PATCH v2 7/7] qemu: ppc64: Support memory hotplug without NUMA enabled

ppc64 guests don't require adding a NUMA node for hotplug memory to work. Lift the requirement and add test cases. --- src/qemu/qemu_domain.c | 32 ++ .../qemuxml2argv-memory-hotplug-ppc64-nonuma.args | 28

[libvirt] [PATCH v2 1/7] qemu: command: Make qemuBuildMemoryBackendStr usable without NUMA

Make the function usable so that -1 can be passed to it as cell ID so that we can later enable memory hotplug on non-NUMA guests for certain architectures. --- src/qemu/qemu_command.c | 32 1 file changed, 20 insertions(+), 12 deletions(-) diff --git

[libvirt] [PATCH v2 2/7] qemu: command: Always execute memory device formatter

Since we already make sure before that the domain configuration is valid we may execute it always at the cost of doing 0 iterations of the for loop. This patch will simplify later refactor as it will avoid whitespace changes. --- src/qemu/qemu_command.c | 47

[libvirt] [PATCH v2 5/7] conf: Prepare making memory device target node optional

Adjust the config code so that it does not enforce that target memory node is specified. To avoid breakage, adjust the qemu memory hotplug config checker to disallow such config for now. --- docs/formatdomain.html.in | 5 +++-- docs/schemas/domaincommon.rng | 8 +---

[libvirt] [PATCH v2 7/8] libxl: implement virDomainGetJobInfo

Introduce support for domainGetJobInfo to get info about the ongoing job. If the job is active it will update the timeElapsed which is computed with the "started" field added to struct libxlDomainJobObj. For now we support just the very basic info and all jobs have VIR_DOMAIN_JOB_UNBOUNDED (i.e.

[libvirt] [PATCH v2 5/8] libxl: implement virDomainBlockStats

Introduce initial support for domainBlockStats API call that allow us to query block device statistics. openstack nova uses this API call to query block statistics, alongside virDomainMemoryStats and virDomainInterfaceStats. Note that this patch only introduces it for VBD for starters. QDisk will

[libvirt] [PATCH v2 4/8] util: add virDiskNameParse to handle disk and partition idx

Introduce a new helper function "virDiskNameParse" which extends virDiskNameToIndex but handling both disk index and partition index. Also rework virDiskNameToIndex to be based on virDiskNameParse. A test is also added for this function testing both valid and invalid disk names. Signed-off-by:

[libvirt] [PATCH v2 2/8] libxl: implement virDomainMemorystats

Introduce support for domainMemoryStats API call, which consequently enables the use of `virsh dommemstat` command to query for memory statistics of a domain. We support the following statistics: balloon info, available and currently in use. swap-in, swap-out, major-faults, minor-faults require

[libvirt] [PATCH v2 8/8] libxl: implement virDomainGetJobStats

Introduces support for domainGetJobStats which has the same info as domainGetJobInfo but in a slightly different format. Another difference is that virDomainGetJobStats can also retrieve info on the most recently completed job. Though so far this is only used in the source node to know if the

Re: [libvirt] [PATCH] vz: implement memory setting functions in driver

On Thu, 2015-11-05 at 13:13 +0300, Nikolay Shirokovskiy wrote: > Implement functions for vz containers only. vz VMs memory > managment thru libvirt yet to be designed. > > vz memory management for containers is rather different from other > drivers. > > 1. Whole bunch of memory settings

[libvirt] [PATCH v2 4/7] qemu: command: Move dimm device checks from formatter to checker

Aggregate the checks of the dimm device into the verification function rather than having them in the formatter. --- src/qemu/qemu_command.c | 65 ++ src/qemu/qemu_command.h | 4 +-- src/qemu/qemu_domain.c | 92 -

Re: [libvirt] [PATCH] qemu: process: Fix automatic setting of locked memory limit for VFIO

On Fri, 2015-11-06 at 08:30 +0100, Peter Krempa wrote: > On Thu, Nov 05, 2015 at 08:41:46 -0700, Alex Williamson wrote: > > On Thu, 2015-11-05 at 16:27 +0100, Peter Krempa wrote: > > > On Wed, Nov 04, 2015 at 17:16:53 -0700, Alex Williamson wrote: > > [...] > > > The power devs will need to

Re: [libvirt] [PATCH] hypervisor driver for Jailhouse

I'm sorry, I completely forgot the virCommandFree calls: diff --git a/src/jailhouse/jailhouse_driver.c b/src/jailhouse/jailhouse_driver.c index 21acbba..9f1ed70 100644 --- a/src/jailhouse/jailhouse_driver.c +++ b/src/jailhouse/jailhouse_driver.c @@ -201,6 +201,7 @@ parseListOutput(virConnectPtr

[libvirt] [PATCH v2 3/7] qemu: domain: Add common function to perform memory hotplug checks

Add a function that will aggregate various checks related to memory hotplug so that they aren't scattered accross various parts of the code. --- src/qemu/qemu_command.c | 26 ++--- src/qemu/qemu_domain.c | 78 + src/qemu/qemu_domain.h

[libvirt] [PATCH v2 6/7] qemu: command: Prepare memory device def formatter for missing target node

Prepare the command line generator for the possibility that in some configurations the target NUMA node info will be missing. --- src/qemu/qemu_command.c | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/src/qemu/qemu_command.c b/src/qemu/qemu_command.c index

[libvirt] [PATCH v2 6/8] libxl: implement virConnectGetAllDomainStats

Introduce support for connectGetAllDomainStats call that allow us to _all_ domain(s) statistics including network, block, cpus and memory. Changes are rather mechanical and mostly take care of the format to export the data. Signed-off-by: Joao Martins --- Changes since

Re: [libvirt] [PATCH] vz: implement memory setting functions in driver

On Thu, 2015-11-05 at 13:13 +0300, Nikolay Shirokovskiy wrote: > Implement functions for vz containers only. vz VMs memory > managment thru libvirt yet to be designed. > > vz memory management for containers is rather different from other > drivers. > > 1. Whole bunch of memory settings

[libvirt] Abstracting device address allocation

Hello, I am undergraduate computer science student in india .I am new to opensource and i want to contribute to project abstracting device address allocation . I have good knowledge of c . please suggest me how i contribute to this. Regards PriyanshuJain -- libvir-list mailing list

Re: [libvirt] [PATCH v2 02/17] qemu: remove all support for kQEMU

On 11/09/2015 09:24 AM, Daniel P. Berrange wrote: > The kQEMU accelerator was deleted in QEMU 0.12, so we no > longer need to support it in the QEMU driver. > > Signed-off-by: Daniel P. Berrange > --- > src/qemu/qemu_capabilities.c | 18 -- >

Re: [libvirt] [PATCH 1/2] conf: add crash to hyperv features

"Denis V. Lunev" writes: > On 11/10/2015 06:55 PM, Dmitry Andreev wrote: >> Paolo, Jiri, can I do something more for this patch to be accepted? >> >> On 05.11.2015 17:32, Paolo Bonzini wrote: >>> >>> On 05/11/2015 14:54, Dmitry Andreev wrote: >> Add crash CPU feature for

Re: [libvirt] Issue with Parallel/VZ driver on Parallel Cloud Server 6.0

10.11.2015 19:32, Frank Laszlo пишет: Hello, I've been tasked with integrating libvirt into a server running Parallel Cloud Server 6.0. However, it seems I've ran into some trouble getting the vz/parallel driver to compile. It appears there might be an issue with the version of

Re: [libvirt] [PATCH v2 08/17] qemu: assume -drive argument is always available

On Mon, Nov 09, 2015 at 06:24:07PM -0500, John Ferlan wrote: > > > On 11/09/2015 11:24 AM, Daniel P. Berrange wrote: > > As of QEMU 0.9.1 the -drive argument can be used to configure > > all disks, so the QEMU driver can assume it is always available > > and drop support for -hda/-cdrom/etc. > >

Re: [libvirt] [PATCH v2 11/17] qemu: really remove last traces of Xenner support

On Mon, Nov 09, 2015 at 06:24:37PM -0500, John Ferlan wrote: > > > On 11/09/2015 11:24 AM, Daniel P. Berrange wrote: > > We have twice previously attempted to remove Xenner > > support > > > > commit de9be0ab4d7abe4c3ae5beaaff7ddb208921f1f1 > > Author: Daniel P. Berrange

Re: [libvirt] [PATCH v2 1/3] qemu: Extract logic to determine the mlock limit size for VFIO

On Mon, Nov 09, 2015 at 01:09:59PM -0500, John Ferlan wrote: > > > On 11/09/2015 07:50 AM, Peter Krempa wrote: > > New function qemuDomainGetMlockLimitBytes will now handle the > > calculation so that it unifies the logic to one place and allows later > > reuse. > > --- > >

Re: [libvirt] [PATCH v2 00/17] Drop support for QEMU < 0.12.0

On Mon, Nov 09, 2015 at 06:37:06PM -0500, John Ferlan wrote: > > > On 11/09/2015 11:24 AM, Daniel P. Berrange wrote: > > A v2 of this series: > > > > https://www.redhat.com/archives/libvir-list/2015-November/msg00165.html > > > > The patches for introducing virtlogd will be significantly > >

Re: [libvirt] [PATCH v2 17/17] qemu: assume various QEMU 0.10 features are always available

On Mon, Nov 09, 2015 at 06:28:03PM -0500, John Ferlan wrote: > > > On 11/09/2015 11:24 AM, Daniel P. Berrange wrote: > > The -sdl and -net ...name=XXX arguments were both introduced > > in QEMU 0.10, so the QEMU driver can assume they are always > > available. > > > > The -sdl wasn't really

[libvirt] libvirt-snmp development

Hi all, There were no active develoment in libvirt-snmp subproject for a while. Taking this into account I want to ask the following. If we are, here in Virtuozzo, interested in extending this subproject, will there be support from project maintainers in doing this or not? Maxim Nestratov

Re: [libvirt] libvirt-snmp development

On Tue, Nov 10, 2015 at 12:18:14PM +0300, Maxim Nestratov wrote: > Hi all, > > There were no active develoment in libvirt-snmp subproject for a while. > Taking this into account I want to ask the following. > If we are, here in Virtuozzo, interested in extending this subproject, will > there be

Re: [libvirt] libvirt-snmp development

10.11.2015 12:23, Daniel P. Berrange пишет: On Tue, Nov 10, 2015 at 12:18:14PM +0300, Maxim Nestratov wrote: Hi all, There were no active develoment in libvirt-snmp subproject for a while. Taking this into account I want to ask the following. If we are, here in Virtuozzo, interested in

Re: [libvirt] [PATCH v2 13/17] qemu: assume support for all migration protocols except rdma

On Mon, Nov 09, 2015 at 06:27:02PM -0500, John Ferlan wrote: > > > On 11/09/2015 11:24 AM, Daniel P. Berrange wrote: > > Since we require QEMU 0.12.0, we can assume that QEMU supports > > all of the fd, tcp, unix and exec migration protocols. > > > > Signed-off-by: Daniel P. Berrange

Re: [libvirt] libvirt-snmp development

On Tue, Nov 10, 2015 at 12:40:36PM +0300, Maxim Nestratov wrote: 10.11.2015 12:23, Daniel P. Berrange пишет: On Tue, Nov 10, 2015 at 12:18:14PM +0300, Maxim Nestratov wrote: Hi all, There were no active develoment in libvirt-snmp subproject for a while. Taking this into account I want to ask

Re: [libvirt] [PATCH v2 0/3] qemu: Fix mlock limit on memory hotplug

On Mon, Nov 09, 2015 at 13:50:14 +0100, Peter Krempa wrote: > Peter Krempa (3): > qemu: Extract logic to determine the mlock limit size for VFIO > qemu: hotplug: Fix mlock limit handling on memory hotplug > qemu: hotplug: Reject VFIO hotplug if setting RLIMIT_MEMLOCK fails > >

Re: [libvirt] libvirt-snmp development

10.11.2015 13:36, Martin Kletzander пишет: On Tue, Nov 10, 2015 at 12:40:36PM +0300, Maxim Nestratov wrote: 10.11.2015 12:23, Daniel P. Berrange пишет: On Tue, Nov 10, 2015 at 12:18:14PM +0300, Maxim Nestratov wrote: Hi all, There were no active develoment in libvirt-snmp subproject for a

[libvirt] [PATCH] hypervisor driver for Jailhouse

>From README: The jailhouse hypervisor driver for the libvirt project aims to provide rudimentary support for managing jailhouse with the libvirt library. The main advantage of this is the possibility to use virt-manager as a GUI to manage Jailhouse cells. Thus the driver is mainly built around

Re: [libvirt] [vbox-dev] Assert with libvirt + xen hvm

Reviving old thread, this came up again via a Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1278847 https://retrace.fedoraproject.org/faf/reports/597209/ I took a cursory look at libxl's sigchld handling... it's intense to say the least, but there's some driver options that

Re: [libvirt] [RFC] migration encryption

On Tue, Nov 10, 2015 at 01:52:16PM +0300, Nikolay Shirokovskiy wrote: > Hi guys. > > I have a problem getting migration traffic encrypted for some scenarios. I > need to > migrate domain with non shared disks and can't use tunelled migration because > of RHEL7 qemu. > Without tunnel i get both

[libvirt] [RFC] migration encryption

Hi guys. I have a problem getting migration traffic encrypted for some scenarios. I need to migrate domain with non shared disks and can't use tunelled migration because of RHEL7 qemu. Without tunnel i get both vm state and disk state traffic unencrypted between peer's qemus. AFAIK there is a

Re: [libvirt] [PATCH v2 17/17] qemu: assume various QEMU 0.10 features are always available

On 11/10/2015 05:31 AM, Daniel P. Berrange wrote: > On Mon, Nov 09, 2015 at 06:28:03PM -0500, John Ferlan wrote: >> >> >> On 11/09/2015 11:24 AM, Daniel P. Berrange wrote: >>> The -sdl and -net ...name=XXX arguments were both introduced >>> in QEMU 0.10, so the QEMU driver can assume they are

Re: [libvirt] [RFC] migration encryption

On 10.11.2015 14:08, Ján Tomko wrote: > On Tue, Nov 10, 2015 at 01:52:16PM +0300, Nikolay Shirokovskiy wrote: >> Hi guys. >> >> I have a problem getting migration traffic encrypted for some scenarios. I >> need to >> migrate domain with non shared disks and can't use tunelled migration >>

Re: [libvirt] [PATCH v2 17/17] qemu: assume various QEMU 0.10 features are always available

On Tue, Nov 10, 2015 at 06:22:32AM -0500, John Ferlan wrote: > > > On 11/10/2015 05:31 AM, Daniel P. Berrange wrote: > > On Mon, Nov 09, 2015 at 06:28:03PM -0500, John Ferlan wrote: > >> > >> > >> On 11/09/2015 11:24 AM, Daniel P. Berrange wrote: > >>> The -sdl and -net ...name=XXX arguments

Re: [libvirt] [PATCH v2 17/17] qemu: assume various QEMU 0.10 features are always available

On 11/10/2015 06:43 AM, Daniel P. Berrange wrote: > On Tue, Nov 10, 2015 at 06:22:32AM -0500, John Ferlan wrote: >> >> >> On 11/10/2015 05:31 AM, Daniel P. Berrange wrote: >>> On Mon, Nov 09, 2015 at 06:28:03PM -0500, John Ferlan wrote: On 11/09/2015 11:24 AM, Daniel P. Berrange

[libvirt] [PATCH v2 0/2] vz: implement memory setting functions in driver

Diff from v1. 1. Add a patch to factor out common domain config update checks. Nikolay Shirokovskiy (2): vz: implement memory setting functions in driver vz: factor out config update flags checks src/libvirt-domain.c |5 +- src/vz/vz_driver.c | 129

Re: [libvirt] [PATCH v2 02/17] qemu: remove all support for kQEMU

On Tue, Nov 10, 2015 at 12:06:21 -0700, Eric Blake wrote: > On 11/09/2015 09:24 AM, Daniel P. Berrange wrote: > > The kQEMU accelerator was deleted in QEMU 0.12, so we no > > longer need to support it in the QEMU driver. > > > > Signed-off-by: Daniel P. Berrange > > --- > >

[libvirt] [PATCH v2 2/2] vz: factor out config update flags checks

Signed-off-by: Nikolay Shirokovskiy --- src/vz/vz_driver.c | 86 +-- 1 files changed, 29 insertions(+), 57 deletions(-) diff --git a/src/vz/vz_driver.c b/src/vz/vz_driver.c index 7a4d431..3392dc3 100644 ---

[libvirt] [PATCH v2 1/2] vz: add memory setting functions to driver

Implement functions for vz containers only. vz VMs memory managment thru libvirt yet to be designed. vz memory management for containers is rather different from other drivers. 1. Whole bunch of memory settings functions change both cur_balloon and maximum memory to the same value. The reason

Re: [libvirt] [PATCH 1/2] conf: add crash to hyperv features

On Thu, Nov 05, 2015 at 16:54:02 +0300, Dmitry Andreev wrote: > > > On 05.11.2015 14:06, Jiri Denemark wrote: > > On Mon, Oct 26, 2015 at 13:23:32 +0300, Dmitry Andreev wrote: > >> Add crash CPU feature for Hyper-V. Hyper-V crash MSR's can be used > >> by Hyper-V based guests to notify about

Re: [libvirt] [PATCH 08/10] conf: Prepare making memory device target node optional

On 11/10/2015 08:34 AM, Peter Krempa wrote: > On Tue, Oct 20, 2015 at 17:31:57 -0400, John Ferlan wrote: >> >> >> On 10/16/2015 08:11 AM, Peter Krempa wrote: >>> Adjust the config code so that it does not enforce that target memory >>> node is specified. To avoid breakage, adjust the qemu memory

[libvirt] discuss libvirt with lxc don't support network type:ethenet , thanks!

Dear, I find that:current libvirt version with lxc hypervisor don’t support network type :Ethernet For example: xml is： //hypervisor is lxc ………. //network type is ethernet When I start the lxc with that

[libvirt] [PATCH 1/3] qemu: domain: Restructurate control flow in qemuDomainGetMlockLimitBytes

Break early when hard limit is set so that it's not intermixed by other logic for determining the limit. --- src/qemu/qemu_domain.c | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c index 416ab5b..12517a5 100644 ---

[libvirt] [PATCH 3/3] qemu: Explain why mlock size is modified when def->mem.locked is enabled

--- src/qemu/qemu_domain.c | 5 + 1 file changed, 5 insertions(+) diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c index 11cd39e..7f2783b 100644 --- a/src/qemu/qemu_domain.c +++ b/src/qemu/qemu_domain.c @@ -3673,6 +3673,11 @@ qemuDomainRequiresMlock(virDomainDefPtr def) {

[libvirt] [PATCH 0/3] qemu: Tweak VFIO limit documentation

Peter Krempa (3): qemu: domain: Restructurate control flow in qemuDomainGetMlockLimitBytes qemu: Explain mlock limit size more in detail qemu: Explain why mlock size is modified when def->mem.locked is enabled src/qemu/qemu_domain.c | 34 -- 1 file

[libvirt] [PATCH 2/3] qemu: Explain mlock limit size more in detail

Based on Alex's explanation [1] in the recent discussion let's update the comment explaining the memory lock limit calculation. [1] http://www.redhat.com/archives/libvir-list/2015-November/msg00329.html --- src/qemu/qemu_domain.c | 19 --- 1 file changed, 16 insertions(+), 3

Re: [libvirt] [PATCH] qemu: process: Fix automatic setting of locked memory limit for VFIO

On Tue, Nov 10, 2015 at 09:40:34 -0700, Alex Williamson wrote: > On Fri, 2015-11-06 at 08:30 +0100, Peter Krempa wrote: [...] > Now the next question is whether this peer-to-peer DMA is useful, or > even used. I have heard of users assigning multiple AMD cards to a > system and making use of

Re: [libvirt] [PATCH 04/10] qemu: command: Always execute memory device formatter

On Tue, Oct 20, 2015 at 09:57:49 -0400, John Ferlan wrote: > On 10/16/2015 08:11 AM, Peter Krempa wrote: > > Since we already make sure before that the domain configuration is > > valid we may execute it always at the cost of doing 0 iterations of the > > for loop. > > > > This patch will

Re: [libvirt] [PATCH] vz: support cpu time in driver's domainGetInfo

On 10/30/2015 09:16 AM, Maxim Nestratov wrote: 28.10.2015 17:29, Nikolay Shirokovskiy пишет: Just straight-forward patch. Use reference counting for privdom as stats internally could drop domain lock. OK, I've checked, it works, and patch look good, ACKed and pushed. Signed-off-by:

Re: [libvirt] libvirt-snmp development

Hi, On 10/11/15 15:09, "libvir-list-boun...@redhat.com on behalf of Maxim Nestratov" wrote: > >10.11.2015 13:36, Martin Kletzander пишет: >> On Tue, Nov 10, 2015 at 12:40:36PM +0300, Maxim Nestratov wrote: >>> 10.11.2015

Re: [libvirt] [PATCH] hypervisor driver for Jailhouse

On Tue, Nov 10, 2015 at 13:17:41 +0100, Christian Loehle wrote: > >From README: > The jailhouse hypervisor driver for the libvirt project aims to provide > rudimentary support for managing jailhouse with the libvirt library. The > main advantage of this is the possibility to use virt-manager as a

Re: [libvirt] [PATCH 08/10] conf: Prepare making memory device target node optional

On Tue, Oct 20, 2015 at 17:31:57 -0400, John Ferlan wrote: > > > On 10/16/2015 08:11 AM, Peter Krempa wrote: > > Adjust the config code so that it does not enforce that target memory > > node is specified. To avoid breakage, adjust the qemu memory hotplug > > config checker to disallow such

Re: [libvirt] libvirt-snmp development

On Tue, Nov 10, 2015 at 09:29:19PM +, Dmitry Mishin wrote: Hi, On 10/11/15 15:09, "libvir-list-boun...@redhat.com on behalf of Maxim Nestratov" wrote: 10.11.2015 13:36, Martin Kletzander пишет: On Tue, Nov 10, 2015

[libvirt] [PATCH] doc: fix memory setting API documentation inconsistencies

Hi, everyone. Patch series "vz: implement memory setting functions in driver" besides doing what it declares also fixes inconsistency in documentation of domain API vs virsh CLI and somewhat biased to vz case. I've hoped that core mantainers check this out but suddenly realized that they are