Xen
(or whatever the name of the RPM is).
Installing Xen from source is more complicated, as it involves patching and recompiling the Linux kernel. Installing from source is not covered in this article, and is described thoroughly in the Xen User Manual (www.cl.cam.ac.uk/Research/SRG/netos/xen/documentation.html).
After Xen has been installed, we need to configure the bootloader. For GRUB users, edit the menu.lst file, and add this entry:
title Xen kernel /boot/xen-3.0.gz dom0_mem=32768 module -->/boot/vmlinuz-2.6-xen0 root=/dev/hda7 ro console=tty0
vmlinuz-2.6-xen0 is the kernel image that would have been installed by the tarball binaries or RPM; if you install from source, replace the name of the image here.
Also be sure to replace the name of the root filesystem to suit your system (in this example, it is root=/dev/hda7).
For LILO users, do the following:
image="/boot/xen-3.0.gz label="Xen" root="/dev/hda7" read-only append="dom0_mem=32768"
After Xen has been installed and configured, you are now ready to boot in to Xen and start your first virtual machine.
After rebooting and starting your Xen installation, which resembles a normal Linux startup, log in to Domain0. That is the most-privileged domain in a Xen system.
From here, users can create virtual machines that will run guest operating systems, and start and stop virtual machines.
To create a new virtual machine, you need to define a configuration file for it. Xen comes with two default configuration files in the /etc/xen directory named xmexample1/ amd xmexample2/. The configuration files contain many parameters, but fortunately, many of them are optional. You need only a few configured parameters to get your virtual machine running. Some important parameters include:
Kernel: which kernel to boot.
Root: the root filesystem.
Disk: on which disk partition the system is installed.
Memory: define how much memory the virtual machine should use.
A sample configuration file may look like this:
kernel = '/boot/vmlinuz-2.6.12.6-xen' disk = [ 'phy:hda1,hda1,w' ] root = '/dev/hda1 ro' memory = 128
After declaring a configuration file for the virtual machine, you can boot up the machine by typing the following:
bash# xm create -c /root/myOSconf vmid=1
where myOsconf is the name of the configuration file.
After this, a new window will pop up, and you will see a normal Linux startup until you reach the login screen, and from there you can enjoy your new guest OS.
Xen is mature, open-source virtualization software that creates many new opportunities for organizations in reducing their total cost of ownership and providing more dependable and high-availability applications. Commodity x86-based systems provide all of this, with a minimum cost of porting an operating system to Xen.
The developers of Xen have tested Xen against other popular virtualization solutions, such as VMware Workstation and user-mode Linux. In all tests conducted, Xen out-performed the other approaches—in standard benchmark tests, such as Spec Int200, Spec Web99, dbench and many more. The results were published in a research paper, available at www.cl.cam.ac.uk/Research/SRG/netos/papers/2003-xensosp.pdf.
Irfan Habib has been an open-source enthusiast for five years. He has great interest in distributed computing technologies, in which he does full-time research, and he loves to explore new solutions to common problems in computing. Comments can be sent to him at irfan.habib@gmail.com.
- « first
- ‹ previous
- 1
- 2
- 3
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Designing Electronics with Linux
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Kernel Problem
8 hours 32 min ago - BASH script to log IPs on public web server
12 hours 59 min ago - DynDNS
16 hours 35 min ago - Reply to comment | Linux Journal
17 hours 7 min ago - All the articles you talked
19 hours 31 min ago - All the articles you talked
19 hours 34 min ago - All the articles you talked
19 hours 35 min ago - myip
1 day 37 sec ago - Keeping track of IP address
1 day 1 hour ago - Roll your own dynamic dns
1 day 7 hours ago




Comments
Mr. Habib: You mention in
Mr. Habib:
You mention in the article:
"VMware's approach does have one large advantage over Xen's approach. VMware is capable of virtualizing proprietary operating systems. As I discuss later in this article, you have to port an operating system's kernel to Xen for it to work with Xen. You cannot run an operating system on Xen otherwise."
I'm not sure this is exactly correct, in the case of Xen running
on a cpu with AMD-v or Intel VT hardware extentions, you can
run proprietary OS's raw with no porting of the guest OS to xen.
In the case of AMD, you'd have to use a AM2 or later chip or
with Intel any of the recent Core 2, Xeon or other chips with
Vanderpool support.
Mark Schlegel