Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

error: failed to connect to the hypervisor

Featured Replies

Hi,

 

I'm using Unraid version 6.8.0 as seen in the screenshot in attached.

Everything is working great, just fine actually !

I have an array and 2 VMs that start automatically.  Working fine !

 

I have noticed today that I get the following 2 errors during boot of Unraid that I never noticed before.  It doesn't seem to affect anything, but was curious if anyone could tell me why and how to fix it !

 

error: failed to connect to the hypervisor

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

 

Please see attached photo as for reference.

 

Any help would be greatly appreciated !

 

IMG_0236.png

Edited by Ginfrecss

Same here.

Not sure if it is since 6.8.0, but when I boot in GUI mode the GUI won‘t show up and it stays in the command line as seen on the picture you have attached.

Does your Unraid Server behave the same when booting in GUI mode?

  • Community Expert
1 hour ago, Melo said:

Same here.

Not sure if it is since 6.8.0, but when I boot in GUI mode the GUI won‘t show up and it stays in the command line as seen on the picture you have attached.

Does your Unraid Server behave the same when booting in GUI mode?

if you login at the prompt and use the df command does it show something mounted as /boot?   

Same here, also after update to Unraid 6.8.1

 

But all my VM's runs well...

 

df tells:

/dev/sda1         30016160     605280   29410880   3% /boot

 

Hi, I'm seeing the same hypervisor error as shown in the first post. I think it started with 6.8.0, but can't confirm that.

My VMs are working.

error: failed to connect to the hypervisor

 

I also get this error on boot with 6.8 & 6.8.1, everything seems to be working OK though.

On 1/17/2020 at 2:24 PM, itimpi said:

if you login at the prompt and use the df command does it show something mounted as /boot?   

Yes, /dev/sdb1 mounted on /boot

Same here

df shows  dev/sda1         7823420     518884    7304536   7% /boot

 

 

 

Getting same thing was happening with 6.8.1 and just updated to 6.8.2. I run 2 VMs they seem to run fine.

  • 3 weeks later...

I have the same problem.
Yet libvirt-sock exists ?

 

My terminal :

root@AAA:~# ls /var/run/libvirt/
hostdevmgr/          libvirt-sock-ro=  nodedev/           secrets/               virtlockd.pid
interface/           libvirtd.pid      nwfilter/          storage/               virtlogd-admin-sock=
libvirt-admin-sock=  lockd/            nwfilter-binding/  virtlockd-admin-sock=  virtlogd-sock=
libvirt-sock=        network/          qemu/              virtlockd-sock=        virtlogd.pid
root@AAA:~# ls -lh /var/run/libvirt/
total 12K
drwxrwxrwx 2 root root   40 Feb 15 16:20 hostdevmgr/
drwx------ 2 root root   60 Feb 15 16:20 interface/
srwx------ 1 root users   0 Feb 15 16:20 libvirt-admin-sock=
srwxrwx--- 1 root users   0 Feb 15 16:20 libvirt-sock=
srwxrwxrwx 1 root users   0 Feb 15 16:20 libvirt-sock-ro=
-rw-r--r-- 1 root root    5 Feb 15 16:20 libvirtd.pid
drwxr-xr-x 2 root root   40 Dec 20 22:53 lockd/
drwxr-xr-x 2 root root  140 Feb 15 16:20 network/
drwx------ 2 root root   60 Feb 15 16:20 nodedev/
drwx------ 2 root root   60 Feb 15 16:20 nwfilter/
drwx------ 2 root root   40 Feb 15 16:20 nwfilter-binding/
drwxr-xr-x 4 root root  120 Feb 15 16:20 qemu/
drwx------ 2 root root   60 Feb 15 16:20 secrets/
drwxrwxrwx 2 root root   80 Feb 15 16:20 storage/
srwx------ 1 root root    0 Feb 15 16:20 virtlockd-admin-sock=
srwx------ 1 root root    0 Feb 15 16:20 virtlockd-sock=
-rw-r--r-- 1 root root    5 Feb 15 16:20 virtlockd.pid
srwx------ 1 root root    0 Feb 15 16:20 virtlogd-admin-sock=
srwx------ 1 root root    0 Feb 15 16:20 virtlogd-sock=
-rw-r--r-- 1 root root    5 Feb 15 16:20 virtlogd.pid

 

