Hyper-v 3 guest machines


Recommended Posts

Hello All

I am doing a work project at university and it is about virtualisation and I will need to install Microsoft server hyper-v 2012 onto two computers.

I alread know I can install it onto both machines.

But I need to know can i run hyper-v guests on computers with pentium 4 processors.

Link to comment
Share on other sites

Not from what I remember reading that remixedcat said because the lack the level 3 instructions for something though you can do it on W8's edition or maybe on server 2012 if you can disable the option somehow.

Ask remixedcat

Link to comment
Share on other sites

Screwdriver out, look around for techs and then pop that case off whilst nobody is looking :D

enabling virtualization in the BIOS would be helpful as well but if its not your computer access to the BIOS might be restricted.

Do you have to use Hyper-V? Working with VMWare might make this task easier?

Link to comment
Share on other sites

hi, you will need the proper virtulization support on the CPU.

VT-X are needed. Also your processor must support Second Level Address Translation or Intel VT-x with Extended Page Tables (EPT) if this will be done under Windows 8. It is still preferred but not required for Windows Server 2012, however, as you will have enhanced performance of the VMs.

Link to comment
Share on other sites

Hardware requirements

Prescott 2M (Extreme Edition)

Intel, by the first quarter of 2005, released a new Prescott core with 6x0 numbering, codenamed "Prescott 2M". Prescott 2M is also sometimes known by the name of its Xeon derivative, "Irwindale". It features Intel 64, the XD Bit, EIST (Enhanced Intel SpeedStep Technology), Tm2 (for processors at 3.6 GHz and above), and 2 MB of L2 cache. However, higher cache latency and the double word size, if using Intel 64 mode, negated any advantage that added cache introduced. Rather than being a targeted speed boost the double size cache was intended to provide the same space and hence performance for 64-bit mode operations.

6xx series Prescott 2Ms have incorporated Hyper-Threading in order to speed up some processes that use multithreaded software, such as video editing.

On November 14, 2005, Intel released Prescott 2M processors with VT (Virtualization Technology, codenamed "Vanderpool") enabled. Intel only released two models of this Prescott 2M category: 662 and 672, running at 3.6 GHz and 3.8 GHz, respectively.

http://en.wikipedia.org/wiki/Pentium_4

Link to comment
Share on other sites

  • 2 weeks later...

The earliest machine I could find at work that would take Hyper-V 2012 was a Core 2 Quad Q9550 (2.83Ghz) on Intel X38 Express Chipset. Some older C2D/C2Q CPU's support it but the chipsets don't.

On AMD, Phenom or newer seems fine (I run a Phenom X4 2.2Ghz B3 at home with Server 2012 & Hyper-V 2012) but I hear B2 steppings and earlier are broken by mistake.

Link to comment
Share on other sites

  • 1 month later...

I have been working as an IT admin in a university and know the situation regarding budgets...:)

For old processors you are better off using the free VMware Server 2.0. It works on stone age processors whereas the newer VMware Workstations, ESXi and Hyper-V require newer CPUs. You can check the processor specs worst case there are lists online. But VMware Server is just as good and runs even on dual cores

Link to comment
Share on other sites

I have been working as an IT admin in a university and know the situation regarding budgets... :)

For old processors you are better off using the free VMware Server 2.0. It works on stone age processors whereas the newer VMware Workstations, ESXi and Hyper-V require newer CPUs. You can check the processor specs worst case there are lists online. But VMware Server is just as good and runs even on dual cores

Actually, Hyper-V Server (or Windows Server 2008 and newer) will work on any computer that supports x64 flavors of Windows.

Unlike Windows 8 (which requires EPT/SLAT to use Hyper-V) Windows Server didn't, and still doesn't - even with Server 2012. (That is why I use Server 2012 Standard in my virtualization lab - no SLAT support in the Q6600.)

Why Server 2012 (instead of Hyper-V Server)? The GUI VM management tools - period. If I were comfortable using PowerShell for VM creation and management, I'd stick with Hyper-V Server.

So who told you that load of BS?

Link to comment
Share on other sites

Why Server 2012 (instead of Hyper-V Server)? The GUI VM management tools - period. If I were comfortable using PowerShell for VM creation and management, I'd stick with Hyper-V Server.

I was the same, You just add them to a windows 8 computer using the server manager and you can use the hyperv tools as if you were on the full gui version.

Link to comment
Share on other sites

The earliest machine I could find at work that would take Hyper-V 2012 was a Core 2 Quad Q9550 (2.83Ghz) on Intel X38 Express Chipset. Some older C2D/C2Q CPU's support it but the chipsets don't.

On AMD, Phenom or newer seems fine (I run a Phenom X4 2.2Ghz B3 at home with Server 2012 & Hyper-V 2012) but I hear B2 steppings and earlier are broken by mistake.

Actually any Core 2 Quad will, as *all* support at least VT-x - the same is true of most Core 2 Duos (E6xxx/E8xxx and above) and *all* Celeron DC E3xxx (again, all the preceding support VT-x) as long as the chipset is from Intel's 3-series or newer (the exception, weirdly enough, is G31 - AKA Bear Lake; G41 - AKA Eagle Lake, the successor to Bear Lake, explicitly supports VT-x) - my Windows 8 computer dual-boots Server 2012 (which is the core of my virtualization lab) because of no SLAT support in the Q6600.

I was the same, You just add them to a windows 8 computer using the server manager and you can use the hyperv tools as if you were on the full gui version.

If I were running i5-3570K (which supports SLAT) I'd simply run Hyper-V in Windows 8; however, due to lack of SLAT/EPT with Q6600, I need a server OS, and my choices were Server 2008 or newer or Hyper-V Server. (I don't have a second box.)

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.