For those watching this bug, to work around this until there is an AMI available that fixes it, you can disable udev memory hotadd by changing the /lib/udev/rules.d/40-vm-hotadd.rules file to comment out the memory hotadd rule, like this:
--- /lib/udev/rules.d/40-vm-hotadd.rules.old 2017-03-01 22:02:39.905314616 +0000 +++ /lib/udev/rules.d/40-vm-hotadd.rules 2017-03-01 22:02:46.797002312 +0000 @@ -6,7 +6,7 @@ LABEL="vm_hotadd_apply"
# Memory hotadd request -SUBSYSTEM=="memory", ACTION=="add", DEVPATH=="/devices/system/memory/memory[0-9]*", TEST=="state", ATTR{state}="online" +#SUBSYSTEM=="memory", ACTION=="add", DEVPATH=="/devices/system/memory/memory[0-9]*", TEST=="state", ATTR{state}="online"
# CPU hotadd request SUBSYSTEM=="cpu", ACTION=="add", DEVPATH=="/devices/system/cpu/cpu[0-9]*", TEST=="online", ATTR{online}="1"
For those watching this bug, to work around this until there is an AMI available that fixes it, you can disable udev memory hotadd by changing the /lib/udev/ rules.d/ 40-vm-hotadd. rules file to comment out the memory hotadd rule, like this:
--- /lib/udev/ rules.d/ 40-vm-hotadd. rules.old 2017-03-01 22:02:39.905314616 +0000 rules.d/ 40-vm-hotadd. rules 2017-03-01 22:02:46.797002312 +0000 "vm_hotadd_ apply"
+++ /lib/udev/
@@ -6,7 +6,7 @@
LABEL=
# Memory hotadd request ="memory" , ACTION=="add", DEVPATH= ="/devices/ system/ memory/ memory[ 0-9]*", TEST=="state", ATTR{state} ="online" ="memory" , ACTION=="add", DEVPATH= ="/devices/ system/ memory/ memory[ 0-9]*", TEST=="state", ATTR{state} ="online"
-SUBSYSTEM=
+#SUBSYSTEM=
# CPU hotadd request ="/devices/ system/ cpu/cpu[ 0-9]*", TEST=="online", ATTR{online}="1"
SUBSYSTEM=="cpu", ACTION=="add", DEVPATH=