Hyper-V as a service
-
@scottalanmiller said:
Same reasons as with Hyper-V minus the benefits that Hyper-V has of having lots of people that do this and a few tools that are used for the purpose. There isn't any "local Xen console" interface like Hyper-V has. So all of the negatives of Hyper-V with a GUI, none of the benefits. Plus, there are great API based tools like XC and XO, so no need for it.
I thought you were making a general statement on GUIs on Linux servers.
XC/XO has been fine for me.
-
@BRRABill said:
@scottalanmiller said:
Same reasons as with Hyper-V minus the benefits that Hyper-V has of having lots of people that do this and a few tools that are used for the purpose. There isn't any "local Xen console" interface like Hyper-V has. So all of the negatives of Hyper-V with a GUI, none of the benefits. Plus, there are great API based tools like XC and XO, so no need for it.
I thought you were making a general statement on GUIs on Linux servers.
XC/XO has been fine for me.
No different than GUIs anywhere on servers.
-
This thread made me finally realize why @mdecamp was having issues with me wanting to use "Hyper-V" to shutdown a Hyper-V machine and its hosts.
I was always accessing Hyper-V via the GUI. Via the GUI using the Eaton software to send shutdown to Hyper-V is possible. (Though is it legal license-wise, I wonder?) But a lot of people probably only know it in its non-GUI version, like other hypervisors.
So I would imagine there would be no way to install the shutdown software into it. (Or XS, or any other hypervisor for that matter.)
-
@BRRABill said:
This thread made me finally realize why @mdecamp was having issues with me wanting to use "Hyper-V" to shutdown a Hyper-V machine and its hosts.
I was always accessing Hyper-V via the GUI. Via the GUI using the Eaton software to send shutdown to Hyper-V is possible. (Though is it legal license-wise, I wonder?) But a lot of people probably only know it in its non-GUI version, like other hypervisors.
So I would imagine there would be no way to install the shutdown software into it. (Or XS, or any other hypervisor for that matter.)
WHAT?
-
@BRRABill That makes no sense. Even if you couldn't install software on them (you can), every OS has well-known remote shutdown/restart procedures.
-
@travisdh1 said:
@BRRABill That makes no sense. Even if you couldn't install software on them (you can), every OS has well-known remote shutdown/restart procedures.
Perhaps I was unclear. That was pre-coffee.
The was trying to decide between the 5S and the 5P. The 5S only communicates with the machine via USB. The 5P can communicate via network interface as well.
If you are able to plug the UPS into a machine via UPS, and install the Windows-based "UPS Companion Software", you can shut down that machine. If it was a server running Hyper-V (with the GUI) that would work.
However, this scenario would have no way of contacting the VMs. The 5S only works via UPS cable and the companion software.
So to shutdown the VMs, you would need the 5P which sends the shutdown signal over the network to the software sitting on each VM.
Does that make more sense. Someone I will not mention called my first post "babbling" or "rambly" or something, so hopefully this makes more sense!
-
@travisdh1 said:
every OS has well-known remote shutdown/restart procedures.
Though you could be right even the 5S via USB cable might work even WITHOUT the companion software.
Hmmm, time for a new thread!
-
@BRRABill You seriously need to slow down and think a little.
Half the time you typed UPS, I think you meant USB.
I have no idea if the Eaton client software can be installed on Hyper-V Server, but I can test that. It will come down to what Windows features it requires. The software installs and runs as a service that you access via a browser (even on the local machine), so I would see no reason why it would not install.
Regarding the 5P, it does NOT have a network card by default. The network card is an optional add on that costs $250.
-
@BRRABill said:
So to shutdown the VMs, you would need the 5P which sends the shutdown signal over the network to the software sitting on each VM.
This is not how that works.
You tell Hyper-V Server to shut down. That is all. The Hyper-V server will correctly handle the guest VM's based on the settings you specified for each VM.
-
@JaredBusch said:
Regarding the 5P, it does NOT have a network card by default. The network card is an optional add on that costs $250.
Correct.
-
@JaredBusch said:
This is not how that works.
You tell Hyper-V Server to shut down. That is all. The Hyper-V server will correctly handle the guest VM's based on the settings you specified for each VM.
Do you know how to do that with Hyper-V and an Eaton UPS? Not the GUI.
-
@JaredBusch said:
@BRRABill You seriously need to slow down and think a little.
No time for slowing down, Dr. Jones.
-
@BRRABill said:
@JaredBusch said:
This is not how that works.
You tell Hyper-V Server to shut down. That is all. The Hyper-V server will correctly handle the guest VM's based on the settings you specified for each VM.
Do you know how to do that with Hyper-V and an Eaton UPS? Not the GUI.
This has nothing to do with the Eaton. These are normal Hyper-V settings.
-
-
-
@BRRABill said:
Is that available non GUI?
Assuming it is, and that you would know how.
just f******[moderated] stop and think man.
I am going to stop helping if you can't.Those are Hyper-V settings. Period. Manage them however the hell you want. Normal people do it with the GUI because they don't do it often enough to learn the powershell. but the almost the entirety of anything on windows server can be done in powershell anymore.
-
Eaton setup on Hyper-V Server 2012 R2. There is not an Eaton UPS in the same room as this server and the software says it wants it connected first. so sno idea if the install will succeed or fail for that reason. but I will try it.
-
Yup, worked.
Failed to launch the browser because there is not one.
So open port 4679 on the firewall and access the browser remotely.
-
The whole situation that you can get a GUI based install to work in something that it's suppose to have a GUI just weirds me out!
How is this suppose to be so much lighter when the stuff that makes GUI windows work is still clearly there?
I agree that it's nothing more than myself boxing myself into incorrect assumption (something that most of us do) - Hey this is GUI-less, therefore anything that requires GUI interaction (at least for install) won't work.
-
@JaredBusch said:
@BRRABill said:
So to shutdown the VMs, you would need the 5P which sends the shutdown signal over the network to the software sitting on each VM.
This is not how that works.
You tell Hyper-V Server to shut down. That is all. The Hyper-V server will correctly handle the guest VM's based on the settings you specified for each VM.
OK, someone who's brand new to hypervisors might not know that.. good post.