Did you start libvirtwol... in the bar at the bottom of the array?

  • Author
1 hour ago, Sosk91 said:

Did you start libvirtwol... in the bar at the bottom of the array?

Bar at the bottom of the array ?  Can you specify where exactly ?

Bottom bar (array started)

chrome_eNBoRpnVaw.png.d6cb545e421c8ba5460cefa3cd9d9b0f.png

  • Author

Non sure how to start libvirtwol ? The array and parity are started with no errors reported.

The array and parity it's my action.

Libvirtwol is a plugin, and they don't start, but I'm waiting for the end of the parity to restart Unraid and see if it's still

I'm a newbie to UNRAID, so far it's been pretty stable but I made some changes this morning.
Since then I get this error message at startup and especially this plugin that doesn't start anymore.

Edited by Sosk91

4 minutes ago, Sosk91 said:

Since then I get this error message at startup and especially this plugin that doesn't start anymore.

It's the Virtual BMC portion of the plugin that doesn't start up, and you're best posting in the support thread for the plugin regarding all this.  (There's a support link within the Plugins Tab for it)

  • Author

What is BMC ?  I have a vanilla Unraid install i.e no plugins installed from me..and I'm getting this error.

Yeah, I'm waiting for a restart.
We're here for the first post problem. (my bad)

2 minutes ago, Ginfrecss said:

What is BMC ?  I have a vanilla Unraid install i.e no plugins installed from me..and I'm getting this error.

I was replying to the quoted post.  But if you're truly a vanilla install, then post your diagnostics

  • 4 weeks later...

Has anyone worked out what is causing this? Now on 6.8.3 and have the same error and to my knowledge no libvirtwol plug-in installed. df shows /dev/sdf1 mounted at boot, which is my flash drive!

tower-diagnostics-20200310-1221.zip

  • 2 weeks later...

I traced this issue to the installation of the VM Backup Plugin.  I will be cross posting in that thread about this issue.

 

-JesterEE

  • 1 month later...

I'm having this exact same issue. My VM tab is not even present in the WebUI.

 

This happened after I had a strange issue with unRAID where I could not access the WebUI nor ssh, so had to force restart unRAId. After the restart now i see this same error and in the WebUI i can't see my VM tab.

  • 2 weeks later...
On 3/20/2020 at 2:23 AM, JesterEE said:

I traced this issue to the installation of the VM Backup Plugin.  I will be cross posting in that thread about this issue.

 

-JesterEE

Hi

 

New install a couple of days ago and installed lots of plugins and 3 VMs. After a force restart I have the same errors on boot and cannot access webUI.

 

You say you traced it to this plugin which I do have but what makes you think its that? I saw your post on the plugin thread but I see nothing to indicate why you are sure this is the cause? 

 

And is there a repair other than reinstall ALL MY UNRAID AGAIN!? Please no...

2 hours ago, methanoid said:

Hi

 

New install a couple of days ago and installed lots of plugins and 3 VMs. After a force restart I have the same errors on boot and cannot access webUI.

 

You say you traced it to this plugin which I do have but what makes you think its that? I saw your post on the plugin thread but I see nothing to indicate why you are sure this is the cause? 

 

And is there a repair other than reinstall ALL MY UNRAID AGAIN!? Please no...

 

I disabled all my plugins and restarted.  Then I enabled one plugin at a time and restarted till it popped up.  As soon as I turned on the VM Backup plugin it started happening.  I disabled all the other plugins and restarted (keeping the VM Backup plugin enabled) and restarted.  Still there.

 

Check with the VM Backup plugin support thread to see if there is any info on an update there.  If not, no, there is no "repair" and a reinstall won't help.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.