You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built a kernel using linux-4.9.139 and clang toolchains to get Image.gz
I want to run a virtual emulator with it, I've tried API24 x86_64 & API30 x86 but both didn't work
noah@kali-noah:~/Android/Sdk/emulator$ ./emulator -avd API24 -kernel $HOME/linux-4.9.139/out/arch/arm64/boot/Image.gz -show-kernel
emulator: ERROR: Running multiple emulators with the same AVD is an experimental feature.
Please use -read-only flag to enable this feature.
noah@kali-noah:~/Android/Sdk/emulator$ ./emulator -avd API30 -kernel $HOME/linux-4.9.139/out/arch/arm64/boot/Image.gz -show-kernel
emulator: ERROR: Unknown AVD name [API30], use -list-avds to see valid list.
HOME is defined but there is no file API30.ini in $HOME/.android/avd
(Note: Directories are searched in the order $ANDROID_AVD_HOME, $ANDROID_SDK_HOME/avd and $HOME/.android/avd)
The text was updated successfully, but these errors were encountered:
noah@kali-noah:~/Android/Sdk/emulator$ uname -r
5.7.0-kali1-amd64
I built a kernel using linux-4.9.139 and clang toolchains to get Image.gz
I want to run a virtual emulator with it, I've tried API24 x86_64 & API30 x86 but both didn't work
noah@kali-noah:~/Android/Sdk/emulator$ ./emulator -avd API24 -kernel $HOME/linux-4.9.139/out/arch/arm64/boot/Image.gz -show-kernel
emulator: ERROR: Running multiple emulators with the same AVD is an experimental feature.
Please use -read-only flag to enable this feature.
noah@kali-noah:~/Android/Sdk/emulator$ ./emulator -avd API30 -kernel $HOME/linux-4.9.139/out/arch/arm64/boot/Image.gz -show-kernel
emulator: ERROR: Unknown AVD name [API30], use -list-avds to see valid list.
HOME is defined but there is no file API30.ini in $HOME/.android/avd
(Note: Directories are searched in the order $ANDROID_AVD_HOME, $ANDROID_SDK_HOME/avd and $HOME/.android/avd)
The text was updated successfully, but these errors were encountered: