Please help us improve HowtoForge and take our survey:
The Perfect Xen 3.1.0 Setup For Debian Etch (i386) - Page 6
5.4 Creating Virtual Machines (domU)(In this chapter I'm assuming that you've compiled a domU kernel to use with the virtual machines (/boot/vmlinuz-2.6.18-xenU). If you haven't, please replace all references to /boot/vmlinuz-2.6.18-xenU with /boot/vmlinuz-2.6.18-xen!) We will use xen-tools to create virtual machines. xen-tools make it very easy to create virtual machines - please read this tutorial to learn more: http://www.howtoforge.com/xen_tools_xen_shell_argo. xen-tools are available as a Debian Etch package, so we install that one right now: apt-get install xen-tools Next we edit /etc/xen-tools/xen-tools.conf. This file contains the default values that are used by the xen-create-image script unless you specify other values on the command line. I changed the following values and left the rest untouched: vi /etc/xen-tools/xen-tools.conf
Please make sure that you comment out the initrd line! At least on my installations I've never needed a ramdisk for virtual machines. The passwd = 1 line makes that you can specify a root password when you create a new guest domain. In the kernel line you must specify the domU kernel that you want to use for your guest domains. In the mirror line specify a Debian mirror close to you. Make sure you specify a gateway and netmask. If you don't, and you don't specify a gateway and netmask on the command line when using xen-create-image, your guest domains won't have networking even if you specified an IP address! Now let's create our first guest domain, xen1.example.com, with the IP address 192.168.0.101: xen-create-image --hostname=xen1.example.com --size=2Gb --swap=256Mb --ide \ A lot of switches are unnecessary here because we specified the same details in /etc/xen-tools/xen-tools.conf but it shows that you can specify the desired settings either on the command line or in /etc/xen-tools/xen-tools.conf. Please make sure that you specify --ide, otherwise your virtual machine might not boot! (To learn more about the available options, take a look at the xen-create-image man page: man xen-create-image ) The xen-create-image command will now create the xen1.example.com virtual machine for us. This can take a few minutes. The output should be similar to this one: server1:/usr/src/xen-3.1.0-src# xen-create-image --hostname=xen1.example.com --size=2Gb --swap=256Mb --ide \ (You can ignore this warning: WARNING modprobe loop loop_max=255 The virtual machine will work nevertheless.) There should now be a xen1.example.com configuration file - /etc/xen/xen1.example.com.cfg. Take a look at it to become familiar with virtual machines configuration files: cat /etc/xen/xen1.example.com.cfg
To start the virtual machine, run xm create /etc/xen/xen1.example.com.cfg Run xm console xen1.example.com to log in on that virtual machine (type CTRL+] if you are at the console, or CTRL+5 if you're using PuTTY to go back to dom0), or use an SSH client to connect to it (192.168.0.101). To get a list of running virtual machines, type xm list The output should look like this: server1:~# xm list To shut down xen1.example.com, do this: xm shutdown xen1.example.com If you want vm01 to start automatically at the next boot of the system, then do this: ln -s /etc/xen/xen1.example.com.cfg /etc/xen/auto Here are the most important Xen commands: xm create -c /path/to/config - Start a virtual machine. Let's create a second vm, xen2.example.com with the IP address 192.168.0.102: xen-create-image --hostname=xen2.example.com --size=2Gb --swap=256Mb --ide \ Afterwards, you can start xen2.example.com like this: xm create /etc/xen/xen2.example.com.cfg and shut it down like this: xm shutdown xen2.example.com A list of all virtual machines that were created with the xen-create-image command is available under xen-list-images server1:~# xen-list-images Name: xen2.example.com To learn more about what you can do with xen-tools, take a look at this tutorial: http://www.howtoforge.com/xen_tools_xen_shell_argo You can check which kernel you are using by running uname -a You can do this on both dom0 and domU. For example, on my xen1.example.com virtual machine for which I have compiled a special domU kernel, the output looks like this: xen1:~# uname -a
|






print: 
Recent comments
1 day 9 hours ago
1 day 12 hours ago
1 day 16 hours ago
3 days 9 hours ago
3 days 9 hours ago
3 days 10 hours ago
5 days 11 hours ago
6 days 20 hours ago
1 week 11 hours ago
1 week 16 hours ago