Thanks for your reply, i finally figured out why my libtool version is not correct. I am using libuv as a dependency(via git submodule) of my another autotools project, libuv is located on myproject/deps/libuv.It seems that my project's build system has. X11 client-side library (development headers) This package provides a client interface to the X Window System, otherwise known as 'Xlib'. It provides a complete.Published on 27 Nov 2013 · Filed in Tutorial · 556 words (estimated 3 minutes to read)
One of the cool things about libvirt is the ability to work with multiple hypervisors and virtualization technologies, including Linux containers using LXC. In this post, I’m going to show you how to use libvirt with LXC, including leveraging libvirt to help automate attaching containers to Open vSwitch (OVS).
If you aren’t familiar with Linux containers and LXC, I invite you to have a look at my introductory post on Linux containers and LXC. It should give you enough background to make this post make sense.
To use libvirt with an LXC container, there are a couple of basic steps:
Create the container using standard LXC user-space tools.
Create a libvirt XML definition for the container.
Define the libvirt container domain.
Start the libvirt container domain.
Mustang amplifier driver. The first part, creating the container, is pretty straightforward:
This creates a container using the Ubuntu template and calls it
cn-01. As you may recall from my introductory LXC post, this creates the container’s configuration and root filesystem in
/var/lib/lxc by default. (I’m assuming you are using Ubuntu 12.04 LTS, as I am.)
Once you have the container created, you next need to get it into libvirt. Libvirt uses a standard XML-based format for defining VMs, containers, networks, etc. At first, I thought this might be the most difficult section, but thanks to this page I was able to create a template XML configuration. I’ve uploaded this template XML configuration to GitHub as a gist, which you can view here.
Simply take this XML template and save it as something like
lxc-template.xml or similar. Then, after you’ve created your container using
lxc-create as above, you can easily take this template and turn it into a specific container configuration with only one command. For example, suppose you created a container named “cn-02” (as I did with the command I showed earlier). If you wanted to customize the XML template, just use this simple Unix/Linux command:
Once you have a container-specific libvirt XML configuration, then defining it in libvirt is super-easy:
Then start the container:
And connect to the container’s console:
When you’re done with the container’s console, press “Ctrl-]” (that’s Control and right bracket at the same time); that will return you to your host.
Pretty handy, eh? Further, since you’re now controlling your containers via libvirt, you can leverage libvirt’s networking functionality as well—which means that you can easily create libvirt virtual networks backed by OVS and automatically attach containers to OVS for advanced networking configurations. You only need to create an OVS-backed virtual network like I describe in this post on VLANs with OVS and libvirt.
I still need to do some additional investigation and testing to see how the networking configuration in the container’s
config file interacts with the networking configuration in the libvirt XML file. For example, how do you define multiple network interfaces? Can you control the name of the veth pairs that show up in the host? I don’t have any answers for these questions (yet). If you know the answers, feel free to speak up in the comments!
All courteous feedback and interaction is welcome, so I invite you to start (or join) the discussion via the comments below.
Metadata and Navigation
Be social and share this post!
- LXC, Open vSwitch, and GRE Tunnels26 Nov 2013
- Using GRE Tunnels with Open vSwitch7 May 2013
- Libvirt-OVS Integration Revisited12 Nov 2012
Links for libxt-dev
Download Source Package libxt:
- Ubuntu Core Developers (Mail Archive)
Please consider filing a bug or asking a question via Launchpad before contacting the maintainer directly.
Original Maintainers (usually from Debian):
- Debian X Strike Force (Mail Archive)
- Cyril Brulebois
It should generally not be necessary for users to contact the original maintainer.
X11 toolkit intrinsics library (development headers)
Other Packages Related to libxt-dev
- X11 Session Management library (development headers)
- X11 client-side library (development headers)
- dep:libxt6 (= 1:1.1.5-0ubuntu1)
- X11 toolkit intrinsics library
- X11 core wire protocol and auxiliary headers
- X11 toolkit intrinsics library (documentation)
|Architecture||Package Size||Installed Size||Files|
|amd64||384.4 kB||1,189.0 kB||[list of files]|
|arm64||365.0 kB||1,173.0 kB||[list of files]|
|armhf||358.8 kB||914.0 kB||[list of files]|
|i386||385.3 kB||1,042.0 kB||[list of files]|
|powerpc||363.0 kB||1,060.0 kB||[list of files]|
|ppc64el||396.2 kB||1,429.0 kB||[list of files]|
|s390x||377.6 kB||1,393.0 kB||[list of files]|