[6.10.1] failed to connect to the hypervisor after 6.10 upgrade

Is it the same if you boot in safe mode?

7 hours ago, JorgeB said:

Is it the same if you boot in safe mode?

 

Now I got another message, but I guess it's due to the fact that ZFS plug-in is not loaded.

Since the hypervisor errors are gone - it must be one of the plugins, right?

 

3 minutes ago, gemino said:

it must be one of the plugins, right?

Yep.

Thanks! Deleted bunch of plugins that I never used. Errors stopped!

Changed Status to Solved

Changed Priority to Other

"Failed to connect to Hypervisor" is from the VM Backup plugin, and it's because the VM service isn't started when the plugin is being installed during boot - Nothing to worry about.

On 5/23/2022 at 2:41 PM, Squid said:

"Failed to connect to Hypervisor" is from the VM Backup plugin, and it's because the VM service isn't started when the plugin is being installed during boot - Nothing to worry about.

@Squid do you happen to know if the second error message, "error: Operation not supported: Cannot use direct socket mode if no URI is set", is also coming from the VM Backup plugin?  I also have both these error messages.  Do you know if there's anything I can do to suppress these messages on boot (aside from uninstalling the plugin)?  I'll check plugin support too, see if there's anything there.  Thanks!

 

Yes it would be that plugin related.  And it's not an issue.  It happens during boot up as the plugin isn't considering the fact that when it reinstalls itself the VMs aren't yet enabled

I found this info:

 

uri_default = "qemu:///session

 

and RED HAT indicate /// URI it's mandatory

 

any idea?