{"id":8236,"date":"2018-03-06T16:30:59","date_gmt":"2018-03-06T13:30:59","guid":{"rendered":"http:\/\/trueconf.com\/blog\/?p=8236"},"modified":"2025-11-25T14:06:39","modified_gmt":"2025-11-25T11:06:39","slug":"configure-xen-hypervisor-ubuntu-server-14-4-05","status":"publish","type":"post","link":"https:\/\/trueconf.com/blog\/knowledge-base\/configure-xen-hypervisor-ubuntu-server-14-4-05","title":{"rendered":"How to configure Xen hypervisor on Ubuntu Server 14.4.05?"},"content":{"rendered":"

TrueConf Server<\/a> can be run on a virtual machine. However, it is complex and inadvisable to implement for inexperienced users, as enabling a virtual machine to operate correctly can be quite difficult at times.<\/p>\n

This manual will teach you how to configure\u00a0Xen<\/a> hypervisor<\/a> on Ubuntu Server 14.04.05 Server x86-64.<\/p>\n

\n

This article is for informational purposes only and does not necessarily guarantee full server operation after taking all the steps. TrueConf Technical Support does not advise<\/b> users on configuring virtual machines and running TrueConf Server on them. A virtual machine is an external system, which does not depend on TrueConf application. Its configuration and support are entirely user\u2019s responsibility.<\/p>\n<\/div>\n

Step 1: Install Xen and configure the bootloader<\/h2>\n

First you need to update system packages:<\/p>\n

$ sudo apt-get update && sudo apt-get upgrade<\/pre>\n
After that, install Xen:<\/p>\n
$ sudo apt-get install xen-hypervisor-amd64 xen-utils xenwatch xen-tools xen-utils-common xenstore-utils<\/pre>\n
Use the following commands to configure default Xen boot:<\/p>\n
$ sudo mv \/etc\/grub.d\/10_linux \/etc\/grub.d\/20_linux\r\n$ sudo mv \/etc\/grub.d\/20_linux_xen \/etc\/grub.d\/10_linux_xen\r\n$ sudo update-grub<\/pre>\n
Restart the OS and Xen. Next time the system is booting, \u00a0Xen will start automatically:<\/p>\n
\"\"<\/a><\/p>\n
Step 2. Install and configure libvirtd<\/h2>\n
Install libvirtd:<\/b><\/p>\n
$ sudo apt-get install python-libvirt libvirt-bin libvirt0 python-imaging python-numpy virtinst virt-viewer virt-manager<\/pre>\n
After that, configure libvirtd<\/b> for Xen default operation. To do this, edit the \/etc\/libvirt\/libvirt.conf<\/b> file. In this file, uncomment (remove the # symbol at the beginning) the line starting with “#uri_default”<\/b> and replace it with the following line: uri_default = “xen:\/\/\/system”<\/b>.<\/p>\n
Next, add exceptions to the apparmor<\/a>\u00a0protection tool:<\/p>\n
$ sudo ln -s \/etc\/apparmor.d\/usr.sbin.libvirtd \/etc\/apparmor.d\/disable\/\r\n$ sudo apparmor_parser -R \/etc\/apparmor.d\/usr.sbin.libvirtd\r\n$ sudo \/etc\/init.d\/apparmor restart<\/pre>\n
After that, check if the current record is in the libvirtd <\/b>group:<\/p>\n
$ cat \/etc\/group | grep libvirtd<\/pre>\n
Here is a typical command output if the group contains\u00a0111<\/b>\u00a0group and\u00a0andrey<\/b>\u00a0as a user:<\/p>\n
libvirtd:!:111:andrey<\/pre>\n
If the current user is not in the group, add him\/her using a separate command:<\/p>\n
$ sudo adduser `id -un` libvirtd<\/pre>\n
Adding user 'andrey' to group 'libvirtd' ...\r\nAdding user andrey to group libvirtd\r\nDone.<\/pre>\n
After that, it is mandatory to re-enter the system and verify if Xen starts successfully.<\/p>\n
Step 3: Create a Network Bridge<\/h2>\n
Next, create a network bridge<\/a>. To do this, you might need to edit \/etc\/network\/interfaces<\/b> file.<\/p>\n
In this file there is a line setting the main network interface. It can be found after the \u00a0“# The primary network interface” <\/b>line-comment. If the network interface is set to eth0<\/b> (the line reads “auto eth0”<\/b>), it must be replaced with br0<\/b>, and four new lines must be added to the end of the file:<\/p>\n
bridge_ports\u00a0eth0\r\nbridge_stp\u00a0off\r\nbridge_maxwait 0\r\nbridge_fd\u00a00<\/pre>\n
The picture below shows an example of this type of editing. However, instead of changing the line “auto eth0”<\/b>, we commented it (added #<\/b> in the beginning to make it being ignored) and added a new line after it (with an additional comment before it).<\/p>\n
\"\"<\/a><\/p>\n
After that, restart the network or the entire operating system (highly recommended):<\/p>\n
$ sudo \/etc\/init.d\/networking restart\r\n$ sudo shutdown \u2013r now<\/pre>\n
Step 4. Configure the network gateway<\/h2>\n
To configure the gateway, edit \/etc\/sysctl.conf<\/b> file. Find and uncomment the following line:<\/p>\n
net.ipv4.ip_forward=1<\/pre>\n
After that, enter the command to apply changes and restart the OS again:<\/p>\n
$ sudo sysctl -f\r\n$ sudo shutdown \u2013r now<\/pre>\n
Step 5: Check virtualization capabilities<\/h2>\n
After the system is rebooted, create the first virtual machine:<\/p>\n
$ sudo apt-cache search virt-instal\r\n$ sudo apt-cache search virt-viewer<\/pre>\n
To install Windows 2012 (which will be installed in this example) or any other system not ported to Xen, Intel\u00ae Virtualization Technology (VT)<\/a> or Pacifica (AMD) virtualization technology support is required. Xen should also support hardware virtualization. To check it, use the following command:<\/p>\n
$ xm info | grep caps\r\n<\/pre>\n
hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f\r\nxen_caps : xen-4.4-x86_32p hvm-4.4-x86_32 hvm-4.4-x86_32p<\/pre>\n
Based on hvm-4.4-x86_32<\/b> output, Xen has successfully detected a processor that supports Intel VT or AMD-V technologies.<\/p>\n
If this command displays another message but you are sure that the processor has architectural virtualization extensions, check the BIOS settings and use VT support if you haven\u2019t done it yet.<\/p>\n
Your motherboard BIOS may artificially disable virtualization. In this case, update or fix the BIOS.<\/p>\n
Step 6. Create a virtual machine<\/h2>\n
Just in case, check which virtual machines are running now.<\/p>\n
andrey@ubuntu:~$ sudo virsh -c xen:\/\/\/system list<\/pre>\n
The output is empty, as it should be if no virtual machine is running. Next, create a Xen disk image:<\/p>\n
andrey@ubuntu:# mkdir -p \/root\/xenimages\r\nandrey@ubuntu:# cd \/root\/xenimages\r\nandrey@ubuntu:# dd if=\/dev\/zero of=WS2012.img bs=1M count=4096<\/pre>\n
Create Windows 2012 ISO image, which will be used during the installation. In our case, we\u2019ve placed it in the \/root\/xenimages<\/b> directory.<\/p>\n
Create the \/etc\/xen\/win2012 <\/b>configuration file and fill it in using the following example:<\/p>\n
kernel = \"\/usr\/lib\/xen\/boot\/hvmloader\"\r\nbuilder='hvm'\r\nmemory = 2048\r\nname = \"win2012\"\r\nvcpus=1\r\npae=0\r\nacpi=0\r\napic=0\r\ncpus = \"\"\r\nvif = [ 'bridge=br0' ]\r\ndisk = [ 'file:\/root\/xenimages\/WS2012.img,ioemu:hda,w' ]\r\non_poweroff = 'destroy'\r\non_reboot \u00a0\u00a0= 'destroy'\r\non_crash \u00a0\u00a0\u00a0= 'destroy'\r\ndevice_model = '\/usr\/lib\/xen\/bin\/qemu-dm'\r\ncdrom='\/root\/xenimages\/en_windows2012.iso'\r\nboot='d'\r\nsdl=0\r\nvnc=1\r\nvncviewer=0\r\nstdvga=0\r\nserial='pty'\r\nne2000=0<\/pre>\n
Please note that boot = ‘d’<\/b> parameter is required for installation. Subsequently, it must be replaced with boot = ‘c’<\/b>. Guest domain will be accessed through VNC. The use of SDL is not presupposed.<\/p>\n
After creating \/etc\/xen\/win2012 <\/b>configuration file, start the installation and try connecting to the domain using VNC. To do this, run vncviewer <\/b>immediately after creating the domain:<\/p>\n
$ xl create \/etc\/xen\/win2012<\/pre>\n
Using config file \"\/etc\/xen\/win2012\". \r\n\r\nStarted domain Win2012\r\n\r\nvncviewer:0<\/pre>\n
Step 7. Install TrueConf Server<\/h2>\n
Once virtual machine has been successfully configured, just install TrueConf Server and get started. With our guide<\/a>, it takes only 15 minutes<\/p>\n","protected":false},"excerpt":{"rendered":"
TrueConf Server can be run on a virtual machine. However, it is complex and inadvisable to implement for inexperienced users, as enabling a virtual machine to operate correctly can be quite difficult at times. This manual will teach you how to configure\u00a0Xen hypervisor on Ubuntu Server 14.04.05 Server x86-64. This article is for informational purposes […]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[260],"tags":[191],"class_list":["post-8236","post","type-post","status-publish","format-standard","hentry","category-knowledge-base","tag-deployment","wpautop"],"_links":{"self":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts\/8236","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/users\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/comments?post=8236"}],"version-history":[{"count":23,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts\/8236\/revisions"}],"predecessor-version":[{"id":40753,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts\/8236\/revisions\/40753"}],"wp:attachment":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/media?parent=8236"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/categories?post=8236"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/tags?post=8236"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}