> * When would you (roughly) expect an AMI to be available?
it's too early to say, there are various steps before the fix lands in an AMI.
> * How high is your confidence in the 40-vm-hotadd.rules change workaround? Sounds like very high?
100%. if it doesn't work for you, please let me know.
> * For those of us who are not knowledgeable about this subsystem, are there any drawbacks or things to watch out for if we change 40-vm-hotadd.rules?
not for this specific case. AWS doesn't use ballooning or any kind of memory hotplug (that I am aware of...Matt can correct me if that is wrong), so there is no issue with disabling it inside an AWS instance.
> * When would you (roughly) expect an AMI to be available?
it's too early to say, there are various steps before the fix lands in an AMI.
> * How high is your confidence in the 40-vm-hotadd.rules change workaround? Sounds like very high?
100%. if it doesn't work for you, please let me know.
> * For those of us who are not knowledgeable about this subsystem, are there any drawbacks or things to watch out for if we change 40-vm-hotadd.rules?
not for this specific case. AWS doesn't use ballooning or any kind of memory hotplug (that I am aware of...Matt can correct me if that is wrong), so there is no issue with disabling it inside an AWS instance.