From 29b144bd8de7ec865d54191a9cfd99682a0220af Mon Sep 17 00:00:00 2001 From: Josh Lay Date: Mon, 9 Nov 2020 19:22:44 -0600 Subject: [PATCH] improve cleanup --- start-win10 | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/start-win10 b/start-win10 index aa69043..6a49962 100755 --- a/start-win10 +++ b/start-win10 @@ -12,7 +12,7 @@ # - resets host isolation on VM shutdown # # define the CPUs (cores/threads) to isolate for the VM -VM_CORES='0-19,24-43' +VM_CORES='0-20,24-44' # Tip: refer to 'virsh capabilities | grep siblings' # this will show CPU topology information for the host # allows one to pick optimal layout for the VM @@ -38,7 +38,11 @@ sudo sh -c 'sysctl vm.stat_interval=120 ; sysctl kernel.watchdog=0' # attempt to reset shielding, we want to create it with current params # and remove any existing slices from previous VM boots # we want it to be created with current params, such as possibly-changed pinned CPUs -sudo sh -c 'cset shield --reset --sysset=host.slice --userset=windows10.slice ; cset set -d windows10.slice' +sudo cset shield --reset --sysset=host.slice --userset=windows10.slice || echo "something happened resetting shielding" + +# destroy old cpusets +sudo cset set -d windows10.slice || echo "ignoring failure to destroy VM cpuset" +sudo cset set -d host.slice || echo "ignoring failure to destroy host cpuset" # shield cores # userset slice must match the partition defined in libvirt xml, eg: