Problem with Sonoma MacOS and KVD

Vega Open Beta Q&A
1

Hello!
MacOS 14.2.1 Intel
Vega SDK 0.21.4839 & KVD installed.
Sample project build is OK.
But Kepler Virtual Device show only black screen and shutting down after ~2-3 min.

% kepler virtual-device start
Launching default instance.
Waiting for virtual device to boot.
Launch process complete.
/// ~2 min of black screen ///
Launch failed with error code 0.
Cleaning up. Killing virtual device process with pid 27442.
Kepler operation FAILED due to an irrecoverable error: The virtual device failed to start within the expected time.
Additional logs can be found at /Users/arty/.kepler/logs
(no error logs BTW)

Ubuntu 20.04 - no problem with KVD.
What’s the problem with Sonoma MacOS and KVD?

Upd. Ubuntu 22.04 - same problem, even no gui (remote and black box)

Upd 2. Ubuntu 22.04 + libvirt with Ubuntu 20.04: see normal KVD screen inside 20.04 but now main problem - how to tunnel KVD from 20.04VM into host 22.04 like locally started KVD..

3

Hi @DJArty

Welcome to Amazon Developer Community !

We are looking into your issue with the internal teams, rest assured I’ll be back soon with an update.

Warm regards,
Ivy

1 Like
4

Hi @DJArty

Thank you for your patience while we investigated this issue. Based on our analysis, Intel-based Macs experience particularly slow KVD startup times that may exceed the default timeout. We’d like to suggest the following troubleshooting steps:

First Step - Update and Extend the Timeout:

  1. Update your Vega SDK to the latest version (v0.21.5245) if you haven’t already (reference)

  2. Extend the timeout to 5 minutes (300 seconds) when starting the KVD using this command:

kepler virtual-device start --timeout 300

You can find more details about the timeout flag in our documentation: https://developer.amazon.com/docs/vega/0.21/run-apps.html#step-1-start-the-vega-virtual-device

If the Issue Persists:

To help us diagnose the problem further, could you please share the following log files:

  1. ~/kepler/sdk/v0.21.x/kvd/instances/<instanceID>/virtual_device.out

  2. ~/kepler/sdk/v0.21.x/kvd/instances/<instanceID>/virtual_device.err

  3. ~/kepler/logs/kepler-<dateOfLogs>.log

These logs will provide valuable insights into what might be causing the startup failure.

Please let us know how the SDK update and extended timeout work, and feel free to share those logs if you continue experiencing problems.

1 Like
5

Hey @DJArty

Closing this topic due to inactivity. If you are stiull facing this issue and need our help, feel free to create another topic and we’ll be happy to help.

Warm regards,
Ivy