Setting up VMware – Part I

VMware

For the uninitiated, VMware is software for creating Virtual Machines.  “Virtual Machines?” you say?  “Like the matrix?”  No, no, no.  This is having multiple servers of different OS types running on one physical computer.  Say for example you want to have 2 separate servers, however neither of them is taxed too hard so that you essentially don’t need the power consumption of two PCs nor have the room for a second one.  If you could combine the two physically, and yet still have them seperate in all other aspects, VMware is the answer.

Types of OSes

VMware can be installed on Windows or Linux.  The virtual OSes can also be Windows or Linux.  For a list of supported supported host Operating systems consult page 25 of the User’s Guide or page 32 for a list of supported guest operating systems.  This list involves mostly Windows Server 2003 series, Mandrake Linux, Red Hat Enterprise Linux, SUSE Linux Enterprise Server and Ubuntu Linux distros.  I however am going to attempt this daring feat with Debian instead of the listed supported OSes.

Specs

Before starting, I’d highly recommend scanning over the Users Guide.  This will give you a an idea of whether your machine can handle this or not.  My specs are not exactly what they recommend.  I’m running an old salvaged Dell PC with a 2.4Ghz Pentium processor and I upped the RAM to 1GB.  It suggests a minimum of 733Mhz processor and 512MB or RAM, but suggests 2GB of RAM.  My little machine here can’t handle more than a gig.  The processors that it suggests are server types:  Intel Xeon Dual Cores, AMD Opterons.  So needless to say my setup may struggle, but then again, I’m not going to do a whole lot either.

Obtaining VMware

You can download VMware free from the developers website, or another mirror.  You can get support from them as well, however I imagine that is NOT free.  Their download page as of the time of this posting says it’s version 1.0.6, however I found a 2.0.2 version at filehippo.

I’ve downloaded the tarball since I am using a Linux server.  VMware-server-2.0.1-156745.i386.tar.gz

Getting started

Here’s my step by step process.  (my commands in black, the computers response in red)

So now I’ve got to  make sure “killall” is installed.

And I try again and this time I answer “yes” to specifying the location of killall.

What?  I’m missing “make”?  I have a second terminal window open, so I can do other things and not interrupt my install process.  The first thing to do is make sure I am missing make.  The second is to install it.

Okay, now we return to the previously scheduled install.

Okay, now we break out again and use our other session to look for and/or install our gcc compiler and follow the same steps as before.

Again to the other terminal.

Wow, and we were so close.  Okay, highlighted above are what we’ll have to address.

Well our using a different version of our C compiler did not pan out for us.  So let’s fix that

Now we have the version of gcc that we need.  So let’s start our install script again.

Here’s where we get to watch reruns.  It pretty much repeats much of what we’ve seen before minus things such as our compiler and anything else we’ve fixed.  Although it does like to ask where our killall program is.

And yet, another snag.  Seeing as how I told it where my gcc compiler was before I removed it and installed a more agreeable one, the installer is remembering the path that I specified earlier and is having trouble compiling.

This was remedied by creating a symlink to the correct path.

Now our script moves along . . .

So far so good.  I won’t go through the next section of networking.  This is something for another day if you don’t already have it figured out.

SUCCESS!

Now that we have our VMware installed and configured, it’s time for a celebratory beer.  Our next task will be working with the web interface for our guest OSes.

Stay tuned.

sudoers

Where’s my SUDO?

Installing different flavors of Linux can be fun and exciting at times.  And it can have you scratching your head.

Take for instance, my first Linux install was Ubuntu.  Of course, this is a nice intro to anyone new to the Linux game, especially with it’s nice graphical interface.  Now when I looked for help on the net, I was directed to use the SUDO command whenever I needed to issue a command requiring Super User abilities.  This was a nice feature and worked as expected.

