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.

VVD won't stop on Ubuntu

Cause: Stop and status commands aren't supported for VVD on Ubuntu systems.

Solution: Right-click the VVD app icon and select close or click the "x" button in the VVD controls.

VVD crashes after launch

Cause: Certain USB hubs or docking stations interfere with VVD startup.

Solution:

1. Disconnect all USB hubs from your host machine.
2. Disconnect any docking stations from your host machine.
3. Restart the 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 virtual device.

Solution:

1. Click "Register this device" on the top right.
2. Record the registration code shown on screen.
3. 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:

1. Open Activity Monitor (Applications > Utilities > Activity Monitor).
2. Click 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)

   Copy code Copied to clipboard.

   free -h
             total        used        free
   Mem:       16G         8.2G        4.3G
   

   Without -h, output shows bytes:

   Copy code Copied to clipboard.

   free
             total        used        free
   Mem:    16777216    8388608     4304892
   

If available memory is less than 2GB:

1. Close resource-intensive processes.
2. Close unnecessary apps.

3. Restart VVD:

   Copy code Copied to clipboard.

   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:

1. Stop the VVD:

   Copy code Copied to clipboard.

   kepler virtual-device stop
   

2. Restart the simulator:

   Copy code Copied to clipboard.

   kepler virtual-device start
   

3. Restart the app:

   Copy code Copied to clipboard.

   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

• Run Your App on Vega Virtual Device

Last updated: Sep 30, 2025