Branch: refs/heads/staging
Home: https://github.com/qemu/qemu
Commit: bb7fc1543fa45bebe7eded8115f25441a9fee76e
https://github.com/qemu/qemu/commit/bb7fc1543fa45bebe7eded8115f25441a9fee76e
Author: Richard Henderson <[email protected]>
Date: 2025-12-18 (Thu, 18 Dec 2025)
Changed paths:
M VERSION
Log Message:
-----------
Update version for v10.2.0-rc4 release
Signed-off-by: Richard Henderson <[email protected]>
Commit: 698104725efad4b29079d857dfdebbd804e34c99
https://github.com/qemu/qemu/commit/698104725efad4b29079d857dfdebbd804e34c99
Author: Richard Henderson <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M VERSION
Log Message:
-----------
Update version for v10.2.0 release
Signed-off-by: Richard Henderson <[email protected]>
Commit: 8dd5bceb2f9cc58481e9d22355a8d998220896de
https://github.com/qemu/qemu/commit/8dd5bceb2f9cc58481e9d22355a8d998220896de
Author: Richard Henderson <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M VERSION
Log Message:
-----------
Open 11.0 development tree
Signed-off-by: Richard Henderson <[email protected]>
Commit: b043f6df273fd276317e39ce58188a84c7bf8ebb
https://github.com/qemu/qemu/commit/b043f6df273fd276317e39ce58188a84c7bf8ebb
Author: Pawel Zmarzly <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/ram.c
M tests/qtest/migration/file-tests.c
Log Message:
-----------
migration: fix parsing snapshots with x-ignore-shared flag
Snapshots made with mapped-ram and x-ignore-shared flags are
not parsed properly.
The ignore-shared feature adds and extra field in the stream, which
needs to be consumed on the destination side. Even though mapped-ram has
a fixed header format, the ignore-shared is part of the "generic" stream
infomation so the mapped-ram code is currently skipping that be64 read
which incorrectly offsets every subsequent read from the stream.
The current ignore-shared handling can simply be moved earlier in the code
to encompass mapped-ram as well since the ignore-shared doubleword is the
first one read when parsing the ramblock section of the stream.
Co-authored-by: Peter Xu <[email protected]>
Signed-off-by: Pawel Zmarzly <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[peterx: enhance commit log per fabiano]
Signed-off-by: Peter Xu <[email protected]>
Commit: 0b510b51b6340c5c3caead653195711a2a798e96
https://github.com/qemu/qemu/commit/0b510b51b6340c5c3caead653195711a2a798e96
Author: Pawel Zmarzly <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/ram.c
Log Message:
-----------
migration: Fix writing mapped_ram + ignore_shared snapshots
Currently if you set these flags and have any shared memory object, saving
a snapshot will fail with:
Failed to write bitmap to file: Unable to write to file: Bad address
We need to skip writing RAMBlocks that are backed by shared objects.
Also, we should mark these RAMBlocks as skipped, so the snapshot format stays
readable to tools that later don't know QEMU's command line (for example
scripts/analyze-migration.py). I used bitmap_offset=0 pages_offset=0 for this.
This minor change to snapshot format should be safe, as offset=0 should not
have ever been possible.
Signed-off-by: Pawel Zmarzly <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: e476d36ef74c5abf97f0b861f79c65e869655a41
https://github.com/qemu/qemu/commit/e476d36ef74c5abf97f0b861f79c65e869655a41
Author: Pawel Zmarzly <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M scripts/analyze-migration.py
Log Message:
-----------
scripts/analyze-migration: Rename RAM_SAVE_FLAG_COMPRESS to RAM_SAVE_FLAG_ZERO
It has been renamed on the C side a few years ago. In modern QEMU versions,
fill_byte must be zero. Updating the Python script to make grepping and
understanding the code easier.
Signed-off-by: Pawel Zmarzly <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[peterx: fix over-long line]
Signed-off-by: Peter Xu <[email protected]>
Commit: 0002b0db1377808e3c2abcb4f02f3d3aa8ce304a
https://github.com/qemu/qemu/commit/0002b0db1377808e3c2abcb4f02f3d3aa8ce304a
Author: Pawel Zmarzly <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M scripts/analyze-migration.py
Log Message:
-----------
scripts/analyze-migration: Support mapped-ram snapshot format
The script has not been updated to read mapped-ram snapshots and is currently
crashing when trying to read such a file.
With this commit, it can now read a snapshot created with:
(qemu) migrate_set_capability x-ignore-shared on
(qemu) migrate_set_capability mapped-ram on
(qemu) migrate -d file:vm.state
Signed-off-by: Pawel Zmarzly <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[peterx: space fixes, introduce parseMappedRamBlob(), add comments, etc.]
Signed-off-by: Peter Xu <[email protected]>
Commit: 856ac0ccd8c7acfed7abee8f6218813c2b5d391a
https://github.com/qemu/qemu/commit/856ac0ccd8c7acfed7abee8f6218813c2b5d391a
Author: Peter Xu <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/multifd-device-state.c
M migration/savevm.c
Log Message:
-----------
migration: Use explicit error_free() instead of g_autoptr
There're only two use cases of g_autoptr to free Error objects in migration
code paths.
Due to the nature of how Error should be used (normally ownership will be
passed over to Error APIs, like error_report_err), auto-free functions may
be error prone on its own. The auto cleanup function was merged without
proper review, as pointed out by Dan and Markus:
https://lore.kernel.org/r/[email protected]
Remove the two use cases so that we can remove the auto cleanup function,
hence suggest to not use auto frees for Errors.
Suggested-by: Markus Armbruster <[email protected]>
Reviewed-by: Markus Armbruster <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: aa0b2ec50be17d2f1ce3180f0b69a943f7c9c25b
https://github.com/qemu/qemu/commit/aa0b2ec50be17d2f1ce3180f0b69a943f7c9c25b
Author: Peter Xu <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M include/qapi/error.h
Log Message:
-----------
Revert "error: define g_autoptr() cleanup function for the Error type"
This reverts commit 18eb55546a54e443d94a4c49286348176ad4b00a.
Due to the nature of how Error should be used (normally ownership will be
passed over to Error APIs, like error_report_err), auto-free functions may
be error prone on its own. The auto cleanup function was merged without
proper review as pointed out by Dan and Markus:
https://lore.kernel.org/r/[email protected]
Cc: Cédric Le Goater <[email protected]>
Acked-by: Maciej S. Szmigiero <[email protected]>
Reviewed-by: Markus Armbruster <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Acked-by: Maciej S. Szmigiero <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: b4898faabed183517ca1352401dc0071ae8866b9
https://github.com/qemu/qemu/commit/b4898faabed183517ca1352401dc0071ae8866b9
Author: Markus Armbruster <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M include/qapi/error.h
Log Message:
-----------
error: Poison g_autoptr(Error) to prevent its use
The previous commit reverted support for g_autoptr(Error). This one
should stop it from coming back.
Suggested-by: Peter Maydell <[email protected]>
Signed-off-by: Markus Armbruster <[email protected]>
Tested-by: Cédric Le Goater <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 77c82edadbef9db20abee9faaf9a028cb140f3cb
https://github.com/qemu/qemu/commit/77c82edadbef9db20abee9faaf9a028cb140f3cb
Author: Peter Xu <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/channel.c
M migration/migration.c
Log Message:
-----------
migration: Make migration_connect_set_error() own the error
Make migration_connect_set_error() take ownership of the error always.
Paving way for making migrate_set_error() to take ownership.
When at it, renaming it to migration_connect_error_propagate(), following
Error API, to imply the Error object ownership transition.
NOTE: this patch also makes migration_connect() to take ownership of the
Error passed in.
Reviewed-by: Markus Armbruster <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: bc8558307957ab7c826cd6d8f152d8e55aef8634
https://github.com/qemu/qemu/commit/bc8558307957ab7c826cd6d8f152d8e55aef8634
Author: Peter Xu <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/multifd.c
Log Message:
-----------
migration: Make multifd_send_set_error() own the error
Make multifd_send_set_error() take ownership of the error always. Paving
way for making migrate_set_error() to take ownership.
When at it, rename it to multifd_send_error_propagate() to imply the
ownership transition following Error API's naming style.
Reviewed-by: Markus Armbruster <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 2f904a384df9b0e07db0cae6481ecbb66c26db97
https://github.com/qemu/qemu/commit/2f904a384df9b0e07db0cae6481ecbb66c26db97
Author: Peter Xu <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/multifd.c
Log Message:
-----------
migration: Make multifd_recv_terminate_threads() own the error
Make multifd_recv_terminate_threads() take ownership of the error always.
Paving way for making migrate_set_error() to take ownership.
Reviewed-by: Markus Armbruster <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: d4fd83c9b51612eb3bd674eb9c106f2d45fc2c28
https://github.com/qemu/qemu/commit/d4fd83c9b51612eb3bd674eb9c106f2d45fc2c28
Author: Peter Xu <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/cpr-exec.c
M migration/migration.c
M migration/migration.h
M migration/multifd-device-state.c
M migration/multifd.c
M migration/postcopy-ram.c
M migration/ram.c
M migration/savevm.c
Log Message:
-----------
migration: Replace migrate_set_error() with migrate_error_propagate()
migrate_set_error() currently doesn't take ownership of the error being
passed in. It's not aligned with the error API and meanwhile it also
makes most of the caller free the error explicitly.
Change the API to take the ownership of the Error object instead. This
should save a lot of error_copy() invocations.
Reviewed-by: Markus Armbruster <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[peterx: break line for qemu_savevm_send_packaged, per markus]
Signed-off-by: Peter Xu <[email protected]>
Commit: a85fb03ee4ecd9da5e5ef532f6058905d62c1d07
https://github.com/qemu/qemu/commit/a85fb03ee4ecd9da5e5ef532f6058905d62c1d07
Author: Peter Xu <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/migration.c
Log Message:
-----------
migration: Use error_propagate() in migrate_error_propagate()
It improves readability, as suggested by Markus.
Suggested-by: Markus Armbruster <[email protected]>
Reviewed-by: Markus Armbruster <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: e39dd4e5d5428837e0308e486beece36798f9ecd
https://github.com/qemu/qemu/commit/e39dd4e5d5428837e0308e486beece36798f9ecd
Author: Peter Xu <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/options.c
Log Message:
-----------
migration/options: Add x-ignore-shared
This aids scriptings only.
Reviewed-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[peterx: make the property x-ignore-shared to match, per cedric]
[peterx: fix over-80 line]
Signed-off-by: Peter Xu <[email protected]>
Commit: 1b67d9535241438ffc9af9aa038f0fd510811ecf
https://github.com/qemu/qemu/commit/1b67d9535241438ffc9af9aa038f0fd510811ecf
Author: Ben Chaney <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M MAINTAINERS
Log Message:
-----------
MAINTAINERS: Update reviewers for CPR
Signed-off-by: Ben Chaney <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 16de4ac52e026447175e66d79ddbd279b4ece5c7
https://github.com/qemu/qemu/commit/16de4ac52e026447175e66d79ddbd279b4ece5c7
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/migration.c
Log Message:
-----------
migration: Fix leak of block_bitmap_mapping
Caught by inspection, but ASAN also reports:
Direct leak of 16 byte(s) in 1 object(s) allocated from:
#0 in malloc
#1 in g_malloc
#2 in g_memdup
#3 in qapi_clone_start_struct ../qapi/qapi-clone-visitor.c:40:12
#4 in qapi_clone_start_list ../qapi/qapi-clone-visitor.c:59:12
#5 in visit_start_list ../qapi/qapi-visit-core.c:80:10
#6 in visit_type_BitmapMigrationNodeAliasList
qapi/qapi-visit-migration.c:639:10
#7 in migrate_params_apply ../migration/options.c:1407:13
#8 in qmp_migrate_set_parameters ../migration/options.c:1463:5
#9 in qmp_marshal_migrate_set_parameters qapi/qapi-commands-migration.c:214:5
#10 in do_qmp_dispatch_bh ../qapi/qmp-dispatch.c:128:5
Note that this is entirely harmless because the migration object which
contains the MigrationParameters structure is kept until the QEMU
process exits.
Reviewed-by: Markus Armbruster <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 881536e2a53dad9b528bf135c8835256f997737e
https://github.com/qemu/qemu/commit/881536e2a53dad9b528bf135c8835256f997737e
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/migration.c
Log Message:
-----------
migration: Fix leak of cpr_exec_command
Signed-off-by: Fabiano Rosas <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: be346eb667349ca316942970365f0f1533875170
https://github.com/qemu/qemu/commit/be346eb667349ca316942970365f0f1533875170
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/options.c
Log Message:
-----------
migration: Add a qdev property for StrOrNull
The MigrationState is a QOM object with TYPE_DEVICE as a parent. This
was done about eight years ago so the migration code could make use of
qdev properties to define the defaults for the migration parameters
and to be able to expose migration knobs for debugging via the
'-global migration' command line option.
Due to unrelated historical reasons, three of the migration parameters
(TLS options) received different types when used via the
query-migrate-parameters QMP command than with the
migrate-set-parameters command. This has created a lot of duplication
in the migration code and in the QAPI documentation because the whole
of MigrationParameters had to be duplicated as well.
The migration code is now being fixed to remove the duplication and
for that to happen the offending fields need to be reconciled into a
single type. The StrOrNull type is going to be used.
To keep the command line compatibility, the parameters need to
continue being exposed via qdev properties accessible from the command
line. Introduce a qdev property StrOrNull just for that.
Note that this code is being kept in migration/options.c as this
version of StrOrNull doesn't need to handle QNULL because it was never
a valid option in the previous command line, which took a string.
Signed-off-by: Fabiano Rosas <[email protected]>
Acked-by: Peter Xu <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: df9c38b19af889eac893adddf09e4e2da60333ea
https://github.com/qemu/qemu/commit/df9c38b19af889eac893adddf09e4e2da60333ea
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M tests/qtest/migration/migration-qmp.c
M tests/qtest/migration/migration-qmp.h
M tests/qtest/migration/tls-tests.c
Log Message:
-----------
tests/qtest/migration: Add a NULL parameters test for TLS
Make sure the TLS options handling is working correctly with a NULL
parameter. This is relevant due to the usage of StrOrNull for the
tls-creds, tls-authz and tls-hostname options.
With this, all manners of passing TLS options are somehow covered by
the tests, we should not need to do manual testing when touching TLS
options code.
Signed-off-by: Fabiano Rosas <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: aed97f0563994a8b0aafa86d267fb842b0a803b4
https://github.com/qemu/qemu/commit/aed97f0563994a8b0aafa86d267fb842b0a803b4
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/migration-hmp-cmds.c
M migration/options.c
M migration/options.h
M migration/tls.c
M qapi/migration.json
Log Message:
-----------
migration: Normalize tls arguments
The migration parameters tls_creds, tls_authz and tls_hostname
currently have a non-uniform handling. When used as arguments to
migrate-set-parameters, their type is StrOrNull and when used as
return value from query-migrate-parameters their type is a plain
string.
Not only having to convert between the types is cumbersome, but it
also creates the issue of requiring two different QAPI types to be
used, one for each command. MigrateSetParameters is used for
migrate-set-parameters with the TLS arguments as StrOrNull while
MigrationParameters is used for query-migrate-parameters with the TLS
arguments as str.
Since StrOrNull could be considered a superset of str, change the type
of the TLS arguments in MigrationParameters to StrOrNull. Also ensure
that QTYPE_QNULL is never used.
1) migrate-set-parameters will always write QTYPE_QSTRING to
s->parameters, either an empty or non-empty string.
2) query-migrate-parameters will always return a QTYPE_QSTRING, either
empty or non-empty.
3) the migrate_tls_* helpers will always return a non-empty string or
NULL, for the internal migration code's consumption.
Points (1) and (2) above help simplify the parameters validation and
the query command handling because s->parameters is already kept in
the format that query-migrate-parameters (and info migrate_paramters)
expect. Point (3) is so people don't need to care about StrOrNull in
migration code.
This will allow the type duplication to be removed in the next
patches.
Note that the type of @tls_creds, @tls-hostname, @tls-authz changes
from str to StrOrNull in introspection of the query-migrate-parameters
command. We accept this imprecision to enable de-duplication.
There's no need to free the TLS options in
migration_instance_finalize() because they're freed by the qdev
properties .release method.
Temporary in this patch:
migrate_params_test_apply() copies s->parameters into a temporary
structure, so it's necessary to drop the references to the TLS options
if they were not set by the user to avoid double-free. This is fixed
in the next patches.
Acked-by: Markus Armbruster <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[peterx: in hmp_info_migrate_parameters(), remove an extra dump of
max_postcopy_bandwidth, introduced likely by accident]
Signed-off-by: Peter Xu <[email protected]>
Commit: 691a83657297719d01b0c7ef0df3d51d3f5f3370
https://github.com/qemu/qemu/commit/691a83657297719d01b0c7ef0df3d51d3f5f3370
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/migration-hmp-cmds.c
M migration/options.c
M qapi/migration.json
Log Message:
-----------
migration: Remove MigrateSetParameters
Now that the TLS options have been made the same between
migrate-set-parameters and query-migrate-parameters, a single type can
be used. Remove MigrateSetParameters.
The TLS options documentation from MigrationParameters were replaced
with the ones from MigrateSetParameters which was more complete.
Acked-by: Markus Armbruster <[email protected]>
Acked-by: Peter Xu <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 2220c2b9ef7f0032d45c3ac7e4f50271c0e4ce36
https://github.com/qemu/qemu/commit/2220c2b9ef7f0032d45c3ac7e4f50271c0e4ce36
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M qapi/migration.json
M qapi/pragma.json
Log Message:
-----------
qapi/migration: Don't document MigrationParameter
The MigrationParameter (singular) enumeration is not part of the
migration QMP API, it's only used for nicely converting HMP strings
into MigrationParameters (plural) members and for providing readline
completion.
Documenting this enum only serves to duplicate documentation between
MigrationParameter and MigrationParameters.
Add an exception to QAPIs pragma.json and stop documenting it.
The generated "QEMU QMP Reference Manual" now lists the enum members
as "Not documented." Tolerable.
Acked-by: Markus Armbruster <[email protected]>
Acked-by: Peter Xu <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 6ab968d5e99f4eb4b9d1476c88fe2894f20ea69c
https://github.com/qemu/qemu/commit/6ab968d5e99f4eb4b9d1476c88fe2894f20ea69c
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/options.c
M migration/ram.c
Log Message:
-----------
migration: Run a post update routine after setting parameters
Some migration parameters are updated immediately once they are set
via migrate-set-parameters. Move that work outside of
migrate_params_apply() and leave that function with the single
responsibility of setting s->parameters and not doing any
side-effects.
Reviewed-by: Peter Xu <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 47979fce03a65e7bb33e60afc873d055fbf68a6a
https://github.com/qemu/qemu/commit/47979fce03a65e7bb33e60afc873d055fbf68a6a
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/migration-hmp-cmds.c
M migration/migration.h
M migration/options.c
Log Message:
-----------
migration: Add a flag to track block-bitmap-mapping input
The QAPI converts an empty list on the block-bitmap-mapping input into
a NULL BitmapMigrationNodeAliasList. The empty list is a valid input
for the block-bitmap-mapping option, so commit 3cba22c9ad ("migration:
Fix block_bitmap_mapping migration") started using the
s->parameters.has_block_bitmap_mapping field to tell when the user has
passed in an empty list vs. when no list has been passed at all.
Using s->parameters.has_block_bitmap_mapping field is only possible
because MigrationParameters has had its members made optional due to
historical reasons.
In order to make improvements to the way configuration options are set
for a migration, we'd like to reduce the open-coded usage of the has_*
fields of the global configuration object (s->parameters).
Add a separate boolean to track the status of the block_bitmap_mapping
option.
No functional change intended.
(this was verified to not regress iotest 300, which is the test that
3cba22c9ad refers to)
CC: Kevin Wolf <[email protected]>
Acked-by: Peter Xu <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 03049e0221e4d73486ac7dbbe33a274129c4ba95
https://github.com/qemu/qemu/commit/03049e0221e4d73486ac7dbbe33a274129c4ba95
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/migration.c
M migration/options.c
Log Message:
-----------
migration: Remove checks for s->parameters has_* fields
The migration parameters validation produces a temporary structure
which is the merge of the current parameter values (s->parameters,
MigrationParameters) with the new parameters set by the user
(former MigrateSetParameters).
When copying the values from s->parameters into the temporary
structure, the has_* fields are copied along, but when merging the
user-input values they are not.
During migrate_params_check(), only the parameters that have the
corresponding has_* field will be checked, so only the parameters that
were initialized in migrate_params_init() will be validated.
This causes (almost) all of the migration parameters to be validated
every time a parameter is set, regardless of which fields the user
touched, but it also skips validation of any values that are not set
in migrate_params_init().
It's not clear what was the intention of the original code, whether to
validate all fields always, or only validate what the user input
changed. Since the current situation is closer to the former option,
make the choice of validating all parameters by removing the checks
for the has_* fields when validating.
Note that bringing the user input into the temporary structure for
validation still needs to look at the has_* fields, otherwise any
parameters not set by the user (i.e. 0) would override the
corresponding value in s->parameters.
The empty migrate_params_init() will be kept because subsequent
patches will add code to it.
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 1a739d30123246b3c34cd9e4c0b475b07e1a3392
https://github.com/qemu/qemu/commit/1a739d30123246b3c34cd9e4c0b475b07e1a3392
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/migration.c
M migration/options.c
M migration/page_cache.c
M migration/ram.c
Log Message:
-----------
migration: Do away with usage of QERR_INVALID_PARAMETER_VALUE
The QERR_INVALID_PARAMETER_VALUE macro is documented as not to be used
in new code. Remove the usage from migration/options.c.
Reviewed-by: Peter Xu <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: f55f4ef6324812ec7ca6a7541b547b7efc4f75f5
https://github.com/qemu/qemu/commit/f55f4ef6324812ec7ca6a7541b547b7efc4f75f5
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/options.c
Log Message:
-----------
migration: Extract code to mark all parameters as present
MigrationParameters needs to have all of its has_* fields marked as
true when used as the return of query_migrate_parameters because the
corresponding QMP command has all of its members non-optional by
design, despite them being marked as optional in migration.json.
Extract this code into a function and make it assert if any field is
missing. With this we ensure future changes will not inadvertently
leave any parameters missing.
Note that the block-bitmap-mapping is a special case because the empty
list is considered a valid value, so it has historically not been
present in the command's output if it has never been set.
CC: Kevin Wolf <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 058f71402ff7686ff222340b01b72f4ed89fba52
https://github.com/qemu/qemu/commit/058f71402ff7686ff222340b01b72f4ed89fba52
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M migration/options.c
Log Message:
-----------
migration: Use QAPI_CLONE_MEMBERS in query_migrate_parameters
QAPI_CLONE_MEMBERS is a better option than copying parameters one by
one because it operates on the entire struct and follows pointers. It
also avoids the need to alter this function every time a new parameter
is added.
For this to work, the has_* fields of s->parameters need to be already
set beforehand, so move migrate_mark_all_params_present() to the init
routine.
Reviewed-by: Peter Xu <[email protected]>
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: 6fea394aa6d4b6ffb7b7631e247ef9de7c59b4fa
https://github.com/qemu/qemu/commit/6fea394aa6d4b6ffb7b7631e247ef9de7c59b4fa
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M tests/qtest/migration/compression-tests.c
M tests/qtest/migration/cpr-tests.c
M tests/qtest/migration/file-tests.c
M tests/qtest/migration/migration-util.c
M tests/qtest/migration/migration-util.h
M tests/qtest/migration/misc-tests.c
M tests/qtest/migration/postcopy-tests.c
M tests/qtest/migration/precopy-tests.c
M tests/qtest/migration/tls-tests.c
Log Message:
-----------
tests/qtest/migration: Pass MigrateCommon into test functions
With the upcoming addition of the config QDict, the tests will need a
better way of managing the memory of the test data than putting the
test arguments on the stack of the test functions. The config QDict
will need to be merged into the arguments of migrate_qmp* functions,
which causes a refcount increment, so the test functions would need to
allocate and deref the config QDict themselves.
A better approach is to already pass the arguments into the test
functions and do the memory management in the existing wrapper. There
is already migration_test_destroy(), which is called for every test.
Do the following:
- merge the two existing wrappers, migration_test_wrapper() and
migration_test_wrapper_full(). The latter was pioneer in passing
data into the tests, but now all tests will receive data, so we
don't need it anymore.
The usage of migration_test_wrapper_full() was in passing a slightly
different test name string into the cancel tests, so still keep the
migration_test_add_suffix() function.
- add (char *name, MigrateCommon *args) to the signature of all test
functions.
- alter any code to stop allocating args on the stack and instead use
the object that came as parameter.
- pass args around as needed.
- while here, order args (MigrateCommon) before args->start
(MigrateStart) and put a blank like in between.
No functional change.
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[peterx: fix a conflict with newly added mapped-ram+ignore-share test]
Signed-off-by: Peter Xu <[email protected]>
Commit: 11e06ae0b51c3558a9bf3554ae8274e08f0634df
https://github.com/qemu/qemu/commit/11e06ae0b51c3558a9bf3554ae8274e08f0634df
Author: Fabiano Rosas <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M tests/qtest/migration/precopy-tests.c
Log Message:
-----------
tests/qtest/migration: Pass MigrateStart into cancel tests
Pass the "args" parameter to the cancel tests so they can access the
config object which will be part of this struct.
Signed-off-by: Fabiano Rosas <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: e8a6d158dbfad09de507ba175e5442156f9b0eff
https://github.com/qemu/qemu/commit/e8a6d158dbfad09de507ba175e5442156f9b0eff
Author: Chuang Xu <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M accel/tcg/cputlb.c
M include/system/physmem.h
M migration/ram.c
M system/memory.c
M system/physmem.c
Log Message:
-----------
migration: merge fragmented clear_dirty ioctls
In our long-term experience in Bytedance, we've found that under
the same load, live migration of larger VMs with more devices is
often more difficult to converge (requiring a larger downtime limit).
Through some testing and calculations, we conclude that bitmap sync time
affects the calculation of live migration bandwidth.
When the addresses processed are not aligned, a large number of
clear_dirty ioctl occur (e.g. a 4MB misaligned memory can generate
2048 clear_dirty ioctls from two different memory_listener),
which increases the time required for bitmap_sync and makes it
more difficult for dirty pages to converge.
For a 64C256G vm with 8 vhost-user-net(32 queue per nic) and
16 vhost-user-blk(4 queue per blk), the sync time is as high as *73ms*
(tested with 10GBps dirty rate, the sync time increases as the dirty
page rate increases), Here are each part of the sync time:
- sync from kvm to ram_list: 2.5ms
- vhost_log_sync:3ms
- sync aligned memory from ram_list to RAMBlock: 5ms
- sync misaligned memory from ram_list to RAMBlock: 61ms
Attempt to merge those fragmented clear_dirty ioctls, then syncing
misaligned memory from ram_list to RAMBlock takes only about 1ms,
and the total sync time is only *12ms*.
Signed-off-by: Chuang Xu <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Link:
https://lore.kernel.org/r/[email protected]
[peterx: drop var "offset" in physical_memory_sync_dirty_bitmap]
Signed-off-by: Peter Xu <[email protected]>
Commit: bcb411a005fdf39b76e99c14f3618c7b70f7774d
https://github.com/qemu/qemu/commit/bcb411a005fdf39b76e99c14f3618c7b70f7774d
Author: David Hildenbrand (Red Hat) <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M MAINTAINERS
Log Message:
-----------
MAINTAINERS: remove David from "Memory API" section
I don't have a lot of capacity to do any maintanance (or even review) of
"Memory API" lately, so remove myself. Fortunately we still do have two
other maintainers and one reviewer :)
Cc: Paolo Bonzini <[email protected]>
Cc: Peter Xu <[email protected]>
Cc: Philippe Mathieu-Daudé <[email protected]>
Signed-off-by: David Hildenbrand (Red Hat) <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Peter Xu <[email protected]>
Commit: bdab1f0c24ea6b9fc7cd2ef87ea24e388d3a6f1c
https://github.com/qemu/qemu/commit/bdab1f0c24ea6b9fc7cd2ef87ea24e388d3a6f1c
Author: Helge Deller <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M pc-bios/hppa-firmware.img
M pc-bios/hppa-firmware64.img
M roms/seabios-hppa
Log Message:
-----------
target/hppa: Update SeaBIOS-hppa to version 21
Some small bugfixes for the 715/64 machine:
- fix CPU detection of 715 in HP-UX and NetBSD
- minor cleanups regarding LASI_SCSI for 715
Signed-off-by: Helge Deller <[email protected]>
Commit: a8df524c8fec18230e6b9335564c9112016c821b
https://github.com/qemu/qemu/commit/a8df524c8fec18230e6b9335564c9112016c821b
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Add null pointer checks
Add nullpointer safety checks in ncr710_request_free() and
ncr710_request_cancelled() to prevent crashed while handing invalid req
structures.
Added to preventing memory corruption, which occured during device
initialization.
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Reviewed-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: 177364fa43c3adc2797dd3f1be2f14ad5118ab0c
https://github.com/qemu/qemu/commit/177364fa43c3adc2797dd3f1be2f14ad5118ab0c
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Fix use after free in command_complete
Add proper hba_private pointer cleanup in ncr710_command_complete.
This prevents use after free errors from occuring.
This was causing memory corruption in NetBSD device initialization
when commands complete and the request structures were freed while
still being referenced.
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Reviewed-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: e17f1e9f0be456c5805f156f4f2513504c5fc18e
https://github.com/qemu/qemu/commit/e17f1e9f0be456c5805f156f4f2513504c5fc18e
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Fix interrupt related register handing
These fixes ensure proper interrupt signaling and status
register behavior during SCSI operations:
- Mask DFE bit in ncr710_update_irq()
- Remove manual ISTAT_DIP clearing, let ncr710_update_irq()
handle it consistently
- Fix SSTAT0 read to clear unconditionally when non zero
- Fix SSTAT2 read was returning DSTAT instead
- Preserve DFE status bit when clearing DSTAT
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Tested-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: 22f10208d711dc11b6c90da8ac749ea0f6e0b673
https://github.com/qemu/qemu/commit/22f10208d711dc11b6c90da8ac749ea0f6e0b673
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Fix DMA State machine and flow control
Set waiting state and return after scsi_req_continue() to prevent
re entrancy when DMA transfer completes.
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Reviewed-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: eb7a22dc2e079b1358e6db12914832c3c77980e9
https://github.com/qemu/qemu/commit/eb7a22dc2e079b1358e6db12914832c3c77980e9
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Fix table indirect addressing endianness
Correct the endianness conversion for table indirect addressing and
use be32_to_cpu() instead of cpu_to_le32().
This fix descriptor table parsing when using indirect addressing modes
in SCRIPTS.
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Reviewed-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: 0cbcd0612bb1d5a26eb1ac459ed3d71d9215daed
https://github.com/qemu/qemu/commit/0cbcd0612bb1d5a26eb1ac459ed3d71d9215daed
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Mark command complete in status phase and fix disconnect
Set command_complete flag after status_phase and use_phase_clearing,
instead of full disconnect during message processing.
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Reviewed-by: Helge Deller <[email protected]>
Tested-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: 3be0f8f7febad1dfe0af90cf55a186e9ce859962
https://github.com/qemu/qemu/commit/3be0f8f7febad1dfe0af90cf55a186e9ce859962
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Add LUN scanning
Add multi LUN support by scanning all 8 LUNs when ANT bit is set.
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Tested-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: 3fb0e0d841940f6c48e0237ca8f82ca65007ad37
https://github.com/qemu/qemu/commit/3fb0e0d841940f6c48e0237ca8f82ca65007ad37
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Simplify disconnect handling
Simplify disconnect instruction by unconditionally clearing waiting
statements when command completes.
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Tested-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: 9a9c2915c423791a979ab783570d536c90b3a213
https://github.com/qemu/qemu/commit/9a9c2915c423791a979ab783570d536c90b3a213
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Fix DSA register
Implement bytewise write handling for DSA register instead of using
the macro, as NetBSD driver accesses it byte by byte.
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Tested-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: 2410c0332a562c5a33cac366a360c4ae33bde795
https://github.com/qemu/qemu/commit/2410c0332a562c5a33cac366a360c4ae33bde795
Author: Soumyajyotii Ssarkar <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
Log Message:
-----------
scsi: ncr710: Fix CTEST FIFO status
Update CTEST1 FIFO status when CTEST8 is written, setting to 0xFF when
FIFO is flushed, otherwise clear to 0x00.
Signed-off-by: Soumyajyotii Ssarkar <[email protected]>
Tested-by: Helge Deller <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: b2c2d00f48cc5f4486cfba33b505ff86d79cb137
https://github.com/qemu/qemu/commit/b2c2d00f48cc5f4486cfba33b505ff86d79cb137
Author: Sven Schnelle <[email protected]>
Date: 2025-12-23 (Tue, 23 Dec 2025)
Changed paths:
M target/hppa/gdbstub.c
Log Message:
-----------
target/hppa: add 64 bit support to gdbstub
Signed-off-by: Sven Schnelle <[email protected]>
Reviewed-by: Helge Deller <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Signed-off-by: Helge Deller <[email protected]>
Commit: 9eef3854d30911d117f85253f1f2a154e4076adf
https://github.com/qemu/qemu/commit/9eef3854d30911d117f85253f1f2a154e4076adf
Author: Philippe Mathieu-Daudé <[email protected]>
Date: 2025-12-26 (Fri, 26 Dec 2025)
Changed paths:
M tests/qtest/fuzz-e1000e-test.c
M tests/qtest/lpc-ich9-test.c
Log Message:
-----------
tests/qtest: Do not use versioned pc-q35-5.0 machine anymore
As of QEMU v10.2.0, the v5.0.0 machines are not usable anymore.
Use the latest x86 q35 machine instead, otherwise we get:
$ qemu-system-x86_64 -M pc-q35-5.0
qemu-system-x86_64: unsupported machine type: "pc-q35-5.0"
Use -machine help to list supported machines
See commit a35f8577a07 ("include/hw: add macros for deprecation
& removal of versioned machines") and f59ee044067 ("include/hw/boards:
cope with dev/rc versions in deprecation checks") for explanation
on automatically removed versioned machines.
Signed-off-by: Philippe Mathieu-Daudé <[email protected]>
Reviewed-by: Fabiano Rosas <[email protected]>
Reviewed-by: Akihiko Odaki <[email protected]>
Link:
https://lore.kernel.org/qemu-devel/[email protected]
Signed-off-by: Fabiano Rosas <[email protected]>
Commit: f96d2014dd9c5eacfbfb3e380091eefafc126158
https://github.com/qemu/qemu/commit/f96d2014dd9c5eacfbfb3e380091eefafc126158
Author: Richard Henderson <[email protected]>
Date: 2025-12-27 (Sat, 27 Dec 2025)
Changed paths:
M MAINTAINERS
M accel/tcg/cputlb.c
M include/qapi/error.h
M include/system/physmem.h
M migration/channel.c
M migration/cpr-exec.c
M migration/migration-hmp-cmds.c
M migration/migration.c
M migration/migration.h
M migration/multifd-device-state.c
M migration/multifd.c
M migration/options.c
M migration/options.h
M migration/page_cache.c
M migration/postcopy-ram.c
M migration/ram.c
M migration/savevm.c
M migration/tls.c
M qapi/migration.json
M qapi/pragma.json
M scripts/analyze-migration.py
M system/memory.c
M system/physmem.c
M tests/qtest/migration/compression-tests.c
M tests/qtest/migration/cpr-tests.c
M tests/qtest/migration/file-tests.c
M tests/qtest/migration/migration-qmp.c
M tests/qtest/migration/migration-qmp.h
M tests/qtest/migration/migration-util.c
M tests/qtest/migration/migration-util.h
M tests/qtest/migration/misc-tests.c
M tests/qtest/migration/postcopy-tests.c
M tests/qtest/migration/precopy-tests.c
M tests/qtest/migration/tls-tests.c
Log Message:
-----------
Merge tag 'next-pull-request' of https://gitlab.com/peterx/qemu into staging
memory + migration pull
- Pawel's misc fixes to mapped-ram when x-ignore-share is enabled
- Peter's series to cleanup migration error reporting
- Peter's added debug property for x-ignore-shared
- Part of Fabiano's series on unify capabilities and parameters
- Chuang's log_clear optimization on unaligned ramblocks
- Maintainer file update from Ben (CPR++) and David (MemoryAPI-)
# -----BEGIN PGP SIGNATURE-----
#
# iIgEABYKADAWIQS5GE3CDMRX2s990ak7X8zN86vXBgUCaUqnKhIccGV0ZXJ4QHJl
# ZGhhdC5jb20ACgkQO1/MzfOr1wbOSgD/b62g/6CnM3WtvzsGhOodjO1vixaYOxXk
# BO5k8x0mea8A/ibOOI4MreDfJ7cx6KtI+Pn2ooyJBPAtMJLYiPvaDmUF
# =KmkA
# -----END PGP SIGNATURE-----
# gpg: Signature made Wed 24 Dec 2025 01:28:58 AM AEDT
# gpg: using EDDSA key B9184DC20CC457DACF7DD1A93B5FCCCDF3ABD706
# gpg: issuer "[email protected]"
# gpg: Good signature from "Peter Xu <[email protected]>" [unknown]
# gpg: aka "Peter Xu <[email protected]>" [unknown]
# gpg: WARNING: The key's User ID is not certified with a trusted signature!
# gpg: There is no indication that the signature belongs to the owner.
# Primary key fingerprint: B918 4DC2 0CC4 57DA CF7D D1A9 3B5F CCCD F3AB D706
* tag 'next-pull-request' of https://gitlab.com/peterx/qemu: (31 commits)
MAINTAINERS: remove David from "Memory API" section
migration: merge fragmented clear_dirty ioctls
tests/qtest/migration: Pass MigrateStart into cancel tests
tests/qtest/migration: Pass MigrateCommon into test functions
migration: Use QAPI_CLONE_MEMBERS in query_migrate_parameters
migration: Extract code to mark all parameters as present
migration: Do away with usage of QERR_INVALID_PARAMETER_VALUE
migration: Remove checks for s->parameters has_* fields
migration: Add a flag to track block-bitmap-mapping input
migration: Run a post update routine after setting parameters
qapi/migration: Don't document MigrationParameter
migration: Remove MigrateSetParameters
migration: Normalize tls arguments
tests/qtest/migration: Add a NULL parameters test for TLS
migration: Add a qdev property for StrOrNull
migration: Fix leak of cpr_exec_command
migration: Fix leak of block_bitmap_mapping
MAINTAINERS: Update reviewers for CPR
migration/options: Add x-ignore-shared
migration: Use error_propagate() in migrate_error_propagate()
...
Signed-off-by: Richard Henderson <[email protected]>
Commit: 83202ca72277873d456d1017b8f3a2db4c6058ad
https://github.com/qemu/qemu/commit/83202ca72277873d456d1017b8f3a2db4c6058ad
Author: Richard Henderson <[email protected]>
Date: 2025-12-27 (Sat, 27 Dec 2025)
Changed paths:
M hw/scsi/ncr53c710.c
M pc-bios/hppa-firmware.img
M pc-bios/hppa-firmware64.img
M roms/seabios-hppa
M target/hppa/gdbstub.c
Log Message:
-----------
Merge tag 'hppa-updates-qemu-v11-pull-request' of
https://github.com/hdeller/qemu-hppa into staging
Please pull fixes and updates for the parisc architecture:
- New SeaBIOS-hppa v21 mit fixes for 715 machine
- ncr710 fixes for NetBSD and HP-UX on 715 machine
- 64-bit gdb support
Thanks!
Helge
# -----BEGIN PGP SIGNATURE-----
#
# iHUEABYKAB0WIQS86RI+GtKfB8BJu973ErUQojoPXwUCaUq53gAKCRD3ErUQojoP
# X0fqAP4wmQIDeyknz4uSZlfaNS7L6HElMrz1jiyyh0avKA/TjwD/UkSvVJJ5Ww7W
# DRx9W5Lg7if93+hQl00QnJGTzgQZQQo=
# =zro8
# -----END PGP SIGNATURE-----
# gpg: Signature made Wed 24 Dec 2025 02:48:46 AM AEDT
# gpg: using EDDSA key BCE9123E1AD29F07C049BBDEF712B510A23A0F5F
# gpg: Good signature from "Helge Deller <[email protected]>" [unknown]
# gpg: aka "Helge Deller <[email protected]>" [unknown]
# gpg: WARNING: This key is not certified with a trusted signature!
# gpg: There is no indication that the signature belongs to the owner.
# Primary key fingerprint: 4544 8228 2CD9 10DB EF3D 25F8 3E5F 3D04 A7A2 4603
# Subkey fingerprint: BCE9 123E 1AD2 9F07 C049 BBDE F712 B510 A23A 0F5F
* tag 'hppa-updates-qemu-v11-pull-request' of
https://github.com/hdeller/qemu-hppa:
target/hppa: add 64 bit support to gdbstub
scsi: ncr710: Fix CTEST FIFO status
scsi: ncr710: Fix DSA register
scsi: ncr710: Simplify disconnect handling
scsi: ncr710: Add LUN scanning
scsi: ncr710: Mark command complete in status phase and fix disconnect
scsi: ncr710: Fix table indirect addressing endianness
scsi: ncr710: Fix DMA State machine and flow control
scsi: ncr710: Fix interrupt related register handing
scsi: ncr710: Fix use after free in command_complete
scsi: ncr710: Add null pointer checks
target/hppa: Update SeaBIOS-hppa to version 21
Signed-off-by: Richard Henderson <[email protected]>
Commit: 5887cb3e2b3ea94d40afe7d7e427c6d9242075f4
https://github.com/qemu/qemu/commit/5887cb3e2b3ea94d40afe7d7e427c6d9242075f4
Author: Richard Henderson <[email protected]>
Date: 2025-12-27 (Sat, 27 Dec 2025)
Changed paths:
M tests/qtest/fuzz-e1000e-test.c
M tests/qtest/lpc-ich9-test.c
Log Message:
-----------
Merge tag 'qtest-20251226-pull-request' of https://gitlab.com/farosas/qemu
into staging
Qtest pull request
- Fix tests using deprecated machine versions
# -----BEGIN PGP SIGNATURE-----
#
# iQJEBAABCAAuFiEEqhtIsKIjJqWkw2TPx5jcdBvsMZ0FAmlOxGMQHGZhcm9zYXNA
# c3VzZS5kZQAKCRDHmNx0G+wxnQ8jEACKyE525JVTSBqa7UTVpU1WMmViHGYoQY1S
# bbGHTnWuMMXHFw0ptF1nMRQbKSZvtOJ7BDYDs/lYhNzKCJJ47/WkHyv9npUH1ttl
# jSbbZz0iN5RrIkRvVv3paiJ+uh3pCOSnThh86eUCf8W+7lwpulYVM5AUTg7cc7Lh
# sTCDbVp6im/tB5ePySUTp7edSc+tEXe1NufmKxOfw7znvn0Aqj+31F5KV39GvyQb
# CpaoPxVI6l6F489EcDiwzLXGoOTG6pmIx0fvDiHiC+u41lwLL/dDsWfXS03EdQmu
# GXD0SKSp7ta0QhxvhSlmasM/YqNIeXGGdNeAEVvoZdV9jm3KIFZViOqa7ObPxlGO
# h8ZBM3mwkDzLcszp1F1UF5a0HoBUv7F788W1Ocn3QEumFS2UmOG1xJ6vWhBCWOyC
# n6XrA9ollxuqpBL+wkZF1fKeFWQp0+umsaosQoC1l3+dw0MIgwf0wwncMD0XNMhO
# L3pRkH/kgNo0C6U4CwujpXtel3Q0C51+6kSzpKFUgpt/5Igd30jdDEszbrv1HKFB
# ZrTOuTFPOPIH9+BVZYbId4deyUUcs0zUNUO+xpizBuq4kNg1npxGLJO77kNYOSdJ
# TurJcyAkwQp9Wd0kcMzXOVA0qKJvmsWtX36GCBhrecaW+sWLq8b8uYv8LBdFvaRh
# 3Z5depSLQQ==
# =n+cs
# -----END PGP SIGNATURE-----
# gpg: Signature made Sat 27 Dec 2025 04:22:43 AM AEDT
# gpg: using RSA key AA1B48B0A22326A5A4C364CFC798DC741BEC319D
# gpg: issuer "[email protected]"
# gpg: Good signature from "Fabiano Rosas <[email protected]>" [unknown]
# gpg: aka "Fabiano Almeida Rosas <[email protected]>"
[unknown]
# gpg: WARNING: The key's User ID is not certified with a trusted signature!
# gpg: There is no indication that the signature belongs to the owner.
# Primary key fingerprint: AA1B 48B0 A223 26A5 A4C3 64CF C798 DC74 1BEC 319D
* tag 'qtest-20251226-pull-request' of https://gitlab.com/farosas/qemu:
tests/qtest: Do not use versioned pc-q35-5.0 machine anymore
Signed-off-by: Richard Henderson <[email protected]>
Compare: https://github.com/qemu/qemu/compare/8208694e5677...5887cb3e2b3e
To unsubscribe from these emails, change your notification settings at
https://github.com/qemu/qemu/settings/notifications
