Creating A Virtual Machine

Creating a virtual machine from scratch is a three step process.

First I ran the New Virtual Machine wizard to create a virtual machine. The NewVirtual Machine wizard guided me through the key steps for setting up a new virtual machine, helping me set the virtual hardware specifications and other parameters. A virtual machine provides a base x86 platform and you use the wizard to choose devices to install on that platform. For example, you select the number of virtual processors, the amount of memory, the virtual disk capacity, and so forth. Next I set the virtual machine to connect to a physical CD-ROM device or an ISO file, power on the virtual machine, and install the operating system just like you would for any new physical machine. Finally, I installed VMware Tools to enhance the performance and manageability of the virtual machine. The VMware Tools installation wizard automatically selects the VMware Tools version appropriate for the operating system running in the virtual machine.

After creating a new virtual machine, like a physical computer, it has a blank hard disk. Before you can use it, you need to

partition and format the virtual disk and install an operating system. You can install the operating system from an installation CD-ROM or create an ISO image file and install from that file.The basic procedure to install the guest operating system from CD-ROMs is to first insert the installation CD or floppy into the physical device. Then on the VM menu on workstation menu bar for the virtual machine, click the Settings option to open the Virtual machine Settings editor. On the Hardware tab, for CD/DVD Drive, be sure to enable Connect at power on option under the Device Status. Then when you power on the virtual machine, it will boot from the installation CD. From there you can follow the instructions provided by the operating system vendor to partition the disk and install the operating system. A faster and often more convenient method is to install from an ISO image file. To do so, you must change the virtual machine settings to connect to the ISO image instead of the physical device. Virtual machines support both attended and unattended installations. You can install VMware Tools after installing the guest operating system VMware Tools is a suite of utilities that enhances the performance and manageability of a virtual machine. The installers for VMware Tools for Windows, Linux, FreeBSD, and NetWare guest operating systems are bundled into Workstation as ISO image files.

Viola, we have a virtual machine on our host…. Next week we will look at “configuring virtual networks”… Hopefully, this will keep you from making the same mistakes I and my two colleagues made.

Snap! This is not a “no Brainer”

Earlier this week I was walking past a desk with two “techies” deep in pensive conversation and actively gesturing. Curiosity got the best of me, so I asked them “What’s up”? Well it appears that they had just deleted and reinstalled a Windows VM in their VMware Workstation host and they could no longer see it. I smiled because I thought of something my father used to say, “if you live long enough, you are bound to see your old mistakes be committed by someone else”.

The trouble was that they did not remember that the default for a network adapter on a VM was NAT. This happens when we use the network wizard setting as “Typical”. They could not see the VM on the network because the network adapter setting needed to be set at “Bridged” for the VM to appear on an equal network status as the host. NAT configures a virtual machine to share the IP and MAC addresses of the host. The virtual machine and the host share a single network identity that is not visible outside the “workstation” network. In a “Bridged” network; the virtual network adapter in the virtual machine connects to the physical network adapter in your host computer, allowing it to connect to the LAN the host computer uses.

The point is, these folks were not novices and had easily overlooked a small but vital step. No, not the fact that when reinstalling the VM, they used all default settings but they did not remember the old adage; “when nothing else works, RTM….” It would have saved them energy and the irritation that a passer-by resolved their issue. They seemed relieved when I told them that that had just happened to me yesterday.

Fortunately, there is a cornucopia of knowledge to help you out of a jam. VMware has white papers, forums, training sessions, and videos. You are not alone…

Try it: you’ll like it….

This is aimed at the small to medium business that wants to get started in virtualization but thinks it takes too much of an investment. Well I’m here to tell ya – That aint the case. There are two VMware products with which you can start to learn what it’s all about and if you want to go further. One is VMware Server. VMware Server is a Free and easy way to get introduced to virtualization. VMware Server provides a risk-free introduction to Windows and Linux application server virtualization. I am currently evaluating it and the other introductory product – VMware Workstation 7.
The top three reasons many business use either of these products is (a) Test and Development of software and IT environments, (b) use of virtual machines to evaluate software, and (c) they want to assess what this virtualization thing is all about. Now before we go any farther, I want to let you know that there is another free product out there: It’s the VMware vSphere Hypervisor (ESXI). However, it does require a dedicated server (recommended 4GB Memory and dual socket, dual core). The next step after ESXI would be vSphere. So if you have a server with the requisite configuration, go for it. But if you are just feeling your way – look at VMware Server or VMware Workstation 7 to begin. There is a cost for VMware Workstation 7 – Approximately $190.00. Now let’s do a quick comparison of these two products.
First of all neither require a dedicated server. They both can run on a Dual Core PC (XP, Win 7, or Linux) with 2GB Ram. This is the minimum that I would recommend. Remember the more ram and processing power, the more virtual machines/better performance. Both can run either Windows or Linux as a guest operating system. OK, what are the differences? They are Basic. VMware Server is designed with the Data Center in mind… it is a Server product while VMware Workstation 7 (while more flexible) is built for the desktop/laptop. With Workstation 7 you can demonstrate a complete network solution on your laptop – You can even run ESXI on one of your virtual machines. OK, which should I use….? Remember the universal answer – It all depends.
Actually, I plan to use both…. I can use VMware Server to establish a small test and development lab to evaluate software. When I am ready, I can use the VMware upgrade roadmap so that I do not lose my infrastructure investment. I can also use VMware Workstation as a demonstration platform both for the infrastructure and developed solutions.
How will you use these entry points?