Hyper-V virtualization in action

Hyper-V virtualization in action

Summary: How well does the latest beta of Microsoft's virtualization solution work? In this gallery, Ed Bott looks at Hyper-V in action on Windows Server 2008.

SHARE:
TOPICS: Virtualization
4

 |  Image 11 of 11

  • Thumbnail 1
  • Thumbnail 2
  • Thumbnail 3
  • Thumbnail 4
  • Thumbnail 5
  • Thumbnail 6
  • Thumbnail 7
  • Thumbnail 8
  • Thumbnail 9
  • Thumbnail 10
  • Thumbnail 11
  • The list of available settings for the Hyper-V server itself are relatively limited. You can specify the location of VM settings and virtual disk files and also control the credentials used to connect to virtual machines.

    For the full review, see Is Hyper-V ready for the Windows desktop?.
  • The physical machine hosting this collection of virtual machines is using a quad-core CPU with 6 GB of RAM. With three VMs started but not running any tasks, CPU usage is practically nonexistent. Memory usage corresponds almost perfectly to the amount of virtual memory assigned.

    For the full review, see Is Hyper-V ready for the Windows desktop?.

Topic: Virtualization

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Related Stories

Talkback

4 comments
Log in or register to join the discussion
  • Virtualization Systems

    Any reason there hasn't been virtual machines before on PC's?

    I first worked with virtual systems on CP67 and / or CMS (Cambridge Monitoring System), in the late 60's on machines that were a thousand times the size and power requirements and 1/1000 the processing power of modern PC's . . . in case anyone out there thinks this is new technoloogy or anything!
    rdmcconnell
    • There have been several

      I've been using VMWare for more than five years, and Virtual PC has been around for that long as well.
      Ed Bott
  • 2013?

    Ed:

    I really don't think it would take Microsoft that long to do this. I mean, they already have toolkits for producing stripped down XP and Server 2003 appliances. A lot of those appliances never became very popular, but the toolkits exist. All you would need to do is deploy that stripped down appliance into a built-in VM with Hyper-V, fixed for ACPI, with a dumbed down interface, and its done.

    Maybe I am oversimplifying things, but if there is a will, there is a way.
    jperlow
    • One word: Testing

      Integrating, stabilizing, and testing the virtualization module would take a year, minimum. And adding support for USB and power management would add another year or two.
      Ed Bott