db5d2a4b77
where there is no good reason to keep them separate. It's a pain during rebase if there are multiple patches changing the same code over and over again. This was especially bad for the backup-related patches. If the history of patches really is needed, it can be extracted via git. Additionally, compilation with partial application of patches was broken since a long time, because one of the master key changes became part of an earlier patch during a past rebase. If only the same files were changed by a subsequent patch and the changes felt to belong together (obvious for later bug fixes, but also done for features e.g. adding master key support for PBS), the patches were squashed together. The PBS namespace support patch was split into the individual parts it changes, i.e. PBS block driver, pbs-restore binary and QMP backup infrastructure, and squashed into the respective patches. No code change is intended, git diff in the submodule should not show any difference between applying all patches before this commit and applying all patches after this commit. The query-proxmox-support QMP function has been left as part of the "PVE-Backup: Proxmox backup patches for QEMU" patch, because it's currently only used there. If it ever is used elsewhere too, it can be split out from there. The recent alloc-track and BQL-related savevm-async changes have been left separate for now, because it's not 100% clear they are the best approach yet. This depends on what upstream decides about the BQL stuff and whether and what kind of issues with the changes pop up. The qemu-img dd snapshot patch has been re-ordered to after the other qemu-img dd patches. Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
42 lines
1.8 KiB
Diff
42 lines
1.8 KiB
Diff
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
|
|
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
|
|
Date: Mon, 6 Apr 2020 12:16:54 +0200
|
|
Subject: [PATCH] PVE: [Compat]: 4.0 used balloon qemu-4-0-config-size false
|
|
here
|
|
|
|
The underlying issue why this change from upstream to us arised in
|
|
the first place is that QEMU 4.0 was already released at the point we
|
|
run into this migration issue, so we did the then obvious fallback to
|
|
false for virtio-balloon-device qemu-4-0-config-size.
|
|
|
|
QEMU made that switch back in 4.1, where it now uses a backward
|
|
compatible mechanism to detect if the bigger CFG sizes should be
|
|
used, i.e., checking the VIRTIO_BALLOON_F_PAGE_POISON or
|
|
VIRTIO_BALLOON_F_FREE_PAGE_HINT balloon feature flags.
|
|
As for them, upstream released version 4.0 had this to true they keep
|
|
it to true in their compatibility record for the 4.0 machine, to
|
|
allow live migrations from 4.0 to 4.1.
|
|
As for us, downstream released version 4.0 (first public release of
|
|
this QEMU) had this to false, we change it back to false again, for
|
|
the same reason.
|
|
|
|
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
|
|
---
|
|
hw/core/machine.c | 3 ++-
|
|
1 file changed, 2 insertions(+), 1 deletion(-)
|
|
|
|
diff --git a/hw/core/machine.c b/hw/core/machine.c
|
|
index 5060119952..9d1c358c12 100644
|
|
--- a/hw/core/machine.c
|
|
+++ b/hw/core/machine.c
|
|
@@ -142,7 +142,8 @@ GlobalProperty hw_compat_4_0[] = {
|
|
{ "virtio-vga", "edid", "false" },
|
|
{ "virtio-gpu-device", "edid", "false" },
|
|
{ "virtio-device", "use-started", "false" },
|
|
- { "virtio-balloon-device", "qemu-4-0-config-size", "true" },
|
|
+ // PVE differed from upstream for 4.0 balloon cfg size
|
|
+ { "virtio-balloon-device", "qemu-4-0-config-size", "false" },
|
|
{ "pl031", "migrate-tick-offset", "false" },
|
|
};
|
|
const size_t hw_compat_4_0_len = G_N_ELEMENTS(hw_compat_4_0);
|