Compiling Xen-4.4 From Source And Installing It On Ubuntu Server (Amd-64)

  1. First of all, you should install a clean Ubuntu Server (Amd-64) on your server. (Version 14.04 is strongly recommended for the best compatibility)
  2. Get the souce code of Xen ready by "git clone". ((If some errors occur in this step, you may check the /ect/apt/source.list and update it by running "$ sudo apt-get update")
    1 $ git clone git://xenbits.xen.org/xen.git
    If you have not yet install "git", please run "sudo apt-get install git" on your terminal.
    1 $ cd xen
    Use "git branch" to show the versions of Xen: 
     1 $ git branch -av
     2   master                     3e2331d VT-d: suppress UR signaling for further desktop chipsets
     3   remotes/origin/HEAD        -> origin/master
     4   remotes/origin/master      3e2331d VT-d: suppress UR signaling for further desktop chipsets
     5   remotes/origin/stable-4.0  2692df2 compat/gnttab: Prevent infinite loop in compat code
     6   remotes/origin/stable-4.1  8995a94 page-alloc: scrub pages used by hypervisor upon freeing
     7   remotes/origin/stable-4.2  7bcdeb9 update Xen version to 4.2.5
     8   remotes/origin/stable-4.3  a153d8a update Xen version to 4.3.3
     9   remotes/origin/stable-4.4  be84c34 evtchn: check control block exists when using FIFO-based events
    10   remotes/origin/staging     3e2331d VT-d: suppress UR signaling for further desktop chipsets
    11   remotes/origin/staging-4.0 2692df2 compat/gnttab: Prevent infinite loop in compat code
    12   remotes/origin/staging-4.1 8995a94 page-alloc: scrub pages used by hypervisor upon freeing
    13   remotes/origin/staging-4.2 7bcdeb9 update Xen version to 4.2.5
    14   remotes/origin/staging-4.3 a153d8a update Xen version to 4.3.3
    15   remotes/origin/staging-4.4 be84c34 evtchn: check control block exists when using FIFO-based events

    Checkout to "stable-4.4" and create a new branch named "netopt" and then checkout to it:

    1 $ git checkout stable-4.4
    2 Switched to branch ‘stable-4.4‘
    3 $ git branch netopt
    4 $ git checkout netopt
    5 Switched to branch ‘net opt‘
  3. Before compiling the source code of Xen, you must install the dependencies: (If some errors occur in this step, you may check the /ect/apt/source.list and update it by running "$ sudo apt-get update")
    1 $ sudo apt-get install build-essential
    2 $ sudo apt-get install bcc bin86 gawk bridge-utils iproute libcurl3 libcurl4-openssl-dev bzip2 module-init-tools transfig tgif
    3 $ sudo apt-get install texinfo texlive-latex-base texlive-latex-recommended texlive-fonts-extra texlive-fonts-recommended pciutils-dev mercurial
    4 $ sudo apt-get install make gcc libc6-dev zlib1g-dev python python-dev python-twisted libncurses5-dev patch libvncserver-dev libsdl-dev libjpeg-dev
    5 $ sudo apt-get install iasl libbz2-dev e2fslibs-dev git-core uuid-dev ocaml ocaml-findlib libx11-dev bison flex xz-utils libyajl-dev
    6 $ sudo apt-get install gettext pandoc markdown python-dev
    7 $ sudo apt-get install libperl-dev libgtk2.0-dev libaio-dev gcc-multilib
  4. Now you can compile the source code and install Xen: (Note that this step takes a long time. Be patient!)
    1 $ ./configure
    2 $ make world
    3 $ sudo make install
  5. After step 4, Xen is already successfully installed on your machine. However, some post-installation operations is necessary:

    You can enable automatic start of Xen Project services on system startup:

    1 $ sudo update-rc.d xencommons defaults 19 18
    2 $ sudo update-rc.d xendomains defaults 21 20
    3 $ sudo update-rc.d xen-watchdog defaults 22 23

    By running "$ ls /etc/init.d/", you can find "xencommons", "xendomains" and "xen-watchdog". Note that Starting with Xen-4.3, "xend" is abandoned and replace by "xl".

    You also need to make some changes to "/boot/grub/grub.cfg" to correctly boot to xen.gz:

    1 $ sudo update-grub
    2 $ sudo vim /boot/grub/grub.cfg

    Modify the grub default option from "0" to "2": set default="2" (The option "2" normally locates the menuentry of "xen.gz")

  6. Reboot the Ubuntu Server: (Now your machine will automatically boot from Xen‘s core)
    1 $ sudo reboot
  7. You can run "sudo xl list" to test whether Xen is running correctly. If some errors occur, try to add a soft link to "libxenctrl.so.4.4":
    1 $ ln -s /usr/local/lib/libxenctrl.so.4.4 libxenctrl.so.4.4
    2 $ sudo ldconfig

    Then restart service xencommons:

    1 $ sudo service xencommons start/restart

    or:

    1 $ sudo /etc/init.d/xencommons start/restart 
    Congradulations! All steps are completed and now you can create a virtual machine by "sudo xl create **".
时间: 2025-01-01 02:59:50

Compiling Xen-4.4 From Source And Installing It On Ubuntu Server (Amd-64)的相关文章

Installing PHP5 on Ubuntu Server

When installing PHP 5 from source I ran into the following problems and solutions: Problem:configure: error: xml2-config not found. Please check your libxml2 installation.Solution:sudo apt-get install libxml2-dev Problem:configure: error: Cannot find

Installing Webmin on Ubuntu Server 10.04 LTS (Lucid)

I had some trouble installing Webmin 1.510 on Ubuntu 10.04 LTS Server (aka Lucid). The problem is that Webmin uses a deprecated Perl module (a wrapper around Digest::MD5 for users of an ancient MD5 library) and both Debian and Ubuntu refuse to put it

转: 解决Setting property 'source' to 'org.eclipse.jst.jee.server的问题

我发现这个问题上网搜索 ,找到的地址为:http://blog.csdn.net/z69183787/article/details/19911935 .但是他的标题上也有一个"转",我没找到原作者,暂时只把找到的原址标注一下吧 这是我于2013年9月4号晚遇到的问题,为了这个问题我一夜没睡!对于这个问题,我相信我的方法已经能帮90%的人解决了!当你用Eclipse运行web项目的时候,你就会看到控制台出现:WARNING: [SetPropertiesRule]{Server/Ser

警告: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:

当你用Eclipse运行web项目的时候,你就会看到控制台出现: 警告: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:TestServlet' did not find a matching property. 这样的字样,说的是server.xml的Service标签里的Engine标签里的Host标签里的Context标签配置了一个'source'属性

Visual Source Safe(VSS)和Team Foundation Server(TFS)比较区别

Visual Source Safe 是用于软件专业开发人员的源代码管理工具Team Foundation Server是为开发团队提供集成源代码管理.问题跟踪和进程管理的更改管理系统 相同点 1.同时开发产品的多个版本2.在不影响其他版本的情况下对产品的一个已发布版本进行更改3.快速检索一批相关文件,确定做出更改的用户和时间4.比较文件的两个版本以及将更改从一个版本移至其他版本5.都提供了命令行客户端和Visual Studio 2005 集成 不同点 1.结构区别VSSVSS 是仅包含客户端

eclipse下启动tomcat出现Setting property 'source' to 'org.eclipse.jst.jee.server: '错误的解决办法

在eclipse中启动tomcat时出现Setting property 'source' to 'org.eclipse.jst.jee.server:你的站点名'   did not find a matching property错误 解决办法: 1.在server控制台内,在服务器上点右键--属性 2.general选项卡中点switch location 这时,location变为:/servers/tomcat6.0 server at localhost.server 3.在pro

警告: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:20160928' did not find a matching property

新建一个动态web工程,在web-content目录下新建了一个a.jsp文件如下: 在servlet服务器上运行a.jsp,本来除以0应该出现报错,但是网页却显示如下结果: 控制台看到如下警告: 症状原因: 在eclipse配置好的tomcat服务器上双击,打开tomcat服务器的配置界面.按如下操作配置服务器:在Server Options勾上的选项,会在你部署web项目20160928 服务器会在tomcat根目录\conf\Catalina\localhost下自动创建的.xml的单应用

警告: [SetContextPropertiesRule]{Context} Setting property 'source' to 'org.eclipse.jst.jee.server:build-manager' did not find a matching property.

今天用Eclipse运行web项目的时候,看到控制台出现:WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:firstProject' did not find a matching property. 这样的字样,说的是server.xml的Service标签里的Engine标签里的Host标签里的Co

tomcat警告:Setting property 'source' to 'org.eclipse.jst.j2ee.server:ServletPro' did not find a matching property

警告: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.j2ee.server:ServletPro' did not find a matching property. 原因:这是因为我们在eclipse下,通过tomcat部署web工程时,tomcat的配置文件server.xml中会自动生成一个关于该web工程的配置信息,类似于下面的东