Now even though Ubuntu is a derivitive of Debian, it is not exactly the same.  It apparently came packaged with SUDO, whereas when I went to install Debian, it did not.  Shortly after my install, I attempted to install or configure certain things, and I was given the response that the SUDO command was not found.  I thought I had broken something.  But alas, all was not lost.

Super User

Of course, what SUDO does is issues the command that follows as if you were logged in as Super User.  Now, I had to install SUDO, but without SUDO.  Easy enough.  Just log in as Super User with the “su” command.  Of course, the password you setup for the super user is necessary.

Once in, no SUDO or anything else is needed to use your godlike skills.  Issue the APTITUDE INSTALL SUDO (or apt-get if you prefer) to install SUDO.  Make sure to exit out of super user when you’re done.

Now that you’ve got SUDO installed, you may still have trouble, this being due to the fact that you are not on the list of privileged users to issue Super User commands at will.  You must add yourself to the /etc/sudoers file.  Oh darn, you can’t do that without SUDO abilities.  Or can you.  Oh yeah, never should have exited out of Super User mode so quickly.  I guess I did tell you to, did I not?  That’s okay, back in, edit the file with your favorite editor and voila, exit out of Super User again.  We’re done now, I promise.

While you’re in the sudoers file, find the line that reads # User privilege specification and copy/paste the line below that reads root    ALL=(ALL) ALL and then change root to your name.  You can add other users this way as well, however the more you add, the more problems you invite.  It’s best to reserve this privilege only to those you trust.

MTR – Network Diagnostic Tool

Traceroute

You may have used traceroute in a Micrsoft OS or in Linux.  It’s quite simple and can tell you a few things about the connection between you and any other device on the internet.   Just type in traceroute <domain name> and hit enter.  You should see something like the following.

The second column lists the name (or IP) of the next device interface, and then the next column it’s IP address.  This goes on until you hit the destination.  All the while you are given the time it has taken to send the ICMP message to each device and then the return message.  If you notice, the further away the device is, the longer it takes.  But not always, as the last two devices show ~66ms while #11 had ~82ms to ~87ms.

If you were having problems on the internet and it seemed there were a bottleneck somewhere, this nice little tool can help you identify if one exists.  Perhaps if one of those above was returning ~70ms and then the next device gave you ~250ms.   That’s a noticeable difference, and it could indicate the the link between those two devices has maxed it’s bandwidth at that particular time.   Not that you could do anything about it.

MTR

So what if the problem were intermittent, or traceroute did not show any problems because perhaps the chokepoint is experiencing intermittent bursts of data?  Enter MTR, the big brother to traceroute.  MTR (or My Trace Route) can show you a constant display of each link and how it’s holding up.  Take a look.

If you have MTR installed (aptitude install mtr), run it as you would traceroute.  i.e. MTR YAHOO.COM

Click to see full image

The default display looks much like a regular traceroute display, aside from the data is constantly changing and there’s a few more columns of information.  The data changes due to the fact that it’s constantly getting data for you, no once, but constantly until you quit.

After the hostname, you are given columns telling you how much packet loss you get.  How many packets were sent.  Then you get to see how the pings are doing.  You get what the last time it took for the response, the average time, the best it’s been to that particular host and the worst time.  You also get a standard deviation.   Not exactly sure on this one yet, but lower seems better.

As you can see from the example above, once we went from device #4 to  #5, the pings doubled and then from # 5 to #6, the pings doubled again.   The first time it doubled, it’s not too bad because that’s an increase in 30ms whereas the second jump was a good 72+ ms.

Not that I’m saying here’s a bottleneck, by no means.  However, if anywhere between me and nandomedia.com there would be one, that’s my first suspect.   This trace is pretty simple anyway.  If I were to see much larger numbers then I would be concerned.  Again, not that I can do anything about it, but at least I know it’s not my network, unless the problem was on my network, then I’ll point fingers.

Click to see full image

Hit the D key.  Here you can change the display.   You get a nice view of the packets as they are returned.  This first view does not offer much, so hit the D key again.   DO IT!!!  You’ll like it.  At least better than this view.

