1. This is simpler, as it can be triggered by logic in the init.rc 2. The old method of probing /dev/kvm fails if non-protected kvm is enabled: the device will exist, but pkvm is not enable Bug: 346525496 Test: observe that pkvm is enabled after double reboot Change-Id: I2f557ed56f13458a288ede34e672692b511b6bc9
11 lines
453 B
Text
11 lines
453 B
Text
service pkvm_enabler /vendor/bin/pkvm_enabler
|
|
reboot_on_failure reboot,pkvm-not-enabled
|
|
user root
|
|
|
|
# Old bootloaders do not set the protected_vm sysprop when pkvm is disabled
|
|
on early-init && property:ro.boot.hypervisor.protected_vm.supported=
|
|
exec_start pkvm_enabler
|
|
|
|
# New bootloaders set the protected_vm sysprop to 0 when pkvm is disabled
|
|
on early-init && property:ro.boot.hypervisor.protected_vm.supported=0
|
|
exec_start pkvm_enabler
|