Personal computing discussed
Moderators: renee, Flying Fox, Ryu Connor
Chrispy_ wrote:VT-x, not VT-d. Direct I/O is optional.Hyper-V is the name for Microsoft's virtual machine solution. It's an enterprise product requiring VT-d (or AMD Vi) support in hardware and lets you build/run 2 virtual machines on a copy of Server2012, or unlimited virtual machines on Server2012 Datacenter Edition.
lonleyppl wrote:Nitpick: server version, not "full" version. This article lists the differences quite well.Chrispy_, what features is Windows 8 Hyper-V missing out on, compared to the full version?
The only one I can immediately think of is failover clustering, and I'm not sure if that's missing or just something that takes more effort than I've invested to configure. Other than that, it seems the same between my 8 laptop and my Hyper-V Server 2012 server.
Chrispy_ wrote:Hyper-V is the name for Microsoft's virtual machine solution. It's an enterprise product requiring VT-d (or AMD Vi) support in hardware and lets you build/run 2 virtual machines on a copy of Server2012, or unlimited virtual machines on Server2012 Datacenter Edition.
MSMVP wrote:Windows Server 2008 Enterprise Edition expands upon these terms, providing licensing for up to four simultaneous virtual OSEs in addition to the physical OSE. You can run either Standard or Enterprise Edition in the virtual OSEs.
Enterprise Edition is most cost-effective if you want to run four simultaneous instances in a virtual OSE per processor. Enterprise Edition is licensed by server, not per processor, but more than one Enterprise Edition license may be assigned to a server to have the rights to run more than four instances of Windows Server. For example, one license for Enterprise Edition for a one-processor server running four instances of Windows Server in a virtual OSE is slightly less expensive than one Datacenter processor license. And, two licenses for Enterprise Edition for a two-processor server running eight instances of Windows Server in a virtual OSE is slightly less expensive than two processor licenses for Datacenter Edition.
Flying Fox wrote:lonleyppl wrote:Nitpick: server version, not "full" version. This article lists the differences quite well.Chrispy_, what features is Windows 8 Hyper-V missing out on, compared to the full version?
The only one I can immediately think of is failover clustering, and I'm not sure if that's missing or just something that takes more effort than I've invested to configure. Other than that, it seems the same between my 8 laptop and my Hyper-V Server 2012 server.
Chrispy_ wrote:FF answers you question better than I can:
1. Enterprises aren't touching Windows8, not even with a long pole - any company over a certain size has too much to lose by trying to adopt it.
2. I literally discovered Hyper-V was included with 8 as I was editing that first reply
Chrispy_ wrote:vSphere is VMWare's Linux alternative. It's their basic enterprise product and they do more advanced versions like vCenter which allow you to have multiple physical hosts connected to one hypervisor and shared SAN storage meaning you can move virtual machines from one physical host to another on the fly.
Chrispy_ wrote:You guys are all taking this out of context.
Look at the OP's question and stop getting massively geeky and overly pedantic. Stop trying to prove that you know more than the next guy and apply some common sense. If we carry on down this road we might as well just list a 400-strong collection of Microsoft and VMware whitepapers....
Chrispy_ wrote:They are both hypervisors - software solutions designed to emulate and manage virtual servers.
vSphere is VMWare's Linux alternative. It's their basic enterprise product and they do more advanced versions like vCenter which allow you to have multiple physical hosts connected to one hypervisor and shared SAN storage meaning you can move virtual machines from one physical host to another on the fly.
.[/i]
Chrispy_ wrote:You guys are all taking this out of context.
Look at the OP's question and stop getting massively geeky and overly pedantic. Stop trying to prove that you know more than the next guy and apply some common sense. If we carry on down this road we might as well just list a 400-strong collection of Microsoft and VMware whitepapers....
Forge wrote:This from the dude who pedanted mightily about Enterprise Edition no longer existing?
Chrispy_ wrote:Since the OP is gone, what is the difference between VT-d and VT-i, anyway? All I am aware of is that Hyper-V won't install on a Xeon if Vt-D is disabled. I have no idea what benefits they bring because I don't get the choice to not use it.
Forge wrote:Hyper-V probably wouldn't enable on your Xeon machine because disabling VT-d may have also disabled VT/VT-x.
Chrispy_ wrote:x is frequently algebraic. It is in x86 (where x stands for 80, 802, 803, 804, etc), it is (or was) in DirectX (where x stood for 3D, Sound, Show, Play, etc).My mistake, I meant VT-x instead of VT-i, I'd never come across it before.
Didn't realise the x could be algebraic and not part of the acronym - i.e. VT-<any value is good>
Hz so good wrote:IIRC, doesn't the VMWare used in the Nexsus series from Cisco allow you to have multiple Virtual supervisors running to manage a greater number of VM Hosts?
Could be wrong, since I'm just studying it, but I wanna say from memory that the number of VMs and Supervisors are limited only by the hardware in the Nexus 1000/1002.
Chrispy_ wrote:I wouldn't call it pedanting mightily; Ryu challenged my response with incorrect (outdated) info. Am I not allowed to defend my responses in the forums anymore?
Ryu Connor wrote:My post was all 100% factually correct.
Chrispy_ wrote:Maybe we have our wires crossed, in which case this is all irrelevant
Beelzebubba9 wrote:Hz so good wrote:IIRC, doesn't the VMWare used in the Nexsus series from Cisco allow you to have multiple Virtual supervisors running to manage a greater number of VM Hosts?
Could be wrong, since I'm just studying it, but I wanna say from memory that the number of VMs and Supervisors are limited only by the hardware in the Nexus 1000/1002.
Not to be rude, but what are you talking about?
The Nexus series of switches runs NX OS and the Nexus 1000v is a vApp that extends the reach of the network team down into vSphere so the typical systems/network engineer paradigm can persist in a virtual world.
VM density is limited by the underlying host hardware and the footprint of your services and applications as well as your performance and HA requirements.
Ryu Connor wrote:Chrispy_ wrote:Hyper-V is the name for Microsoft's virtual machine solution. It's an enterprise product requiring VT-d (or AMD Vi) support in hardware and lets you build/run 2 virtual machines on a copy of Server2012, or unlimited virtual machines on Server2012 Datacenter Edition.
That's not how the licensing works.