Unable to boot KVM VPS in SolusVM | An easy fix

Unable to boot KVM VPS in SolusVM is causing trouble?

Our Server Management Service ensures every query gets resolved by our hands-on skilled Support Techs.

Let’s take a look at how our elite Support Team resolved the unable to boot error for a customer recently.

What is “Unable to boot KVM VPS” error in SolusVM?

Are you failing to boot KVM VPS in SolusVM even after pushing the Reboot button? If you are coming across the following error, you have come to the right place.

error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused

In some scenarios, you may also be presented with this error:

error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

In fact, here is a peek at the libvirtd service status on the KVM Slave Node:

#systemctl status libvirtd
● libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sat 2021-10-23 10:19:11 EDT; 31min ago
...

If this service is not running on the KVM Slave Node, it results in the Unable to boot error.

How to resolve the “Unable to boot KVM VPS” error in SolusVM?

1. First, we will log in via SSH to the Slave Node.
2. Then, we will start the libvirtd service with the following command:

   systemctl start libvirtd

Once the libvirtd service starts running, we will not run into the failed to connect socket to ‘/var/run/libvirt/libvirt-sock’ in SolusVM.

[Need further assistance? We are here to lend a hand.]

Conclusion

To sum up, the Support Team at Bobcares demonstrated the reason behind the failure to boot error in SolusVM. We also learned how to resolve this issue without any additional trouble.