1

Hi Folks,

Looking for some guidance on getting started with virtualization and the direction I need to start researching.

I currently have a new physical server with Windows running SQL Server 2012 Express.

I also have an older system running Linux with MySQL, Firebird and other legacy stuff. Basically, this older system is in dire need of an upgrade.

Rather than upgrade and continue to maintain 2 physical servers, I would like to consolidate by running the older server as a VM within the newer physical server. And so here are my questions:

  1. Can I run/sideload a Type-1 hypervisor without affecting my existing Windows installation? I’m guessing not and that the Type-1 HV would need to be the base/host running 2 VMs for Windows and Linux.

1.1 Or am I limited to Type-2 hypervisors? I’d really rather not have to transition the windows installation.

  1. Which hypervisor would you recommend for my pretty basic needs? I would be considering the included MS Hyper-V, one of the free offerings from VMWare and the free VirtualBox. Anything else I should be looking at? (Free being a prerequisite.)

Thank you very much for your help!

@VMware

4 Spice ups
2
  1. You cannot run the type one alongside the existing windows install no.

in short what you can do is use the newer physical server as the type 1 hypervisor (if it is possible for you to backup the SQL and restore it after?).

So, you would backup the server 2012 machine, make sure this backup is restorable. Then, install the hypervisor of choice on this box. Create a new VM, install Server 2012, restore all of your data and SQL Express DB.

Then, you have 2 options with the Linux box, to a P2V (physical to virtual) conversion or else create a new VM and migrate the Linux services and data to this.

  1. I prefer VMware but HyperV or Xen will also be fine.
2 Spice ups
3

+1 for ESXi free.

Seems like you’re trying to do this on the cheap. Nothing wrong with that, but my father used to have a sign hanging on a wall in his business that read:

Good

Cheap

Fast

Please choose 2 of the 3.

If the new server is on the VMware HCL for ESXi 5.x, the you have the ‘slow, cheap, good’ route available to you. In overview, it looks like this:

Install ESXi Free on an unused workstation* and do some test P2V conversions of the old Linux and Windows servers. Once you have a working, tested replacement VMs, back up the old servers again. Then take a long downtime to wipe the new server, install ESXi on it, and copy the VMs from the workstation testbed back into the hypervisor of the server machine. Test again and make sure you have a workable emergency fallback plan (such as running temporarily on the workstation you tested on.)

This process works equally well for any of the hypervisors, and has the advantage of providing an emergency fallback.

There is some considerable risk to this method. This is the cost of trying to do things on the cheap. If you can’t get enough of a downtime window of at least 48 hours, or the business cannot otherwise deem this an acceptable risk, then politely explain that to the key people involved.

  • ESXi isn’t designed to run on desktop-class hardware, and you might have glitches with installation or P2V, but if the VM works on the desktop, it will work on the server.
1 Spice up
4

Barry is right.

There was a product by VMWare called Vmware server which was hypervisor on top on windows, needless to say it had problems so development of it has ended.

5

If you ran into issues with installing ESXi on a workstation, you could venture into the realm of ‘technically possible but really complicated.’ You could evaluate VMware workstation, run ESXi inside of that and P2V your servers to the virtualized virtual host. This is supported by VMware.

Warning: In addition to doing cruel and unusual things to virtual baby penguins, it might just break your brain running a VM inside a VM on top of Windows.

1 Spice up
6

I would go with what the first two said. If you install ESXi on barebones hardware underneath Windows, you’ll typically see better performance as there is less overhead. Here’s what I would do:

  1. Create a P2V copy of your Windows server using VMware vCenter Converter Standalone (free). This creates a virtual copy of your physical server while it’s still running. You’ll want to make sure the server is not being written to so no changes are being made. I would also take a regular full backup and maybe an image of the server before you proceed, and verify that they are good.

  2. Install VMware Player or Workstation on a PC, and make sure your P2V copy of the server works. You should be able to boot it up and it should look the same as before.

  3. Wipe the newer server clean, and install VMware ESXi. Assign it an IP address, make sure everything is working, and download the client.

  4. User vCenter Converter Standalone again to convert your P2V to an Infrastructure type VM and upload it to your ESXi host. Once it’s done, you should be able to boot it up again without issue.

  5. With VMware running and your Windows server now running as a VM, it’s time to work on the Linux box. Use the same procedure. Back it up, create a P2V, then upload the P2V VM to the server using Converter.

1 Spice up
7

@CFonseca:

Sorry to rain on your parade (I mean that seriously and not sarcasically. I really hate it when someone comes up with a cool thought and I have to disagree with it.) What you propose is a techically cool trick that is fun and a cool idea for a lab environment, but is not suitable for what I think the OP is attempting.

Double conversion adds additional complexity and chances for failure. Remember he’d have to be doing this ‘live’ and once he’d wiped his windows server to install ESXi, it’s the wrong time to be running into conversion issues from workstation to ESXi. Murphy will show up and stomp all over him. Better to have it as an known, working infrastructure-type VM when it’s ‘go time’ and the clock is ticking. This is why I suggested ESXi inside workstation if he went the ‘complicated’ route.

Also VMware Player’s licensing would likely prevent its inclusion as an option.

1 Spice up
8

Can you not just add the Hyper V role to the Windows Installation? If you go to add roles and features you should be able to add Hyper V (Depending on which version of Windows you are running would tell if this is a good idea or not) If you have Server 2008 or newer just add the Hyper V role and add the Linux virtual. I have Server 2008 R2 at home running a virtual with another instance of Server 2008 R2

1 Spice up
9

Thanks for all the responses so far! Very helpful insights.

Can I pick CHEAP and RELIABLE? Time is something I have.

I’m starting to lean towards MS Hyper-V as it appears it would let me do what I want without having to manually backup/convert the existing windows installation.

Looks like running with the Type-2 hypervisors is not ideal.

I’m going to re-read all your answers and look into all the different options.

Thanks again, much appreciated! :slight_smile:

10

VMware and Hyper-V both work and will do what you need.

Having said that, given what you have purchased, consider the cost of licensing. If you run your host on Standard Edition, you can run two more instances of Standard license free. If you use the pure Hyper-V hypervisor, each OS has to be licensed. this is, of course, over and beyond CAL licensing.

Finally, were it me, I’d like to start with as clean an enviornment as possible - which means as much fresh installation (vs upgrade) as possible.

11

I second running the hyperV role along side. If you continue to run your Linux box you will not violate any licensing for the Windows system while it is running the SQL instance. However, I would only do this depending on your load for the two systems and the capabilities (i.e. RAM / Proc/ IO) of the Newer server. Also It would only be suggested to do this if you have multiple nic cards (3 would be best but 2 would suffice). A clean install and two VMs would be better but it increases your complexity and down time needed.

12

Yeah, free works! :slight_smile: VMware!

Just like Barry said, you can’t run Type1 HV alongside Windows but I think you can get the ESXi on your newer hardware and install ESXi on it and then do whatever you want on it. You can then upgrade your older systems & do whatever you want with it.

13

Be careful going down the ESXi route. Sure it’s ‘free’, but you then do have to license the VMs separfately. Using HyperV inside WIndows Server can avoid some of that expense. Do you sums carefully

14

You can run Type 1 Hyper V along-side Windows. It is a Role that can be added in Server Manager, I am doing it at home on my Server 2008 R2.