There's no errors in the dmesg because that's taken from a clean boot. When the guest runs and the PV drivers start, then the logs start flooding with: [34279.205229] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [34281.237272] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [34285.269255] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [34287.309223] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [34291.349232] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [34299.397263] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [34315.461233] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [34347.557236] xen:balloon: reserve_additional_memory: add_memory() failed: -17
Is there any way of disabling the message?
There's no errors in the dmesg because that's taken from a clean boot. additional_ memory: add_memory() failed: -17 additional_ memory: add_memory() failed: -17 additional_ memory: add_memory() failed: -17 additional_ memory: add_memory() failed: -17 additional_ memory: add_memory() failed: -17 additional_ memory: add_memory() failed: -17 additional_ memory: add_memory() failed: -17 additional_ memory: add_memory() failed: -17
When the guest runs and the PV drivers start, then the logs start flooding with:
[34279.205229] xen:balloon: reserve_
[34281.237272] xen:balloon: reserve_
[34285.269255] xen:balloon: reserve_
[34287.309223] xen:balloon: reserve_
[34291.349232] xen:balloon: reserve_
[34299.397263] xen:balloon: reserve_
[34315.461233] xen:balloon: reserve_
[34347.557236] xen:balloon: reserve_
Is there any way of disabling the message?