By default OpenVZ is using VENET as network device. It does packet switching based on IP header, which makes it look like a point-to-point connection between VPS and the physical host. An alternative device is Virtual Ethernet device (a.k.a. VETH).

Suppose you made a mistake on the Vserver name when creating it. After finished the installation, you might want to rename your Vserver. This can be accomplished by renaming the config directory and the root for the vserver in question, then modifying some symlinks to match.

Recently I’m playing with Xen virtualization, and I came across one protential problem. As I need to share my guest machines to clients,  I must give them root privileges… that’s whats VPS-es all about… having root access to OS without having to purchase expensive physical ones.  So [...]

In a former post, we know how to use OpenVZ to create virtual system in CentOS, this article will show you how to install Windows under Xen on CentOS 5.3. We fixed one of the problems of Windows XP under Xen. Windows XP’s inability to shut itself down completely. Windows ends up on the ‘it [...]

This article will describe how to create OpenVZ container in CentOS 5.4. With OpenVZ you can create multiple Virtual Private Servers (VPS) on same hardware machine and running them simultaneously and efficiently. OpenVZ is the open-source branch of Virtuozzo, a commercial virtualization solution widely [...]

Sometimes you do not have access to source code or you really do not want to compile the code. Then Red Hat Enterprise Linux provides the service called ia32el. The ia32el package contains IA-32 Execution Layer platform which allows emulation of IA-32 binaries on IA-64.(i.e. it allows to run 32-bit [...]

AMD and REDHAT have just done the so called impossible, and demonstrated VM live migration across CPU architectures. Not only that, they have demonstrated it across CPU vendors, potentially commoditising server  processors. Eeek!