-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
script: Add scripts to run AOSP on QEMU #413
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nook1208
force-pushed
the
qemu-rme
branch
2 times, most recently
from
January 2, 2025 03:58
50fcbd4
to
87e79ed
Compare
nook1208
changed the title
script: Add init_android_on_qemu.sh
script: Add scripts for qemu-cca
Jan 3, 2025
nook1208
changed the title
script: Add scripts for qemu-cca
script: Add scripts to run aosp on QEMU
Jan 3, 2025
nook1208
changed the title
script: Add scripts to run aosp on QEMU
script: Add scripts to run AOSP on QEMU
Jan 3, 2025
bokdeuk-jeong
approved these changes
Jan 3, 2025
Use the following commands to build & launch android on qemu: ./scripts/init_android_on_qemu.sh ./scripts/qemu-cca.py -aosp A number of patches for CCA support are applied to the host kernel. At the moment, it supports rmm-v1.0-eac5. But it'll be updated to the latest. It's the below branch in islet-project/3rd-android-kernel: common-android15-6.6/cca-host/rmm-v1.0-eac5 If the qemu is launched, you can see information about it like this: The following lines contain useful debugging information: Serial console is disabled; use -console=true to enable it. Logcat output: /home/eom/cuttlefish/instances/cvd-1/logs/logcat Kernel log: /home/eom/cuttlefish/instances/cvd-1/kernel.log Launcher log: /home/eom/cuttlefish/instances/cvd-1/logs/launcher.log Instance configuration: /home/eom/cuttlefish/instances/cvd-1/cuttlefish_config.json Launcher Build ID: eng.eom After the virtual device booted, you can see the following: VIRTUAL_DEVICE_BOOT_COMPLETED Virtual device booted successfully Then, check your device using adb: $ adb devices List of devices attached 0.0.0.0:6520 device $ adb shell vsoc_arm64_only:/ $ uname -a Linux localhost 6.6.57-android15-8-maybe-dirty-4k #1 SMP PREEMPT Thu Jan 1 00:00:00 UTC 1970 aarch64 Toybox Signed-off-by: Sunwook Eom <[email protected]>
Signed-off-by: Sunwook Eom <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use the following command to build & launch android on qemu:
./script/init_android_on_qemu.sh
./scripts/qemu-cca.py -aosp
A number of patches for CCA support are applied to the host kernel. At the moment, it supports rmm-v1.0-eac5. But it'll be updated to the latest.
It's the below branch in islet-project/3rd-android-kernel:
common-android15-6.6/cca-host/rmm-v1.0-eac5
If the qemu is launched, you can see information about it like this:
"The following lines contain useful debugging information:
Serial console is disabled; use -console=true to enable it.
Logcat output: /home/eom/cuttlefish/instances/cvd-1/logs/logcat
Kernel log: /home/eom/cuttlefish/instances/cvd-1/kernel.log
Launcher log: /home/eom/cuttlefish/instances/cvd-1/logs/launcher.log
Instance configuration: /home/eom/cuttlefish/instances/cvd-1/cuttlefish_config.json
Launcher Build ID: eng.eom"
After the virtual device booted, you can see the following:
VIRTUAL_DEVICE_BOOT_COMPLETED
Virtual device booted successfully
Then, check your device using adb:
$ adb devices
List of devices attached
0.0.0.0:6520 device
$ adb shell
vsoc_arm64_only:/ $ uname -a
Linux localhost 6.6.57-android15-8-maybe-dirty-4k #1 SMP PREEMPT Thu Jan 1 00:00:00 UTC 1970 aarch64 Toybox