On 5/10/23 13:20, Juan Quintela wrote:
Richard Henderson <richard.hender...@linaro.org> wrote:
On 5/9/23 20:17, Juan Quintela wrote:
The following changes since commit 271477b59e723250f17a7e20f139262057921b6a:
    Merge tag 'compression-code-pull-request' of
https://gitlab.com/juan.quintela/qemu into staging (2023-05-08
20:38:05 +0100)
are available in the Git repository at:
    https://gitlab.com/juan.quintela/qemu.git
tags/migration-20230509-pull-request
for you to fetch changes up to
5f43d297bc2b9530805ad8602c6e2ea284b08628:
    migration: block incoming colo when capability is disabled
(2023-05-09 20:52:21 +0200)
----------------------------------------------------------------
Migration Pull request (20230509 vintage)
Hi
In this PULL request:
- 1st part of colo support for multifd (lukas)
- 1st part of disabling colo option (vladimir)
Please, apply.

Build failures.

https://gitlab.com/qemu-project/qemu/-/jobs/4257605099#L2241

    85 | void colo_record_bitmap(RAMBlock *block, ram_addr_t *normal, uint 
normal_num);
       |                                                              ^~~~
       |                                                              u_int


Grrr

And the worst thing is that hate those types, tried to get then out
long, long ago for a similar problem.

Where do these types come from, and can we poison them on the qemu side?


r~


Reply via email to