Click to see full image

Now this is much more informational.  On the bottom of the screen is a scale.  It shows you what each dot, number and letter up above mean.  The period is 7ms and as you can see from my PC to my router, that’s what it should be.  The next hop is to my ISP and there’s 3’s all along there and the other 2 routers at that location.  The 3 is less than 54ms, but since it’s not a 2, it’s greater than 29ms.  You see an ‘a’ and a ‘b’ up there too.  So the return just from my ISP had a ping return over 54ms and one over 120ms just in these 57 pings.

The display is nice because it scrolls nicely to the left and you can see if there’s just a burp as in the ‘c’ at location #9 or if there’s a serious problem.  And if you need to resize your terminal window, MTR will adjust what it displays with ease.  Above it’s got room to show the last 57 pings, but if I widened it, it would quickly change accordingly.

So, as traceroute is handy, it’s not constant, it gives a snapshot and things may be fine at that moment.  Ping is okay, but does not provide very much info.   MTR is the all around tool to replace both.

apt-get or aptitude

Installing Software

When you install software for windows, there is many ways to go about that.  You can have a CD-ROM with the program and install directly from that.  You can download a zip file, extract the files and install the extracted program.  You can download an installer that will then download the necessary files off the net.

With Linux, there is also a variety of ways.  One of these is using apt-get or aptitude.  You may have seen on the internet instructions on installing some software within debian or ubuntu where someone gave the command apt-get install <program>.  The alternative is to replace apt-get with aptitude.  What’s the difference?

From the users point of view, there is no difference.  However confirmed reliable sources have brought out the fact that aptitude will handle dependencies much better.

To quote IRONWALKER from the linuxquestions.org forum:

Aptitude is said to deal with dependencies better than apt-get. For example, say you install a package which automatically installs some library packages because it depends on them. When you remove this package with apt-get, it won’t remove the libraries this package installed, although they aren’t used anymore.

When you install that package with aptitude and remove it with aptitude, aptitude ‘detects’ that those library packages aren’t used anymore and will therefore automatically remove them.

To sum up, aptitude will clean things up when you remove a program.  It will also check to make sure no other program needs the files it wants to remove before doing so.

The thing to keep in mind is that if you chose to use one over the other, be consistent.

Graphical Interface

Synaptic Package Manager

For those who are running Gnome desktop interface (or KDE), you can use Synaptic.  This nice program will divide up the available programs into categories for you.  You can even search for whatever type of app you are interested in.

If you prefer to hang out in the CLI, you can issue aptitude by itself on the command line and get this interface.

aptitude package manager

It’s fairly easy and similar to the Synaptic Package Manager.  You can search for applications you’re interested in, you can install packages and uninstall them.  Not only can you navigate using your arrow keys on your keyboard, it also responds to your mouse.  Click on the menu above, or an item to the left to open it up.

This is one sweet app you should familiarize yourself if you like to move around the CLI, especially if you have a system setup without a GUI.

Of course, if you know the name of an application, you can just command line it and not enter the package manager.  For instance, you can just enter sudo aptitude install <filename>.  If you are unsure if an app exists, or perhaps it’s name, use aptitude search <filename>.    AND, as if that’s not enough, if you know just part of the name, enter that in.

The following command yields these results:  aptitude search blend

p   blender                                                     – Very fast and versatile 3D modeller/renderer
p   blender-ogrexml                                  – Blender Exporter for Ogre
p   enblend                                                    – Tool for compositing images
p   kwin-style-blended                             – a window decoration theme for KDE

Surprise

If you do bring up the aptitude package manager and find yourself in need of a little time killer, hit Ctrl-T and then P.

This works on my Debian system, but on my Ubuntu box it drops me back to the command line with the following message: “Ouch!  Got SIGABRT, dying..”   –  Weird.  I’ll have to figure that out another day.