Run virt-manager on Windows 10
-
@JaredBusch said in Run virt-manager on Windows 10:
@scottalanmiller said in Run virt-manager on Windows 10:
@hobbit666 said in Run virt-manager on Windows 10:
There's no need for a VM just to run virtmanager
There isn't a VM. Someone suggested that, but that's why I tried doing it with Ubuntu on Windows without a VM. Just an API layer, it runs right on Windows.
He meant a VM on the KVM host.
Where did that come from?
Does he mean on each KVM host? Something has to run and see everything. If using virt-manager on Linux, I would need a server somewhere to run it from that can't be on the KVM hosts.
This seems so simple, but I can't follow the logic. How would we even start to meet the need without a VM somewhere central to put virt-manager?
-
Ok I admit yeah this is not a central point for many KVM hosts. It allows to manage the KVM host your connected to via the software.
(And still NO VM on the host just installing virt-manager)But still I think I'd prefer this method as I normally admin on Host at a time. Very rarely have multiple VMs from multiple hosts open at a time. But this is just how I work.
-
@DustinB3403 said in Run virt-manager on Windows 10:
Ah, with virt-manager you need to add the location. It is a bit weird, but makes sense the first time you do it.
Where and how do I add this?
-
@hobbit666 said in Run virt-manager on Windows 10:
Ok I admit yeah this is not a central point for many KVM hosts. It allows to manage the KVM host your connected to via the software.
Yeah, that's what we already had. That wasn't a problem. It's the centalization that was the value of getting it installed on the local machines.
-
@hobbit666 said in Run virt-manager on Windows 10:
(And still NO VM on the host just installing virt-manager)
Right, that only works if you don't achieve the goal and skip the entire thing we are trying to do and just remain at the starting point. If you want to attempt to achieve the goal in any way, you either need to install virt-manager on the end points and centralize there, or run a central terminal server of Linux and centralize there. To avoid the VM, you have to skip doing the project altogether.
-
@hobbit666 said in Run virt-manager on Windows 10:
But still I think I'd prefer this method as I normally admin on Host at a time.
It's not how many "at a time", it's how you much effort you have to put in to connecting to them. Sure in an X manager you can have all of your connections listed much like you can with virt-manager, but the connection and viewing process isn't a slick. It would work, but I see no benefits. It's just a lesser experience with fewer options. X over the WAN just isn't as nice as the libvirt API over a WAN.
Also, X just isn't as good for this as NX and other protocols that we were already using. X is ancient and not well suited for the task in your example, I don't feel. If you were doing this totally LAN based, sure. But over a WAN, you want a better compressed protocol.
-
@hobbit666 said in Run virt-manager on Windows 10:
@DustinB3403 said in Run virt-manager on Windows 10:
Ah, with virt-manager you need to add the location. It is a bit weird, but makes sense the first time you do it.
Where and how do I add this?
This is from my Fedora desktop, but works identically on Windows. You can do this for every machine that you want to manage as long as you have access via SSH. Set up keys and it's totally transparent. You can make it connect on demand, or automatically. Whatever works for you.
-
Hmmm... I see that imgur no longer allows GIF hosting. Well that totally sucks. It converts your GIFs that you upload into a PNG thumbnail of said GIF!! What. The. Crap.
-
Anyway, it is just File -> Add Connection
You put in the hostname and username and voila, connected.
-
Do i just ignore that error ? It comes up when I run the
virt-manager &
command on the Ubuntu windows. -
@hobbit666 said in Run virt-manager on Windows 10:
Do i just ignore that error ? It comes up when I run the
virt-manager &
command on the Ubuntu windows.Which error?
-
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 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
Thenapt-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
-
-
@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
Thenapt-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.
-
-
You get that error on all systems, it's a standard virt-manager error. You get in on Fedora, Ubuntu Linux, Ubuntu Windows, etc.
-
@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
-
@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?
-
@scottalanmiller no my lab machine is the only KVM machine all the rest are Esxi
-
@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.
-
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?