Run virt-manager on Windows 10

scottalanmiller

I've not seen an error when running on Ubuntu, but I only have one I think. I'm mostly on Fedora. And the one Windows box I've been testing on. It's not me that would need it on Windows.

hobbit666

@hobbit666 said in Run virt-manager on Windows 10:

Having a few issues getting this running.

So i've installed Xming.
Set the Display and Ran the program.

Gone to the Windows Store and installed Ubuntu 18.04

Ran Ubuntu and done and ap-get update
Then apt-get install virt-manager

ran virt-manager &

This is where i get the first problem.
I get the following message:-

Do i need to install or run anything else on the Windows Ubuntu instance?

@scottalanmiller this one

scottalanmiller

@hobbit666 said in Run virt-manager on Windows 10:

@hobbit666 said in Run virt-manager on Windows 10:

Having a few issues getting this running.

So i've installed Xming.
Set the Display and Ran the program.

Gone to the Windows Store and installed Ubuntu 18.04

Ran Ubuntu and done and ap-get update
Then apt-get install virt-manager

ran virt-manager &

This is where i get the first problem.
I get the following message:-

Do i need to install or run anything else on the Windows Ubuntu instance?

@scottalanmiller this one

Oh, that's because by default it is trying to connect to a local instance. If you don't have one, it's just confirming that. It's not an "error", just letting you know that it needs details for a remote instance before you can use it.

scottalanmiller

You get that error on all systems, it's a standard virt-manager error. You get in on Fedora, Ubuntu Linux, Ubuntu Windows, etc.

hobbit666

@scottalanmiller said in Run virt-manager on Windows 10:

Oh, that's because by default it is trying to connect to a local instance. If you don't have one, it's just confirming that. It's not an "error", just letting you know that it needs details for a remote instance before you can use it.

Ah ok will have to wait until Tuesday and try again. Not in Monday and I shut the machine off for the weekend

scottalanmiller

@hobbit666 said in Run virt-manager on Windows 10:

@scottalanmiller said in Run virt-manager on Windows 10:

Oh, that's because by default it is trying to connect to a local instance. If you don't have one, it's just confirming that. It's not an "error", just letting you know that it needs details for a remote instance before you can use it.

Ah ok will have to wait until Tuesday and try again. Not in Monday and I shut the machine off for the weekend

Do you have a remote system with libvirt running that has SSH accessibility? Something to test against?

hobbit666

@scottalanmiller no my lab machine is the only KVM machine all the rest are Esxi

scottalanmiller

@hobbit666 said in Run virt-manager on Windows 10:

@scottalanmiller no my lab machine is the only KVM machine all the rest are Esxi

You can still use that from any Windows instance, even a VM on top of it, to see what a remote system would be like.

hobbit666

before i'm back in tomorrow is there anything I need to do on the KVM (Fedora29) host I need to install/run/firewall to allow it to be managed externally by the windows machine?

travisdh1

@hobbit666 said in Run virt-manager on Windows 10:

before i'm back in tomorrow is there anything I need to do on the KVM (Fedora29) host I need to install/run/firewall to allow it to be managed externally by the windows machine?

You shouldn't. virt-manager operates on remote hosts via ssh.

scottalanmiller

@hobbit666 said in Run virt-manager on Windows 10:

before i'm back in tomorrow is there anything I need to do on the KVM (Fedora29) host I need to install/run/firewall to allow it to be managed externally by the windows machin

Port 22 and 5900. 22 for management, 5900 if you also want remote SPICE terminals.

brandon220

Trying to run virt-manager and Getting the following error:

root@DESKTOP-A911GSS:~# Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
(virt-manager:28): Gtk-WARNING **: 18:58:22.746: cannot open display:

I've followed the steps and no luck.

scottalanmiller

@brandon220 said in Run virt-manager on Windows 10:

Trying to run virt-manager and Getting the following error:

root@DESKTOP-A911GSS:~# Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
(virt-manager:28): Gtk-WARNING **: 18:58:22.746: cannot open display:

I've followed the steps and no luck.

You have Xming running?

hobbit666

OK so got a connection but got a few other problem.
First one was i got this.

Unable to connect to libvirt.

You need to install openssh-askpass or similar to connect to this host.

Solved by running this sudo virt-manager --no-fork

Or a permanent solution was to run sudo apt-get install ssh-askpass ssh-askpass-gnome

hobbit666

My next issue/question

Once in Virt-Manager i can add my KVM host and connect. It asks for my users password twice? Should it?

Then once on (i've already got some VM's on there) when i click on a VM and open the console it asks for the password 5-6 times before displaying the console/desktop.

black3dynamite

@hobbit666 use SSH key authentication to avoid having to enter a username and password.

hobbit666

@black3dynamite Yeah did think that, but thought mention it here in-case someone else gets the issue

brandon220

@scottalanmiller

You have Xming running?

Yes, it should be. Shows the icon in the taskbar after I "opened it".

hobbit666

@hobbit666 said in Run virt-manager on Windows 10:

OK so got a connection but got a few other problem.
First one was i got this.

Unable to connect to libvirt.

You need to install openssh-askpass or similar to connect to this host.

Solved by running this sudo virt-manager --no-fork

Or a permanent solution was to run sudo apt-get install ssh-askpass ssh-askpass-gnome

OK so after playing and re-insyalling from scratch on both the KVM host and Ubuntu on my machine. This is because i'm running everything as root ... oops.

So added a "user" to the KVM while i was installing and now when i use Virt-Manager we are all good.
Also as @black3dynamite suggested i've generated a SSH key and now i can just connect and go.

However i did get a error when creating the connection on Virt-Manager using the "users" account
authentication unavailable: no polkit agent available to authenticate action 'org.libvirt.unix.manage'

This was solved by adding the user on the KVM host to the libvirt group.

hobbit666

Also i was finding that when i closed Virt-Manager on the Windows machine, then came back later the connection was lost and i had to re-add the connection and delete the default one that keeps coming back.

This was solved by running sudo apt-get install dbus-x11 on ubuntu

Now when i reboot my Windows machine and re-open virt-manager the default is gone and my KVM connects automatically