vitalif
/
pve-qemu
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
pve-qemu/debian/patches/pve/0003-PVE-Config-set-the-CPU...

28 lines
933 B
Diff
Raw Normal View History

patch cleanup Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2018-02-19 12:38:54 +03:00
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
import stable-4 build files
2017-04-05 11:49:19 +03:00
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
import QEMU 5.0.0-rc2 and rebase patches Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2020-04-07 17:53:19 +03:00
Date: Mon, 6 Apr 2020 12:16:32 +0200
Subject: [PATCH] PVE: [Config] set the CPU model to kvm64/32 instead of
bump version to 3.0.0-1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2018-08-30 16:00:07 +03:00
qemu64/32
import stable-4 build files
2017-04-05 11:49:19 +03:00
update patches for v4.0.0 Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2019-06-06 13:58:15 +03:00
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
import stable-4 build files
2017-04-05 11:49:19 +03:00
---
bump version to 2.11.1-1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2018-02-22 14:34:57 +03:00
target/i386/cpu.h | 4 ++--
import stable-4 build files
2017-04-05 11:49:19 +03:00
1 file changed, 2 insertions(+), 2 deletions(-)
bump version to 2.11.1-1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2018-02-22 14:34:57 +03:00
diff --git a/target/i386/cpu.h b/target/i386/cpu.h
update submodule and patches to 7.2.0 User-facing breaking change: The slirp submodule for user networking got removed. It would be necessary to add the --enable-slirp option to the build and/or install the appropriate library to continue building it. Since PVE is not explicitly supporting it, it would require additionally installing the libslirp0 package on all installations and there is *very* little mention on the community forum when searching for "slirp" or "netdev user", the plan is to only enable it again if there is some real demand for it. Notable changes: * The big change for this release is the rework of job locking, using a job mutex and introducing _locked() variants of job API functions moving away from call-side AioContext locking. See (in the qemu submodule) commit 6f592e5aca ("job.c: enable job lock/unlock and remove Aiocontext locks") and previous commits for context. Changes required for the backup patches: * Use WITH_JOB_LOCK_GUARD() and call the _locked() variant of job API functions where appropriate (many are only availalbe as a _locked() variant). * Remove acquiring/releasing AioContext around functions taking the job mutex lock internally. The patch introducing sequential transaction support for jobs needs to temporarily unlock the job mutex to call job_start() when starting the next job in the transaction. * The zeroinit block driver now marks its child as primary. The documentation in include/block/block-common.h states: > Filter node has exactly one FILTERED|PRIMARY child, and may have > other children which must not have these bits Without this, an assert will trigger when copying to a zeroinit target with qemu-img convert, because bdrv_child_cb_attach() expects any non-PRIMARY child to be not FILTERED: > qemu-img convert -n -p -f raw -O raw input.raw zeroinit:output.raw > qemu-img: ../block.c:1476: bdrv_child_cb_attach: Assertion > `!(child->role & BDRV_CHILD_FILTERED)' failed. Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
2022-12-14 17:16:32 +03:00
index d4bc19577a..be7da64f38 100644
bump version to 2.11.1-1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2018-02-22 14:34:57 +03:00
--- a/target/i386/cpu.h
+++ b/target/i386/cpu.h
update submodule and patches to 7.2.0 User-facing breaking change: The slirp submodule for user networking got removed. It would be necessary to add the --enable-slirp option to the build and/or install the appropriate library to continue building it. Since PVE is not explicitly supporting it, it would require additionally installing the libslirp0 package on all installations and there is *very* little mention on the community forum when searching for "slirp" or "netdev user", the plan is to only enable it again if there is some real demand for it. Notable changes: * The big change for this release is the rework of job locking, using a job mutex and introducing _locked() variants of job API functions moving away from call-side AioContext locking. See (in the qemu submodule) commit 6f592e5aca ("job.c: enable job lock/unlock and remove Aiocontext locks") and previous commits for context. Changes required for the backup patches: * Use WITH_JOB_LOCK_GUARD() and call the _locked() variant of job API functions where appropriate (many are only availalbe as a _locked() variant). * Remove acquiring/releasing AioContext around functions taking the job mutex lock internally. The patch introducing sequential transaction support for jobs needs to temporarily unlock the job mutex to call job_start() when starting the next job in the transaction. * The zeroinit block driver now marks its child as primary. The documentation in include/block/block-common.h states: > Filter node has exactly one FILTERED|PRIMARY child, and may have > other children which must not have these bits Without this, an assert will trigger when copying to a zeroinit target with qemu-img convert, because bdrv_child_cb_attach() expects any non-PRIMARY child to be not FILTERED: > qemu-img convert -n -p -f raw -O raw input.raw zeroinit:output.raw > qemu-img: ../block.c:1476: bdrv_child_cb_attach: Assertion > `!(child->role & BDRV_CHILD_FILTERED)' failed. Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
2022-12-14 17:16:32 +03:00
@@ -2174,9 +2174,9 @@ uint64_t cpu_get_tsc(CPUX86State *env);
bump version to 3.0.0-1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2018-08-30 16:00:07 +03:00
#define CPU_RESOLVING_TYPE TYPE_X86_CPU
bump version to 2.11.1-1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2018-02-22 14:34:57 +03:00
import stable-4 build files
2017-04-05 11:49:19 +03:00
#ifdef TARGET_X86_64
bump version to 2.11.1-1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2018-02-22 14:34:57 +03:00
-#define TARGET_DEFAULT_CPU_TYPE X86_CPU_TYPE_NAME("qemu64")
+#define TARGET_DEFAULT_CPU_TYPE X86_CPU_TYPE_NAME("kvm64")
import stable-4 build files
2017-04-05 11:49:19 +03:00
#else
bump version to 2.11.1-1 Signed-off-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
2018-02-22 14:34:57 +03:00
-#define TARGET_DEFAULT_CPU_TYPE X86_CPU_TYPE_NAME("qemu32")
+#define TARGET_DEFAULT_CPU_TYPE X86_CPU_TYPE_NAME("kvm32")
import stable-4 build files
2017-04-05 11:49:19 +03:00
#endif
update submodule and patches to 6.2.0 Notable changes: * bdrv_co_p{discard,readv,writev,write_zeroes} function signatures changed, to using int64_t for offsets/bytes and some still had int rather than BrdvRequestFlags for the flags. * job_cancel_sync now has a force parameter. Commit messages in 73895f3838cd7fdaf185cf1dbc47be58844a966f 4cfb3f05627ad82af473e7f7ae113c3884cd04e3 sound like using force=true makes more sense. * Added 3 patches coming in via qemu-stable tag, most important one is to work around a librbd issue. * Added another 3 patches from qemu-devel to fix issue leading to crash when live migrating with iothread. * cluster_size calculation helper changed (see patch pve/0026). * QAPI's if conditionals now use 'CONFIG_FOO' rather than 'defined(CONFIG_FOO)' Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
2022-02-11 12:24:33 +03:00
#define cpu_list x86_cpu_list