As part of Host90  ongoing commitment to our customers to provide an excellent quality of service, we are in the process of upgrading our hardware  as part of our continual service improvement programme. This post will provide you  with information about Hostnode , type of upgrades, schedules,

Hostnode Login url:

chicago.host90.com:5353

or

184.154.49.1xx:5353

Schedule

Friday 11 February ,

20:02 Friday (EST)

Estimated Downtime

25 to 45 minutes

Planed Upgrades

1. Add 1 CPU
2. Add 12GB of ram
3. Add 1TB Hard disk
4. Upgrade from 100mb uplink to 1gb

We apologize for any inconvenience this may cause.

Thank you for understanding.

The physical server typically runs a hypervisor which is tasked with creating, destroying, and managing the resources of “guest” operating systems, or virtual machines. These guest operating systems are allocated a share of resources of the physical server, typically in a manner in which the guest is not aware of any other physical resources save for those allocated to it by the hypervisor.
The Guest system may be fully virtualized, paravirtualized, or a hybrid of the two.
In a fully virtualized environment, the guest is presented with an emulated or virtualized set of hardware and is unaware that this hardware is not strictly physical. The hypervisor in this case must translate, map, and convert requests from the guest system into the appropriate resource requests on the host, resulting in significant overhead. Almost all systems can be virtualized using this method, as it requires no modification of the operating system, however a CPU supporting virtualization is required for most hypervisors that perform full virtualization.
In a paravirtualized environment, the guest is aware of the hypervisor and interfaces directly with the host system’s resources, with the hypervisor implementing real-time access control and resource allocation. This results in near-native performance since the guest sees the same hardware as the host and can thus communicate with it natively. UNIX-like systems, such as Linux, some variants of BSD, Plan9, and OpenSolaris are currently known to support this method of virtualization. However, installing operating systems as paravirtualized guests tends to require more knowledge about the operating system in order to have it use special hypervisor-aware kernels and devices.
Some examples of paravirtualization-capable hypervisors are Xen, Virtuozzo, Vserver, and OpenVZ (which is the open source and development version of Parallels Virtuozzo Containers).
Hybrid or partial paravirtualization, is full virtualization, but in which the guest uses paravirtualized drivers for key components such as Networking and Disk I/O, resulting in greatly increased I/O performance. As such, it is a common solution for operating systems which cannot be modified (for various reasons) to support paravirtualiztion.
Uses

Virtual private servers bridge the gap between shared web hosting services and dedicated hosting services, giving independence from other customers of the VPS service in software terms but at less cost than a physical dedicated server. As a VPS runs its own copy of its operating system, customers have superuser-level access to that operating system instance, and can install almost any software that runs on the OS.

Certain software does not run well in a virtualized environment, including firewalls, anti-virus clients, and indeed virtualizers themselves; some VPS providers place further restrictions, but they are generally lax compared to those in shared hosting environments. Due to the number of virtualization clients typically running on a single machine, a VPS generally has limited processor time, RAM, and disk space.
Virtual private server hosting

A growing number of companies offer virtual private server hosting, or virtual dedicated server hosting as an extension for web hosting services. Some web hosting companies call a Virtual Private Server a Virtual Dedicated Server/Dynamic Dedicated Server or the other way around.
Unmanaged Hosting
The customer is left to monitor and administer their own server.

Buy a VPS Now !

Source : http://en.wikipedia.org/wiki/Virtual_private_server

if you are on a windows machine then you will need to download putty

once you have downloaded putty , open it up and in Hostname ( or IP address) type your VPS IP address and click on ( Open)

you will be asked to login , login as ( username=root password= your ssh password )
and the copy the command below and right click to paste it into putty to download kloxo to your server

wget http://download.lxlabs.com/download/kloxo/production/kloxo-install-master.sh

When done Copy and paste the command below :

sh ./kloxo-install-master.sh

Once kloxo is installed, you can connect to ‘http://machine-name:7778′, and you will be presented with a login screen – the password would be ‘admin’. Once you login, Kloxo will explicitly force you to change the password to something other than ‘admin’.