Hi!
> We'd generally expect to see a change to tests/qemuxml2argvtest.c for
> this. Either adding a new test data file, or updating existing data
> files if they would cover it.
Sorry! Updated my patch. Have I still missed something?
I checked the valgrind tests, but they don't fail because of
Historically we have relied on autopoint/gettextize to install a
standard po/Makefile.in.in. There is very limited scope for customizing
this and it also causes a bunch of extra stuff to be pulled into
configure.ac which potentially clashes with gnulib. Writing make rules
for po file management is
Use virNetServerGetProgram() to determine the virNetServerProgram
instead of using hard coded global variables. This allows us to remove
the global variables @remoteProgram and @qemuProgram as they're now no
longer necessary.
Signed-off-by: Marc Hartmayer
On 12.04.2018 07:14, John Snow wrote:
>
>
> On 04/11/2018 12:32 PM, Eric Blake wrote:
>> On 04/03/2018 07:01 AM, Nikolay Shirokovskiy wrote:
>>> Hi, all.
>>>
>>>
On 04/12/2018 07:13 AM, Daniel P. Berrangé wrote:
> On Wed, Apr 11, 2018 at 04:10:03PM -0400, John Ferlan wrote:
>> Before we generate the command line for qemu, if the domain about to
>> be launched desires to utilize the VM Generation ID functionality, then
>> handle both the regenerating the
On 04/12/2018 04:44 AM, Erik Skultety wrote:
> On Thu, Apr 12, 2018 at 09:14:50AM +0200, Michal Privoznik wrote:
>> In 2ada9ef1465f we've tried to turn virDomainChrSourceDef into
>> virObject. Well, this requires 'virObject' member to be stored on
>> the first position of the struct. This
On Thu, Apr 12, 2018 at 10:41:03AM +0200, Andrea Bolognani wrote:
On Mon, 2018-04-09 at 17:20 +0200, Ján Tomko wrote:
Implied by QEMU >= 1.2.0.
Signed-off-by: Ján Tomko
---
src/qemu/qemu_capabilities.c | 1 -
src/qemu/qemu_capabilities.h
*Please accept our apologies if you receive multiple copies of this Call
for
PapersCALL
FOR PAPERS 13th Workshop on Virtualization in High-Performance Cloud
Computing (VHPC '18)held in conjunction with the International
This method is not tested for now since the test driver
doesn't suport this API.
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 6 ++
src/domain.c| 25 +
2 files changed, 31 insertions(+)
diff --git
Move testing of [Get,Set]Vcpus to seperate test.
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 6 ++
src/domain.c| 26 ++
test/test_domain.py | 9 +++--
3 files changed, 39 insertions(+), 2
The last use of qemuMonitorMigrateToCommand was removed years back in
commit 2e90c9daf9eabe15d826a48c06607acb9d18fda6
Author: Daniel P. Berrange
Date: Fri Nov 6 16:50:26 2015 +
qemu: assume support for all migration protocols except rdma
Prior to that
On Thu, Mar 29, 2018 at 01:09:49AM +0200, Ján Tomko wrote:
> Prefer Jansson, but allow fallback/choice of yajl.
>
> Support for yajl can hopefully be dropped after we ditch CentOS 6
> which has no Jansson.
Seems like we can revisit this patch series given our discusions
about supported
Use the return value of virObjectRef directly. This way, it's easier
for another reader to identify the reason why the additional reference
is required.
Signed-off-by: Marc Hartmayer
Reviewed-by: Boris Fiuczynski
---
src/rpc/virnetserver.c | 3
Introduce global libxl option for enabling nested HVM feature, similar
to kvm module parameter. This will prevent enabling experimental feature
by mere presence of element in domain
config, unless explicitly enabled. element
may be used to configure other features, like NUMA, or CPUID.
Test enabling/disabling individual CPU features and also setting
nested HVM support, which is also controlled by CPU features node.
Signed-off-by: Marek Marczykowski-Górecki
Reviewed-by: Jim Fehlig
Reviewed-by: Daniel P. Berrangé
Details in the commit message for 2/2 and the bug report
referenced therein.
Andrea Bolognani (2):
tests: Create full host NUMA topology by default
qemu: Figure out nodeset bitmap size correctly
src/qemu/qemu_domain.c| 11 +-
tests/qemustatusxml2xmldata/modern-in.xml
Add support for CPUID setting based on element. Since libxl format
support only adjusting specific bits over host CPU, only
mode='host-passthrough' is supported - other values are rejected (including
default 'custom'). This will break some configurations working before (bare
element with for
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 6 ++
src/domain.c| 25 +
2 files changed, 31 insertions(+)
diff --git a/data/org.libvirt.Domain.xml b/data/org.libvirt.Domain.xml
index 074dd62..c3c64fa 100644
On 13.04.2018 02:53, John Snow wrote:
>>
> First a few facts about qemu dirty bitmaps.
>
> Bitmap can be either in active or disable state. In disabled state it
> does not
> get changed on guest writes. And oppositely in active state it tracks
> guest
> writes.
On Thu, Apr 12, 2018 at 04:32:54PM +0200, Katerina Koukiou wrote:
> Move testing of [Get,Set]Vcpus to seperate test.
>
> Signed-off-by: Katerina Koukiou
> ---
> data/org.libvirt.Domain.xml | 6 ++
> src/domain.c| 26 ++
>
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 6 ++
src/domain.c| 36
2 files changed, 42 insertions(+)
diff --git a/data/org.libvirt.Domain.xml b/data/org.libvirt.Domain.xml
index
On 13.04.2018 03:04, John Snow wrote:
>
>
> On 04/12/2018 10:08 AM, Vladimir Sementsov-Ogievskiy wrote:
>>
>> I propose, not to say that bitmap represents a checkpoint. It is simpler
>> to say (and it reflects the reality) that bitmap is a difference between
>> two consecutive checkpoints. And
On Wed, Apr 11, 2018 at 04:41:00PM +0200, Jiri Denemark wrote:
It provides just another view on some migration parameters so let's move
it close to them. The end goal is to merge compression parameters with
the rest of migration parameters since it doesn't make any sense to
handle them
On Thu, Apr 12, 2018 at 04:32:49PM +0200, Katerina Koukiou wrote:
> Signed-off-by: Katerina Koukiou
> ---
> data/org.libvirt.Domain.xml | 6 ++
> src/domain.c| 25 +
> 2 files changed, 31 insertions(+)
[...]
> +static void
>
On Wed, Apr 11, 2018 at 04:40:58PM +0200, Jiri Denemark wrote:
It will get a bit more complicated soon and storing it on a stack with
{0} initializer will no longer work. We need a proper constructor.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_driver.c | 20
On 04/13/2018 09:34 AM, Radostin Stoyanov wrote:
> Remove unnecessary virFileIsExecutable check after virFindFileInPath.
> Since commit 9ae992f, virFindFileInPath will reject non-executables.
>
> 9ae992f24353d6506f570fc9dd58355b165e4472
> virFindFileInPath: only find executable non-directory
>
>
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 6 ++
src/domain.c| 36
2 files changed, 42 insertions(+)
diff --git a/data/org.libvirt.Domain.xml b/data/org.libvirt.Domain.xml
index
On Wed, Apr 11, 2018 at 04:41:16PM +0200, Jiri Denemark wrote:
Migration capabilities are closely related to migration parameters and
it makes sense to keep them in a single data structure. Similarly to
migration parameters the capabilities are all send to QEMU at once in
On 04/12/2018 05:40 PM, Sukrit Bhatnagar wrote:
> Incremental patches do look better. Just to make sure I am on the right
> track, I have some queries.
>
> I have to apply the changes one function at a time, and these changes
> will be the same ones I made in the v2 and v3 patches, right?
yes,
On Wed, Apr 11, 2018 at 04:41:12PM +0200, Jiri Denemark wrote:
There's no real reason for qemuMigrationParamsEnableTLS to require the
callers to pass a valid virQEMUDriverConfigPtr, it can just call
virQEMUDriverGetConfig.
Signed-off-by: Jiri Denemark
---
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 6 ++
src/domain.c| 28
2 files changed, 34 insertions(+)
diff --git a/data/org.libvirt.Domain.xml b/data/org.libvirt.Domain.xml
index 21eb162..eec9dcb 100644
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 4
src/domain.c| 22 ++
test/test_domain.py | 1 +
3 files changed, 27 insertions(+)
diff --git a/data/org.libvirt.Domain.xml b/data/org.libvirt.Domain.xml
On Wed, Apr 11, 2018 at 04:41:05PM +0200, Jiri Denemark wrote:
Currently, only job->phase is passed and both APIs will need to look at
more details about the job.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_process.c | 12 ++--
1 file changed, 6 insertions(+), 6
On 13/04/18 08:35, Michal Privoznik wrote:
> On 04/13/2018 08:01 AM, Radostin Stoyanov wrote:
>> Remove unnecessary virFileIsExecutable check after virFindFileInPath.
>> Since the commit 9ae992f virFindFileInPath will reject non-executables.
>>
>> 9ae992f24353d6506f570fc9dd58355b165e4472
>>
On Wed, Apr 11, 2018 at 04:41:15PM +0200, Jiri Denemark wrote:
Our current monitor API forces the caller to call
migrate-set-capabilities QMP command for each capability separately,
which is quite suboptimal. Let's add a new API for setting all
capabilities at once.
Signed-off-by: Jiri Denemark
On Wed, Apr 11, 2018 at 04:41:03PM +0200, Jiri Denemark wrote:
Any job which touches migration parameters will first store their
original values (i.e., QEMU defaults) to qemuDomainJobObj to make it
easier to reset them back once the job finishes.
Signed-off-by: Jiri Denemark
Move testing of [Get,Set]Vcpus to seperate test.
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 6 ++
src/domain.c| 26 ++
test/test_domain.py | 9 +++--
3 files changed, 39 insertions(+), 2
On Thu, Apr 12, 2018 at 04:33:00PM +0200, Katerina Koukiou wrote:
> Signed-off-by: Katerina Koukiou
> ---
> data/org.libvirt.Domain.xml | 6 ++
> src/domain.c| 26 ++
> 2 files changed, 32 insertions(+)
[...]
> +static void
>
On Wed, Apr 11, 2018 at 04:40:59PM +0200, Jiri Denemark wrote:
It's no longer used since we do not store the struct on a stack anymore.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration_params.c | 12 +---
src/qemu/qemu_migration_params.h | 3 ---
2 files
This method is not tested for now since the test driver
doesn't suport this API.
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 6 ++
src/domain.c| 25 +
2 files changed, 31 insertions(+)
diff --git
On Wed, Apr 11, 2018 at 04:41:09PM +0200, Jiri Denemark wrote:
The new name is qemuMigrationParamsDisableTLS.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration.c| 4 ++--
src/qemu/qemu_migration_params.c | 6 +++---
src/qemu/qemu_migration_params.h | 4 ++--
3
On Wed, Apr 11, 2018 at 04:41:02PM +0200, Jiri Denemark wrote:
When connection to the client which controls a non-p2p migration gets
closed between Perform and Confirm phase, we don't know whether the
domain was successfully migrated or not. Thus, we have to leave the
domain paused and just
On Wed, Apr 11, 2018 at 04:41:08PM +0200, Jiri Denemark wrote:
The function checks whether QEMU supports TLS migration and stores the
original value of tls-creds parameter to priv->migTLSAlias. This is no
longer needed because we already have the original value stored in
priv->migParams.
Rework all remaining callers of qemuMonitorSetMigrationCapability to use
the new qemuMonitorSetMigrationCapabilities API.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration_params.c | 11 ---
tests/qemumonitorjsontest.c | 16 +++-
2 files
11.04.2018 16:56, Eric Blake wrote:
On 04/03/2018 07:01 AM, Nikolay Shirokovskiy wrote:
Hi, all.
This is another RFC on pull backup API. This API provides means to read domain
disks in a
The function checks whether QEMU supports TLS migration and stores the
original value of tls-creds parameter to priv->migTLSAlias. This is no
longer needed because we already have the original value stored in
priv->migParams.
Signed-off-by: Jiri Denemark
---
Since the function is tightly connected to migration, it was renamed as
qemuMigrationCapsCheck and moved to qemu_migration_params.c.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_domain.c | 72
src/qemu/qemu_domain.h |
When connection to the client which controls a non-p2p migration gets
closed between Perform and Confirm phase, we don't know whether the
domain was successfully migrated or not. Thus, we have to leave the
domain paused and just cleanup the migration job and reset migration
parameters.
Previously
The code can be merged directly in qemuMigrationParamsAddTLSObjects.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration.c| 15 ---
src/qemu/qemu_migration_params.c | 73 ++--
src/qemu/qemu_migration_params.h | 6 ---
3 files
On Wed, 2018-04-11 at 08:52 -0400, John Ferlan wrote:
> On 05/03/2018 08:57 AM, Andrea Bolognani wrote:
> > Up until now we have only formatted non-default GIC versions on
> > the command line, in order to maintain compatibility with older
> > QEMU versions that didn't implement the gic-version
On 11.04.2018 17:16, Vladimir Sementsov-Ogievskiy wrote:
> 11.04.2018 16:56, Eric Blake wrote:
>> On 04/03/2018 07:01 AM, Nikolay Shirokovskiy wrote:
>>> Hi, all.
>>>
>>> This is another RFC on
The new name is qemuMigrationParamsEnableTLS.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration.c| 12 ++--
src/qemu/qemu_migration_params.c | 18 +-
src/qemu/qemu_migration_params.h | 16
3 files changed, 23
Our *Free functions usually do not take a double pointer and the caller
has to make sure it doesn't use the stale pointer after the *Free
function returns.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_driver.c | 2 +-
src/qemu/qemu_migration_params.c | 10
This is very convenient for developers using the 'test' flavor,
because it ensures
$ ./lcitool update all
still works by logging in as root, but at the same time ad-hoc
invocations such as
$ ansible all -m shell -a 'cd libvirt && $MAKE -j check'
and custom playbooks log in as the 'test'
ping?
Tks,
John
On 04/02/2018 10:15 AM, John Ferlan wrote:
> Details in each patch - being consistent for future adjustment.
>
> John Ferlan (2):
> lxc: Fix possible leaked @vm in lxcDomainCreateXMLWithFiles
> lxc: Fix object locking after virDomainObjListRemove
>
> src/lxc/lxc_driver.c
Changes from [v1]:
* instead of dropping CentOS 6 altogether, simply stop building
pretty much all projects on it;
* introduce a new job type specifically for whatever little
stuff we need to ensure still works on CentOS 6;
* the end result is still a nice cleanup thanks to not
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 6 ++
src/domain.c| 38 ++
2 files changed, 44 insertions(+)
diff --git a/data/org.libvirt.Domain.xml b/data/org.libvirt.Domain.xml
index
Signed-off-by: Katerina Koukiou
---
data/org.libvirt.Domain.xml | 5 +
src/domain.c| 35 +++
2 files changed, 40 insertions(+)
diff --git a/data/org.libvirt.Domain.xml b/data/org.libvirt.Domain.xml
index 83e37bc..2e0339b
On Thu, 2018-04-12 at 17:16 +0200, Ján Tomko wrote:
> On Thu, Apr 12, 2018 at 10:07:50AM +0200, Andrea Bolognani wrote:
> > On Mon, 2018-04-09 at 17:20 +0200, Ján Tomko wrote:
> > > Delete this one first, because QEMU_CAPS_NODEFCONFIG is only used
> > > when QEMU_CAPS_NO_USER_CONFIG is
On 04/04/2018 10:45 AM, Viktor Mihajlovski wrote:
> The QEMU monitor commmand query-cpus is deprecated starting
> with QEMU 2.12.0 because it can adversely affect the performance of
> a running virtual machine.
>
> This series enables libvirt to use the new query-cpus-fast interface
> if
On 04/04/2018 10:45 AM, Viktor Mihajlovski wrote:
> Extended the json monitor test program with support for query-cpus-fast
> and added a sample file set for x86 data obtained using the it.
> Also extend the test program to recognize the halted property.
This last sentence involves code that
The legacy xen driver is removed, so these ACLL hacks can be removed
too now.
Signed-off-by: Daniel P. Berrangé
---
src/check-aclrules.pl | 23 ---
1 file changed, 4 insertions(+), 19 deletions(-)
diff --git a/src/check-aclrules.pl
Incremental patches do look better. Just to make sure I am on the right
track, I have some queries.
I have to apply the changes one function at a time, and these changes will
be the same ones I made in the v2 and v3 patches, right?
If that is the case, do I need the next patch to be v4 or can the
On 04/12/2018 08:26 AM, Vladimir Sementsov-Ogievskiy wrote:
> 1. It looks unsafe to use nbd server + backup(sync=none) on same node,
> synchronization is needed, like in block/replication, which uses
> backup_wait_for_overlapping_requests, backup_cow_request_begin,
> backup_cow_request_end. We
On 04/04/2018 12:29 PM, Jai Singh Rana wrote:
> In case of pci SR-IOV device with interface_type as 'hostdev', return
> network stats if it has a VF Representor interface on host for
> pci SR-IOV device according to switchdev model.
> ---
> v3 includes changes based on v2's[1] feedback and
On Thu, Apr 12, 2018 at 04:32:44PM +0200, Katerina Koukiou wrote:
> This method is not tested for now since the test driver
> doesn't suport this API.
>
> Signed-off-by: Katerina Koukiou
> ---
> data/org.libvirt.Domain.xml | 6 ++
> src/domain.c| 25
On 04/10/2018 10:50 PM, Stefan Berger wrote:
This patch extends the TPM's device XML with TPM 2 support. This only works
for the emulator type backend and looks as follows:
Once the version of a TPM has been chosen it cannot be changed anymore unless
one removes the TPM
ping?
Changes are less about vz driver and more about domain object
manipulation consistency.
Tks,
John
On 04/02/2018 09:21 AM, John Ferlan wrote:
> Reposting patches 16-17 from:
> https://www.redhat.com/archives/libvir-list/2018-March/msg00489.html
>
> Reposting and using the vz prefix to
On Mon, 2018-04-09 at 17:20 +0200, Ján Tomko wrote:
> Now that we assume QEMU_CAPS_NETDEV, the only thing left to check
> is whether we need to use the legacy -net syntax because of
> a non-conforming armchitecture.
I see you're having "pun" writing these commit messages ;)
[...]
> diff --git
Remove the unnecessary goto error followed by goto cleanup
processing.
Signed-off-by: John Ferlan
---
src/openvz/openvz_driver.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/src/openvz/openvz_driver.c b/src/openvz/openvz_driver.c
index
On Mon, 2018-04-09 at 17:20 +0200, Ján Tomko wrote:
> Signed-off-by: Ján Tomko
> ---
> src/qemu/qemu_domain.c | 6 --
> src/qemu/qemu_domain.h | 2 --
> 2 files changed, 8 deletions(-)
Reviewed-by: Andrea Bolognani
--
Andrea Bolognani / Red Hat /
On Wed, Apr 04, 2018 at 10:13:57AM +0200, Peter Krempa wrote:
QEMU translates the cache mode of a disk internally into 3 flags.
'write-cache' is a flag of the frontend while others are flag of the
backing storage. Add capability which will allow expressing it via the
frontend attribute.
On Wed, 11 Apr 2018 17:49:51 +0200
Shalini Chellathurai Saroja wrote:
> Let us support the basic channel I/O passthrough infrastructure based on
> vfio, which have been introduced in QEMU 2.10. The current focus is to
> support dasd-eckd (cu_type/dev_type =
On Tue, 2018-04-10 at 17:29 +0100, Daniel P. Berrangé wrote:
> Signed-off-by: Daniel P. Berrangé
> ---
> projects/osinfo-db.yaml | 6 +-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/projects/osinfo-db.yaml b/projects/osinfo-db.yaml
> index
https://bugzilla.redhat.com/show_bug.cgi?id=1480668
Signed-off-by: Michal Privoznik
---
src/qemu/qemu_command.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/src/qemu/qemu_command.c b/src/qemu/qemu_command.c
index f864350bd5..67350719aa 100644
---
On Mon, Apr 09, 2018 at 08:34:06AM +0200, Christian Ehrhardt wrote:
> Due to mediation of socket and signal activity currently qemu:///session
> connections calling qemu_bridge_helper fail.
>
> We need the profile for libvirtd itself and the subprofile for
> qemu-bridge-helper to be able to
On 04/10/2018 10:58 AM, Michal Privoznik wrote:
> Signed-off-by: Michal Privoznik
> ---
> src/qemu/qemu_capabilities.c | 1 +
> tests/qemucapabilitiesdata/caps_2.11.0.s390x.xml | 1 +
> tests/qemucapabilitiesdata/caps_2.12.0.aarch64.xml | 1 +
>
On 04/10/2018 10:58 AM, Michal Privoznik wrote:
> Just like in previous commit, qemu-pr-helper might want to open
> /dev/mapper/control under certain circumstances. Therefore we
> have to allow it in cgroups.
Perhaps the two patches should be combined then... yes, I know cgroups
is different
On 04/10/2018 10:58 AM, Michal Privoznik wrote:
> When attaching a disk that requires pr-manager we might need to
> plug the pr-manager object too.
>
> Signed-off-by: Michal Privoznik
> ---
> src/qemu/qemu_hotplug.c | 41 +
> 1 file
On 04/10/2018 10:58 AM, Michal Privoznik wrote:
> When plugging a disk into domain we need to start qemu-pr-helper
> process iff this is the first disk with PR enabled for the
> domain. Otherwise the helper is already running (or not needed).
>
> Signed-off-by: Michal Privoznik
The vmware driver wants to execute vmware-vmx from the same directory in
which vmrun was found. However, on VMware Fusion 10 vmrun at
/Applications/VMware Fusion.app/Contents/Public/vmrun is a symlink
pointing to ../Library/vmrun. vmware-vmx cannot be found, as
it is not in PATH, but only in this
On 04/10/2018 10:58 AM, Michal Privoznik wrote:
> If qemu-pr-helper is compiled with multipath support the first
> thing it does is opening /dev/mapper/control. Since we're going
s/opening/open
> to be running it inside qemu namespace we need to create it
> there. Unfortunately, we don't know
On 04/10/2018 10:58 AM, Michal Privoznik wrote:
> Before we exec() qemu we have to spawn pr-helper processes for
> all managed reservations (well, technically there can only one).
Don't mince words - what have to spawn the qemu-pr-helper process for
all managed persistent reservations.
> The
On 04/10/2018 10:58 AM, Michal Privoznik wrote:
> This is the easier part. All we need to do here is put -object
> pr-manager-helper,id=$alias,path=$socketPath and then just
> reference the object in -drive file.pr-manager=$alias.
>
> Signed-off-by: Michal Privoznik
> ---
These changes were required to get VMware Fusion working at all.
I tested with VMware Fusion 10.1.1 on macOS 10.12 Sierra.
I am not sure whether calling virCapabilitiesInitCaches() makes sense at
all on macOS. This function looks highly specific to Linux as it relies
on /sys/devices/system, so it
So far it's used only for CPU throttling parameters which are all ints,
but we'll soon want to use it for more parameters with different types.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration_params.c | 31 +++
1 file changed, 15
We reached the point when qemuMigrationParamsApply is the only API which
sends migration parameters and capabilities to QEMU. Thus all but the
TLS parameters can be set before we ask QEMU for the current values of
all parameters in qemuMigrationParamsCheck.
Supported migration capabilities are
We reached the point when qemuMigrationParamsApply is the only API which
sends migration parameters and capabilities to QEMU. Thus all but the
TLS parameters can be set before we ask QEMU for the current values of
all parameters in qemuMigrationParamsCheck.
Supported migration capabilities are
We want to have all migration parameters parsing and formatting at one
place, i.e., in qemu_migration_params.c.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration_params.c | 68 +++-
src/qemu/qemu_monitor.c | 35
The API will soon be called from qemuMigrationParamsFromFlags. Let's
move it to avoid the need to add a forward declaration.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration_params.c | 59
1 file changed, 30 insertions(+), 29
Since the monitor code no longer needs to see this enum, we move it
to the place where migration parameters are defined and drop the
"monitor" reference from the name.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_driver.c | 4 +-
Trying to delete the non-existent TLS objects results in ugly error
messages in the log, which could easily confuse users. Let's avoid this
confusion by not trying to delete the objects if we were not asked to
enable TLS migration and thus we didn't created the objects anyway.
This patch restores
ping? This is less about vmware specifically and more about domain
object manipulation coordination...
Tks,
John
On 04/02/2018 09:16 AM, John Ferlan wrote:
> Patches 12-15 of the formerly larger series:
>
> https://www.redhat.com/archives/libvir-list/2018-March/msg00489.html
>
> Changes
When an async job is running, we sometimes need to know how it was
started to distinguish between several types of the job, e.g., post-copy
vs. normal migration. So far we added a specific bool item to
qemuDomainJobObj for such cases, which doesn't scale very well and
storing such bools in status
On 04/04/2018 04:13 AM, Peter Krempa wrote:
> Allow testing of XML->argv conversion with using a real capability map
> as used in the qemucapabilitiestest. This allows specifying the required
> qemu version with the test rather than having to enumerate all the
> required capabilities.
>
>
It's just a tiny wrapper around qemuMigrationParamsSetCapability and
setting priv->job.postcopyEnabled is not something qemuMigrationParams
code should be doing anyway so let the callers do it.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration.c| 16
All users of migration parameters are supposed to use APIs provided by
qemu_migration_params.c without having to worry about the internals.
Signed-off-by: Jiri Denemark
---
src/qemu/qemu_migration_params.c | 5 +
src/qemu/qemu_migration_params.h | 3 ---
2 files
Adding support for new migration parameter requires a lot of places to
be changed (most likely by copy engineering): new variables to
store the parameter value and the associated *_set bool, JSON formatter
and parser, XML formatter and parser (to be added soon), and the actual
code to set the
Originally QEMU provided query-migrate-cache-size and
migrate-set-cache-size QMP commands for querying/setting XBZRLE cache
size. In version 2.11 QEMU added support for XBZRLE cache size to the
general migration paramaters commands.
This patch adds support for this parameter to libvirt to make
There's no need to call this API explicitly in the migration code. We
can pass the compression parameters to qemuMigrationParamsFromFlags and
it can internally call qemuMigrationParamsSetCompression to apply them
to the qemuMigrationParams structure.
Signed-off-by: Jiri Denemark
1 - 100 of 172 matches
Mail list logo