Run virt-manager on Windows 10
-
Found may be a easier way of getting it on Windows 10.
Install virt-manager xorg-x11-fonts-* xorg-x11-utils xorg-x11-xauth
Then install MobaXterm
https://mobaxterm.mobatek.net/download.html
I've used the Home Edition
-
@hobbit666 Isn't that the same process, just replacing Xming with MobaXterm? All the rest seems to be the same effort?
-
@scottalanmiller might be, but this way worked for me.
Also no need to install Ubuntu on the windows machine. Just Mobaxterm -
@scottalanmiller said in Run virt-manager on Windows 10:
solutino.
-
@hobbit666 said in Run virt-manager on Windows 10:
@scottalanmiller might be, but this way worked for me.
Also no need to install Ubuntu on the windows machine. Just MobaxtermOh, I must be missing something. How did you install virt-manager without Ubuntu? There is no download or installer for it without that, that I know of. That's what I was looking for.
-
@hobbit666 said in Run virt-manager on Windows 10:
Found may be a easier way of getting it on Windows 10.
Install virt-manager xorg-x11-fonts-* xorg-x11-utils xorg-x11-xauthThese are the steps that don't exist on Windows. The whole thread was about getting these installed, and no one could do it. Installing Ubuntu was to make them installable. If there was a way to install them without it, that would be even better. But the way you have it written is like "you just do it", but virt-manager and all those xorg libraries are Linux executables, not Windows ones. So not sure what to do.
-
They are but you just install Mobaxterm.
SSH onto the KVM server run those commands and then run virt-managerI just found that process easier than installing the Ubuntu solution through Windows store. Updating it, then having the libvirtd error
-
@hobbit666 said in Run virt-manager on Windows 10:
They are but you just install Mobaxterm.
SSH onto the KVM server run those commands and then run virt-managerThat's NOT running virt-manager on Windows. That totally skips the solution and just goes right to what we are trying to fix. We already have it on Linux and already have remote access to Linux. It's getting it on Windows that we are trying to accomplish.
-
@hobbit666 said in Run virt-manager on Windows 10:
I just found that process easier than installing the Ubuntu solution through Windows store. Updating it, then having the libvirtd error
Yeah, but then we have to run an extra server just to handle this one application. Hardly easier. And way slower since you have extra network hops.
-
@scottalanmiller no you install them on kvm host.
All its doing is X11 forwarding like what your doing with Ubuntu and xmingThere's no need for a VM just to run virtmanager
-
@hobbit666 said in Run virt-manager on Windows 10:
@scottalanmiller no you install them on kvm host.
So basically not solving the problem? That's obviously the easiest thing to do, but that's just identifying a problem and then ignoring it.
The whole purpose is to have central access from the desktop to lots of machines in a single interface. Launching tons of X windows to look at lots of different machines would be a mess and specifically what we have already that we are trying to fix. That's the starting point that doesn't work, hence the point of this thread.
-
@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.
-
@hobbit666 said in Run virt-manager on Windows 10:
All its doing is X11 forwarding like what your doing with Ubuntu and xming
That's nothing like what I'm doing.
In my example, I'm running one central virt-manager on Windows that is viewed locally and aggregates lots of KVM, Xen, and LXC servers.
In your example, you are running many virt-managers on Linux, not aggregating, and passing graphics rather than an API, over the network.
Mine solves both networking issues and consolidation issues. Yours is what we already had, actually not as good as what we already had since we have things like NX and MeshCentral already which is better than X for our purposes, and still we were looking for a solution to the problem.
-
@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.
-
@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.
