Hi Amazon,
I have install the latest SDK and current version is 0.20.3719. But after the installation, Simulator is not starting and it is showing only boot process. I have checked all possible solution from documentation and FAQ but still simulator is not starting.
Hi @ABP_Network
We are investigating this issue and will provide an update as soon as we have more information.
In the meantime, please try this:
kepler virtual-device stopkepler virtual-device startkepler device listThis will delete the existing VVD state and create a fresh instance, which often resolves boot issues.
Warm regards,
Ivy
Hello there,
The long boot time issue you are experiencing can be caused by multiple factors. In order to better understand the root cause, we would need some additional information about your environment.
As a first step, please try increasing the timeout for the Kepler Virtual Device startup process to allow more time for the virtual device to complete the boot sequence before the process is terminated. You can do this by following the documentation below:
kepler device simulator start --timeout 600
If this still fails, it is possible that the virtual device instance was corrupted during creation. In that case, please delete the following directory and try starting the virtual device again:
/Users/<username>/kepler/sdk/<version>/kvd/instances/<random-hash>/
If the problem persists, could you please share the following information with us:
The full console output you receive.
The virtual_device.err and virtual_device.out files located under the instance folder:
/Users/<username>/kepler/sdk/<version>/kvd/instances/<random-hash>/
Your computer architecture and operating system (for example, Intel vs Apple Silicon, macOS version, or Linux distribution)
This information will help us further investigate the issue.
Best regards,
Eder
Hi Edernava
I followed your steps, but the problem still persists. I also removed the SDK and reinstalled it, but the simulator is still not starting. It is stuck on booting. I am sharing the details you asked for.
Drive Link for the virtual_device.err and virtual_device.out file
Hi
I have reinstall the SDK but simulator is not starting . it is showing only in boot state. could you help to resolve it on priority ?
Hi,
We’ve been trying to reproduce your issue in a similar environment, but the Virtual Device runs correctly on our side. This suggests that the problem may be environment-specific.
Unfortunately, the stdout and stderr files you shared didn’t provide enough information to identify the root cause. Could you please run the following commands so we can better understand what might be happening on your end? Please share the output of each one.
kepler device simulator start --timeout 800
vda devices
vda shell systemctl list-jobs
vda shell systemd-analyze
vda shell journalctl -f > logs.txt
Please press Ctrl + C when you want to stop the log collection.
This will generate a logs.txt file—could you share that file with us?
Thank you!
Hi
Sharing the details as you asked. Kindly look and suggest the solution. I have reinstall the sdk many times but problem is persistent yet.
logs.txt (18.0 MB)
Hi,
Thank you for sharing the information requested.
After analyzing the boot logs, we’ve found what appears to be a compatibility issue with SDK version 0.20.3719 that’s causing the simulator to get stuck on the FireTV logo.
We’re escalating this to the corresponding team for further investigation.
Best regards,
Monica
Hi,
To better understand your environment, could you please provide the output of the following commands?
Please run these commands in your terminal and share the results with us:
which kepler (The expected output should look like: /home//kepler/sdk/0.20.3719/bin/kepler)
Then, please run:
cat /Users/$USER/kepler/sdk/0.20.3719/sdk-info.toml
And finally:
ls -al /home/$USER/kepler/sdk/0.20.3719/kvd/images/tv/image_files/
Based on the screenshot you provided, it looks like you may have previously installed Kepler
Native SDK, which is incompatible with SDK 0.20. Could you confirm if this is the case?
Thank you!
Hi Monica,
Thanks for your prompt reply.
Below is the response in bold text of your query.
which kepler – > /Users/adityak/kepler/sdk/0.20.3719/bin/kepler
cat /Users/$USER/kepler/sdk/0.20.3719/sdk-info.toml. – >
Package = “Kepler SDK”
Build_Version = “0.20.3719”
ls -al /home/$USER/kepler/sdk/0.20.3719/kvd/images/tv/image_files/ →
ls: /home/adityak/kepler/sdk/0.20.3719/kvd/images/tv/image_files/: No such file or directory
Hi, thanks a lot for your response.
Apologies, I think there was a small typo in the last command. The correct command should be:
ls -al /Users/$USER/kepler/sdk/0.20.3719/kvd/images/tv/image_files/
From the output of which kepler and the cat command, we can see that your path starts with /Users/$USER/...
Could you run the corrected command again and share the output with us?
Thank you!
Hi Monica
Below is the response of command
adityak@MacBookPro abp-kepler-os-app % ls -al /Users/$USER/kepler/sdk/0.20.3719/kvd/images/tv/image_files/
total 18884480
drwxr-xr-x 14 adityak staff 448 Sep 3 12:03 .
drwxr-xr-x 4 adityak staff 128 Sep 3 12:03 ..
-rw-r–r-- 1 adityak staff 1048576 Sep 3 12:03 bootloader
-rw-r–r-- 1 adityak staff 13056928 Sep 3 12:36 bzImage
-rw-r–r-- 1 adityak staff 134217728 Sep 3 12:03 cache.ext4
-rw-r–r-- 1 adityak staff 665 Sep 3 12:02 config.ini
-rw-r–r-- 1 adityak staff 0 Sep 3 12:03 dhav2-tv
-rw-r–r-- 1 adityak staff 4194304 Sep 3 12:03 idme.img
-rw-r–r-- 1 adityak staff 15658871 Sep 3 12:02 initramfs.cpio.gz
-rw-r–r-- 1 adityak staff 8388608 Sep 3 12:03 keys.ext4
-rw-r–r-- 1 adityak staff 1048576 Sep 3 12:03 misc.img
-rw-r–r-- 1 adityak staff 3010146304 Sep 3 12:36 system.ext4
-rw-r–r-- 1 adityak staff 6442450944 Sep 3 12:03 userdata.ext4
-rw-r–r-- 1 adityak staff 38637568 Sep 3 12:03 vendor.ext4
adityak@MacBookPro abp-kepler-os-app %
Hi Monica and Amazon Team,
Any update ?
Hi @ABP_Network
I understand it’s taking too long at our end, I appreciate your patience !
We are still working on your issue. I’ll let you know once we have an update.
Warm regards,
Ivy
Hi @ABP_Network, sorry for the long wait. I wasn’t able to reproduce your experience on 0.20.3719 which makes me think it’s an issue with your local environment. Could you try running the following command which deletes the state for the virtual device?
rm -rf ~/kepler/sdk/0.20.3719/kvd/instances/*
Then you can try running it again with kepler device simulator start. We’d like to understand the root cause of your issue, but another option to get you going is to download and install v0.21.
Hi Andrew ,
Thanks for reply.
I have applied the suggestion you shared, but the problem still persists. Sharing the screenshot for your reference.
Also, SDK v0.21 is not available to download yet.
Hi @ABP_Network,
I strongly suggest updating the SDK version, currently, the latest one is v0.22.
You can follow the guide to install it here: Install the Vega SDK | Vega Get Started . Here you can select your operating system and the SDK version by updating the dropdown selections.
This is the command to execute to install SDK v0.22 for a Mac Intel:
curl -fsSL https://kepler-static-artifacts.kepler.labcollab.net/24/240c5fecec4f96b859383d67eecbda642430990d0048a917c3afcd9b12067d72 | bash -s -- --sdk-url=https://kepler-static-artifacts.kepler.labcollab.net/b5/b52b3167f76d9423d5b0f5b2e6659c2454823d4d64ef9ce3d7839b84b43cb2c5 --sim-url=https://kepler-static-artifacts.kepler.labcollab.net/a5/a575495837f49f34d15e2c4a1a02edcc512411c46d8f52fa594546c25f6a0872 --version=0.22.5600 --directed-id=amzn1.account.AH2PH565A6OCRD7DAEW7UEDJNPVQ
Could you update the SDK and execute vega virtual-device start
Hi Monica,
But SDK v0.22 is not showing in my machine to download the latest SDK. Could you provide the command to install the latest SDK to resolve the boot issue in simulator ? I am not able to write the code for kepler due to simulator issue.
Hello @ABP_Network,
Sure, here is the command to install SDK v0.22 on a Mac Intel:
curl -fsSL ``https://kepler-static-artifacts.kepler.labcollab.net/24/240c5fecec4f96b859383d67eecbda642430990d0048a917c3afcd9b12067d72`` | bash -s – --sdk-url=https://kepler-static-artifacts.kepler.labcollab.net/b5/b52b3167f76d9423d5b0f5b2e6659c2454823d4d64ef9ce3d7839b84b43cb2c5 --sim-url=https://kepler-static-artifacts.kepler.labcollab.net/a5/a575495837f49f34d15e2c4a1a02edcc512411c46d8f52fa594546c25f6a0872 --version=0.22.5600 --directed-id=amzn1.account.AH2PH565A6OCRD7DAEW7UEDJNPVQ
Alternatively, you can run:
curl -fsSL ``https://sdk-installer.vega.labcollab.net/get_vvm.sh`` | bash && source ~/vega/env
After updating the SDK, could you please run vega virtual-device start again?
Regarding the issue where you are not seeing the latest SDK versions, could you please check the following site: https://developer.amazon.com/docs/vega/latest/install-vega-sdk.html
In your screenshot, I noticed that the page shown is “Kepler Developer Docs.”
Is that link redirecting you to that site?
The current and correct documentation is now under “Vega Developer Docs”:
https://developer.amazon.com/apps-and-games/vega
Hi Monica
Could you share the command/script to remove the previous instance of Kepler ? I want to remove the previous instance before downloading the latest sdk to resolve the simulator booting issue.
