virt-manager for Windows
-
@DustinB3403 said in virt-manager for Windows:
Virt-Viewer is only Windows solution that allows access to your KVM VM's.
It is not at all Virt-Manager, which is install-able throughout the linux world.
Oh, did he mean to view the console?
yeah, if that's the case, Virt-Viewer. but it also works in Cockpit
-
@Obsolesce said in virt-manager for Windows:
@DustinB3403 said in virt-manager for Windows:
Virt-Viewer is only Windows solution that allows access to your KVM VM's.
It is not at all Virt-Manager, which is install-able throughout the linux world.
Oh, did he mean to view the console?
yeah, if that's the case, Virt-Viewer. but it also works in Cockpit
But cockpit isn't a fat-client. It's a web based console and they aren't the same.
Cockpit can also be a full stack management tool. But for KVM, the only fat-client solution that I can think of is VV and it's literally just for accessing the console of the VM's on any given host.
Nothing more.
-
@DustinB3403 said in virt-manager for Windows:
@Obsolesce said in virt-manager for Windows:
@DustinB3403 said in virt-manager for Windows:
Virt-Viewer is only Windows solution that allows access to your KVM VM's.
It is not at all Virt-Manager, which is install-able throughout the linux world.
Oh, did he mean to view the console?
yeah, if that's the case, Virt-Viewer. but it also works in Cockpit
But cockpit isn't a fat-client. It's a web based console and they aren't the same.
Cockpit can also be a full stack management tool. But for KVM, the only fat-client solution that I can think of is VV and it's literally just for accessing the console of the VM's on any given host.
Nothing more.
It gets the job done very well, without having to install anything on Windows.... total server mangement, VM console, whatever.
Assuming the KVM server has Cockpit installed I mean... but I think it's worth it, it's an easy and secure solution.
But I do agree Virt-Viewer is excellent.
-
@DustinB3403 said in virt-manager for Windows:
Virt-Viewer is only Windows solution that allows access to your KVM VM's.
It is not at all Virt-Manager, which is install-able throughout the linux world.
-
@scottalanmiller yup, that's the same one, just from the choco repo.
-
I searched this b4, forget about it. There is none.
-
@Emad-R said in virt-manager for Windows:
I searched this b4, forget about it. There is none.
Well that sucks. I wonder why, shouldn't be too hard.
-
@scottalanmiller said in virt-manager for Windows:
@Emad-R said in virt-manager for Windows:
I searched this b4, forget about it. There is none.
Well that sucks. I wonder why, shouldn't be too hard.
<snark>
Then compile it yourself.
</snark> -
@scottalanmiller said in virt-manager for Windows:
@Emad-R said in virt-manager for Windows:
I searched this b4, forget about it. There is none.
Well that sucks. I wonder why, shouldn't be too hard.
I think that one hasn't been built, because and specifically due to the "f* Microsoft" stance.
-
You can use Xming and just leverage the regular virt-manager via X11, no needs to use different clients. Be careful, virt-manager is on its way on being deprecated. Use virsh and spice-client or a VNC client to access the VMs virtual consoles.
-
@Francesco-Provino said in virt-manager for Windows:
You can use Xming and just leverage the regular virt-manager via X11, no needs to use different clients. Be careful, virt-manager is on its way on being deprecated. Use virsh and spice-client or a VNC client to access the VMs virtual consoles.
The goal isn't to access just the VM console, but the hypervisor itself with a fat client.
-
@Francesco-Provino said in virt-manager for Windows:
You can use Xming and just leverage the regular virt-manager via X11, no needs to use different clients. Be careful, virt-manager is on its way on being deprecated. Use virsh and spice-client or a VNC client to access the VMs virtual cons
No GUI on the server.
-
I have to ask @scottalanmiller , why the weird requirement of a fat client on windows to manage KVM?
I know someone mentioned it, but is Cockpit not sufficient?
-
Assuming virt-manager is installed on the KVM server.
On Windows
choco install xming putty -y- Load Xming not XLaunch
- Open putty, and go to Connection > SSH > X11 > Enable X11 forwarding and enter
localhost:0.0for X display location.
-
@black3dynamite said in virt-manager for Windows:
Assuming virt-manager is installed on the KVM server.
It would not be, that would not make sense. LOL
That would be different in every way. That's not virt-manager on Windows, that's just remoting into a remote system. If we had a GUI on there, we'd just use MeshCentral.
-
@scottalanmiller said in virt-manager for Windows:
@black3dynamite said in virt-manager for Windows:
Assuming virt-manager is installed on the KVM server.
It would not be, that would not make sense. LOL
That would be different in every way. That's not virt-manager on Windows, that's just remoting into a remote system. If we had a GUI on there, we'd just use MeshCentral.
What's preventing you from using a headless GUI? I was doing that **** in the mid 90s on IRIX, what's changed that it wouldn't work now?
-
@travisdh1 said in virt-manager for Windows:
@scottalanmiller said in virt-manager for Windows:
@black3dynamite said in virt-manager for Windows:
Assuming virt-manager is installed on the KVM server.
It would not be, that would not make sense. LOL
That would be different in every way. That's not virt-manager on Windows, that's just remoting into a remote system. If we had a GUI on there, we'd just use MeshCentral.
What's preventing you from using a headless GUI? I was doing that **** in the mid 90s on IRIX, what's changed that it wouldn't work now?
Other than it's a really poor way to do things? What's wrong with wanting a good solution? We have a good solution on Linux, talking over an API. It is very efficient. Doing remote desktops to many machines is 1) ridiculous 2) insanely inefficient 3) a different result - how would you see all those systems in the same GUI?
-
@scottalanmiller said in virt-manager for Windows:
@travisdh1 said in virt-manager for Windows:
@scottalanmiller said in virt-manager for Windows:
@black3dynamite said in virt-manager for Windows:
Assuming virt-manager is installed on the KVM server.
It would not be, that would not make sense. LOL
That would be different in every way. That's not virt-manager on Windows, that's just remoting into a remote system. If we had a GUI on there, we'd just use MeshCentral.
What's preventing you from using a headless GUI? I was doing that **** in the mid 90s on IRIX, what's changed that it wouldn't work now?
Other than it's a really poor way to do things? What's wrong with wanting a good solution? We have a good solution on Linux, talking over an API. It is very efficient. Doing remote desktops to many machines is 1) ridiculous 2) insanely inefficient 3) a different result - how would you see all those systems in the same GUI?
You need access to 1 instance of virt-manager, which you can then manage any other KVM server on the same network.
I agree that it's not a great solution, but there is no great solution here, only picking which is the least painful way to access the thing. Unless you want to take my snark from earlier seriously and compile virt-manager for Windows yourself.
In short, there is no thing that does what you want. If there was, my home lab would be running KVM instead of XCP-ng.
-
@scottalanmiller said in virt-manager for Windows:
@black3dynamite said in virt-manager for Windows:
Assuming virt-manager is installed on the KVM server.
It would not be, that would not make sense. LOL
That would be different in every way. That's not virt-manager on Windows, that's just remoting into a remote system. If we had a GUI on there, we'd just use MeshCentral.
What? You don't need a GUI to use X11 Forwarding. You installing virt-manager, not a windows manager or desktop environment.
-
@black3dynamite said in virt-manager for Windows:
What? You don't need a GUI to use X11 Forwarding. You installing virt-manager, not a windows manager or desktop environment.
You don't need all of the GUI, but you need the back end of it. It's a remote view that you are transmitting. Like RDP to an RDS server.
