Allow protected VMs to run with full debugging
Enforcing this in VirtualizationService is not sufficient and seems
unnecessary. Remove it to allow easier development of VMs. The
enforcement must be done within the VM.
Bug: 219028028
Test: atest MicrodroidTests
Change-Id: Icb51bc035d77564044328a74b3490cebb472c784
diff --git a/virtualizationservice/src/aidl.rs b/virtualizationservice/src/aidl.rs
index 7e0c634..505eb0c 100644
--- a/virtualizationservice/src/aidl.rs
+++ b/virtualizationservice/src/aidl.rs
@@ -177,13 +177,6 @@
}
let is_app_config = matches!(config, VirtualMachineConfig::AppConfig(_));
- let is_debug_level_full = matches!(
- config,
- VirtualMachineConfig::AppConfig(VirtualMachineAppConfig {
- debugLevel: DebugLevel::FULL,
- ..
- })
- );
let config = match config {
VirtualMachineConfig::AppConfig(config) => BorrowedOrOwned::Owned(
@@ -201,14 +194,6 @@
let config = config.as_ref();
let protected = config.protectedVm;
- // Debug level FULL is only supported for non-protected VMs.
- if is_debug_level_full && protected {
- return Err(new_binder_exception(
- ExceptionCode::SERVICE_SPECIFIC,
- "FULL debug level not supported for protected VMs.",
- ));
- };
-
// Check if partition images are labeled incorrectly. This is to prevent random images
// which are not protected by the Android Verified Boot (e.g. bits downloaded by apps) from
// being loaded in a pVM. Specifically, for images in the raw config, nothing is allowed