Troubleshoot Vega Virtual Device Issues
This page provides solutions for common Vega Virtual Device (VVD) issues. If you don't find a solution to your specific problem here, post an issue in Developer Forum for additional support.
Unable to register Vega Virtual Device for Amazon service
Cause: The Vega Virtual Device requires registration before you can use any Amazon services for testing. Without completing the registration process, your app can't access Amazon services on virtual device.
Solution:
- Click "Register this device" on the top right.
- Record the registration code shown on screen.
- Go to www.amazon.com/code and enter the code.
Look for this message to confirm registration:
Your device has successfully been registered
VVD crashes due to low memory
Cause: VVD may crash when running multiple resource-intensive processes (such as screen, audio, and video recording) simultaneously. High memory usage creates memory pressure, causing VVD to crash.
Solution: Check memory usage while VVD is running.
On Mac:
- Open Activity Monitor (Applications > Utilities > Activity Monitor).
- Click the "Memory" tab.
On Linux:
- Open a terminal.
-
Use one of these commands:
top
(basic system monitor)htop
(if installed, more user-friendly)free -h
(shows memory in GB/MB instead of bytes)
free -h total used free Mem: 16G 8.2G 4.3G
Without -h, output shows bytes:
free total used free Mem: 16777216 8388608 4304892
If available memory is less than 2GB:
- Close resource-intensive processes.
- Close unnecessary apps.
-
Restart VVD:
kepler virtual-device start
VVD fails to start
Cause: You see an error about read or write permissions on /dev/kvm
because virtual technology (KVM) is disabled on your Ubuntu system.
Solution: Make sure your Ubuntu image has enabled KVM virtualization technology. If you're running Ubuntu as a virtual machine, go to Settings > Processors & Memory > Advanced options and enable the hypervisor app support.
App freezes after device service crash
Cause: The VVD service crashes, causing your app to freeze and become unresponsive. The app remains frozen even after restarting services because the app connection to VVD is broken.
Solution:
-
Stop the VVD:
kepler virtual-device stop
-
Restart the simulator:
kepler virtual-device start
-
Restart the app:
kepler device launch-app [your-app-name] // Example kepler device launch-app com.example.mykeplerapp
VVD can't connect to the internet
Cause: VVD can't connect to the internet due to potential network configuration issues.
Solution: Test connectivity by opening a shell on VVD:
kepler virtual-device start
kepler device shell
ping www.amazon.com
Expected output:
3 packets transmitted, 3 received, 0% packet loss
Related topics
Last updated: Sep 30, 2025