Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Compute Cloud
    • You are unable to add a Committed Volume of Services (CVoS) for Compute Cloud
    • You see a "Permission denied" error when connecting to a VM created in Terraform
    • No nested virtualization support
    • UEFI support and data import from GPT-formatted disks
    • Fixing the "Not enough resources" error on launching a virtual machine
    • Recovering access to a VM with a lost SSH key
    • Fixing issues with creating disk snapshots
    • Boot disk size failed to increase
    • VM instance shuts down on the "instance guest stop processing" operation
    • Fixing the "WARNING REMOTE HOST IDENTIFICATION HAS CHANGED" error
    • Fixing a non-replicable disk breakdown
    • Fixing connection issues with Kosmos VM
    • Fixing password reset issues for VMs based on a Kosmos image
    • Options to migrate a VM image to Yandex Cloud
    • Changing the boot disk for an instance to SSD
    • Getting details about RAM consumption for Compute Cloud instances
    • Creating VMs having multiple network interfaces
    • Decreasing VM disk size
    • Exporting disk images of Compute Cloud VM instances
    • Transferring VMs between folders or clouds
    • Setting up GUI and graphic environment on Linux VMs
    • Using an ISO image for deploying VM instances
    • Monitoring incoming or outgoing VM traffic
    • How to use WinSCP to connect to a Linux VM in Yandex Cloud with a key generated at VM creation
    • How to back up a VM with rollback support
    • How to connect via SSH as root with a password or key
    • How to track memory usage
    • How to save snapshots and images locally
    • How to change an internal IP address
    • How to read the "Connections quota utilization" chart
    • What is the disk access speed for a VM
    • How to create a VM with password access
    • What is the maximum number of network interfaces that can be connected to a VM

In this article:

  • Issue description
  • Solution
  • If the issue persists
  1. Compute Cloud
  2. Fixing connection issues with Kosmos VM

Fixing connection issues with Kosmos VM

Written by
Yandex Cloud
Updated at November 27, 2023
  • Issue description
  • Solution
  • If the issue persists

Issue descriptionIssue description

  • You cannot connect to a VM created based on a Kosmos VM image.

SolutionSolution

  1. Check if the Kosmos VM is pingable from other VM instances within the same cloud network.
  2. Try to connect to the SAC console and check the statuses of services.

If the SAC console on the problematic VM is unavailable (when trying to connect to it, you see the message: Unable to launch a Command Prompt. The service responsible for launching is not available), perform the following actions:

  1. Create an image of the disk of the problematic VM.
  2. Attach this image as a secondary disk to another VM based on the Kosmos image.
  3. Run these commands in the command prompt:
        bcdedit /store <mountedvolume>\boot\bcd /ems {default} on
        bcdedit /store <mountedvolume>\boot\bcd /emssettings EMSPORT:1 EMSBAUDRATE:115200
Where `<mountedvolume>` is the letter of the additional disk mounted to another VM based on the Kosmos image.
  1. Detach the secondary disk from the VM.
  2. Create a VM using the modified image as a boot disk.
  3. Connect to the newly created VM.

If the issue persistsIf the issue persists

If the above actions did not help solve the problem, create a request for technical support.
When creating the request, provide the following information:

  1. ID of the VM.
  2. The time range during which you tried to connect to the VM.

Was the article helpful?

Previous
Fixing a non-replicable disk breakdown
Next
Fixing password reset issues for VMs based on a Kosmos image
© 2025 Direct Cursus Technology L.L.C.