Amazon Developer

Console

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases

Console

as

Get Started
Design and Develop
Publish
Reference
Support
Skip to main content
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 the Developer Forum for additional support.

​
Webview-based Vega app fails on Ubuntu

Cause: VVD doesn’t support Webview on Ubuntu or Intel-based Mac platforms. Solution: Use Apple Silicon Mac (M1, M2, M3, M4) or Fire TV 4K Select for Webview app testing. Alternative: Consider using Vega SDK for full Virtual Device support across all platforms.

​
VVD crashes after launch

Cause: The following can interfere with VVD startup: • Certain USB hubs or docking stations • Audio interfaces (like Focusrite 2i2) when you use them for both input and output simultaneously Solution: For USB or docking station interference:
  1. Disconnect all USB hubs from your host machine.
  2. Disconnect any docking stations from your host machine.
  3. Restart the VVD.
For audio interface crashes (occur 10-20 seconds after launch):
  1. Use your audio interface for either input or output, but not both simultaneously.
  2. Alternatively, temporarily use different devices for input and output while you run VVD.

​
Unable to register VVD for Amazon service

Cause: VVD requires registration before you can use any Amazon services for testing. Without completing the registration process, your app can’t access Amazon services on a virtual device. Solution:
  1. Select “Register this device” on the top right.
  2. Record the registration code shown on the screen.
  3. Complete device code registration Go to www.amazon.com/code and enter the code.
Look for this message to confirm registration:

​
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:
  1. Open Activity Monitor (Applications > Utilities > Activity Monitor).
  2. Select the “Memory” tab.
On Linux:
  1. Open a terminal.
  2. 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)
    Without -h, the output shows bytes:
If the available memory is less than 2GB:
  1. Close resource-intensive processes.
  2. Close unnecessary apps.
  3. Restart VVD:

​
VVD fails to start

Cause: You see an error about read or write permissions on /dev/kvm because your Ubuntu system has virtual technology (KVM) disabled. Solution: Make sure your Ubuntu image has enabled KVM virtualization technology. If you’re running Ubuntu as a virtual machine, enable hypervisor support. Go to Settings > Processors & Memory > Advanced options to find this setting.

​
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 VVD breaks the connection. Solution:
  1. Stop the VVD:
  2. Restart the VVD:
  3. Restart the app:

​
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:
Expected output: 3 packets transmitted, 3 received, 0% packet loss

​
Module dependency not found for kepler-ui-components

Cause: Your app uses @amazon-devices/kepler-ui-components, but you’re testing on an older VVD version that doesn’t include the required native modules. Each SDK version includes a VVD image with specific native OS components. VVD versions from SDK 0.21 and earlier don’t include native modules added in recent updates. Symptoms: You see this error when installing your app:
Solution: Upgrade to the latest SDK (0.22 or later):
The latest SDK includes an updated VVD with all required native modules. If you can’t upgrade, use one of these alternatives:
  • Test on a physical Fire TV Stick 4K Select. Physical devices receive regular updates and include all required modules.
  • Remove the @amazon-devices/kepler-ui-components dependency from your app, or limit VVD testing to functionality that doesn’t use UI Components.
Last modified on April 1, 2026