Server 2008 and VMware

[Parvardigar]

I don't know if this is the area to post. I am in a mental pickle. We are replacing our HP ML350 with a new machine. We use Server 2003 in a domain. We are planning on buying new and upgrading. The IT specialist sent me this comment.

What the specialist wants to do is to “I want to create a virtual machine (Windows Server 2008 R2) which would run Oracle and Microsoft SQL.  I would create another virtual machine (Windows Server 2008 R2) that would be running Remote Desktop Services. VMware will be installed on the new physical server. “

What I don’t understand is the tech fellow installing on this new computer VMware as the operating system – and then later he creates virtual machines? In those virtual machines he then installs server 2008? I thought one installed first server 2008 as Host ; then install VMware, and then create virtual machines with server 2008 installed as guest?  Thanks for helping me understand what this upgrade to server 2008 and virtual machines entails.

[a_p_]

The tech is correct. VMware ESXi is a Type-1 Hypervisor which is installed on physical hardware. With ESXi installed you can create and run multiple guests as virtual machines.

There are other types of Hypervisors (Type-2) which are installed as applications on an existing operating system. Examples are VMware Workstation and/or VMware Player. However these are not really targeted towards production use.

André

PS: Discussion moved from VMware Player to VMware ESXi 5

[sparrowangelste]

parv,

maybe you are coming from a vmware server background? you would be correct that you would have instaleld a OS like microsoft then install the vmware software then install the virutalized os.

But as a.p stated esxi is a Hypervisor, so this means you wouldnt need to install a host os like windows 2008 because esxi is the host os and is more efficient.

[Parvardigar]

I couldn't figure out how to replay in the discussion area ; let me inquire here ; is the VMware ESXi Type-1 Hypervisor free?

I downloaded the iso and have the license key /and need to test out ESXi in our test environment.... there will be a point in the future when we buy the Proliant ML350G7 Server / and I need to collect a cost assessment for mangement. Let me know if there are prices and so forth,

Thanks

[iw123]

Hi

Yes, there is a free version of ESXi which you can download and use, however it does have some limitations. To use the advanced features you would need to purchase a different licence for your host(s) and use the mangement server (vcenter), which is also a licensed product.

[Josh26]

He is completely correct in what he says.

Howevever, on an unrelated note, I don't like the odds of Oracle and MS SQL coexistinging very well. I would probably suggest your environment should use three Virtual Machines.

Did the IT technician supply pricing? Your VMware costs will depend heavily on the configuration. Given it's a single server, if it has less than 32GB RAM, there is nothing to gain by not using the free edition.

[Parvardigar]

This long note is an expression of my learning curve.

I need to follow up on this post. I downloaded and installed on a test computer, HP ML110 G3 VMWare ESXI 4.1.

I can login ‘root’ to view ‘system customization’.

I thought on the HP ML110 G3 I could simply create a virtual machine running Server 2008. I come from Windows server domain environment. I thought that the VMware ESXi was a VMware server – and that I could install directly on this server a virtual machine running Windows Server 2008.

Thus I downloaded and read ‘getting started with ESXi Installable’.

I did everything correct. What is stated in the article I did achieve.

I can ping from one of the workstations the ESXi ip address.

I then installed on this XPPro workstation VSphere Client.

As per articles instructions. As the article suggested I installed an application ‘AV50_EX_OVF’. I did this to experiment and see what would happen.

However running a ESXi Server from a workstation isn’t what I expected

- accessing from the XP computer using VSphere Client to interface with (ESXi ) \\daze-pc. This is how far I have come along in this project.

My assumption is that when we replace our Proliant Windows Server 2003 with a new HP ESXi server that the Server 2008 virtual machine would be created directly on the HP ESXi server. I am thinking start with a stand alone server. For example logging into the HP ESXi Server and viewing the virtual machines –Server 2008R2. And that from the Windows 7 workstations the users could access Navision Attain and/or a RDP Session and so forth.

Another way of saying this if I had no workstations and just one stand alone Proliant ML350 with ESXi installed can I then install on the ESXi stand alone Server box  Microsoft Server Virtual Machines. Thanks!

[Josh26]

Parvardigar wrote:

Another way of saying this if I had no workstations and just one stand alone Proliant ML350 with ESXi installed can I then install on the ESXi stand alone Server box  Microsoft Server Virtual Machines. Thanks!

You will always need a client machine.

You said you have Windows 7 desktops - any one of them can be used.

[Parvardigar]

The mental lights are finally firing off...this should be the final question.

From the vSphere client I access ESXi - the virtual machines - the virtual machines that recide on the ESXi server?

If I create a Windows Server 2008 virtual machine 'from within the client' the install takes places on the ESXi server - and that is where the 2008 virtual machines recides? Why I ask is if the vSphere client fails ... no issue because all the virtual machines recide and exist on the ESXi server?

I know this is basic but I have spent a decade living on a Microsoft Server Domain. I log into the Server and fiddle around there -except when I do a local mstcs and/or a Citrix login. Thanks for indulging these questions.

[Josh26]

Parvardigar wrote:

2008 virtual machines recides? Why I ask is if the vSphere client fails ... no issue because all the virtual machines recide and exist on the ESXi server?

Correct.

I can start an OS installation of a guest, shutdown my laptop with the vSphere client, drive home and reconnect and continue the installation without an issue.