Mar 17

The London Internet Exchange (LINX) was having problems again last night causing routing issues for a number of ISPs. Users reported intermittent access to websites and packet loss causing poor gaming performance. At the present time the cause of the outage is not yet known.

Tagged with:
Feb 24

Fasthost support is an interesting one. Fasthosts.co.uk are part of one of the largest companies in the world – United Internet AG who are a German company and also own 1&1. Whilst their support appears responsive, and wait times are typically low for a response, the quality of the response is equivalently low. Nobody seems able to solve any problems – you may as well be talking to a bot. Of course, the support is outsourced somewhere where it is cheap for them to have people answering phones etc and communication can be a barrier.

The main problem is that to get any help, you have to have log-in to your account. To log-in to your account, you need your account details. If you have forgotten your account details, you need to contact support. See where this is going? All in all getting help from anyone at Fasthosts is a frustrating job.

Tagged with:
Jan 19

I recently had the misfortune to use a Justhost hosting package as part of some work I was doing for a client. The server was slow and unreliable, to the point that it was completely unsuitable for any kind of a business related website. Justhost may be OK if you’re hosting a very basic blog, but I can’t see anyone serious using them.

Tagged with:
Jul 19

The architecture of OpenVZ is different from the traditional virtual machines architecture because it always runs the same OS kernel as the host system (while still allowing multiple Linux distributions in individual containers). This single-kernel implementation technology enables running containers with a near-zero overhead. Thus, OpenVZ offer an order of magnitude higher efficiency and manageability than traditional virtualization technologies.

From the point of view of applications and container users, each container is an independent system. This independence is provided by a virtualization layer in the kernel of the host OS. Note that only a negligible part of the CPU resources is spent on virtualization (around 1-2%). The main features of the virtualization layer implemented in OpenVZ are the following:

  • A container looks and behaves like a regular Linux system. It has standard startup scripts; software from vendors can run inside a container without OpenVZ-specific modifications or adjustment;
  • A user can change any configuration file and install additional software;
  • Containers are completely isolated from each other (file system, processes, Inter Process Communication (IPC), sysctl variables);
  • Processes belonging to a container are scheduled for execution on all available CPUs. Consequently, CTs are not bound to only one CPU and can use all available CPU power.

A live migration and checkpointing feature was released for OpenVZ in the middle of April 2006. It allows to migrate a container from one physical server to another without a need to shutdown/restart a container. The process is known as checkpointing: a CT is frozen and its whole state is saved to the file on disk. This file can then be transferred to another machine and a CT can be unfrozen (restored) there. The delay is about a few seconds, and it is not a downtime, just a delay.

OpenVZ is free open source software, available under GNU GPL. OpenVZ is the basis of Parallels Virtuozzo Containers, a commercial virtualization solution offered by Parallels.

preload preload preload