Skip to main content

Create your own VMs - I

LXC(Linux Containers:http://en.wikipedia.org/wiki/LXC) is a virtualization technique which provides os and network stack level isolation. It allows to run multiple OS distros on a host machine with isolated process listings, user groups, ip addressing. The only constraint is all  these containers and host machines should use same kernel(http://en.wikipedia.org/wiki/Linux_kernel). It make use of cgroups, a new feature addition to latest linux kernels.

What is cgroup
Cgroup associates each task to a subsystem and the subsystem allocates resources shared fro host machine. One can even control amount of resources by passing them as parameter. There can be heirarchy of cgroups i.e cgroups within cgroups(in precise vm within vm)
Have a look at http://www.kernel.org/doc/Documentation/cgroups/cgroups.txt to get a taste of cgroup

Create our VM
This works without any issue in Ubuntu host.
1)install lxc
2)create a mount point for vms

    mkdir -p /cgroup

    mount none -t cgroup /cgroup

3)create network bridges
   Refer http://blogs.eskratch.com/2012/10/bridging-interfaces.html
4)Create your vm

   lxc-create -n <name for vm> -t ubuntu -f /usr/share/doc/lxc/examples/lxc-veth.conf

where -t specifies os templates
os templates are available at /usr/lib/lxc/templates/. Have a look at them and try to understand how devices are shared between host system and containers.
-f specifies the config file (here for network ip assignment ). To understand different network options available, have a look at http://blog.flameeyes.eu/2010/09/linux-containers-and-networking
5)The previous command should have created a vm. Check using

  lxc-ls

6)Start the VM using

    lxc-start -n <name of the vm>

This will take some time to boot. Then once the console appears, it prompts for username, password. For each OS, the template will have username password as variables(For eg ubuntu template assigns username and password to be ubuntu).

LXC and Ubuntu Connection:
Ubuntu's 12.04 release has fixed most of the common bugs of lxc and have created security policies to avoid collision between containers and host while sharing resources.

For CentOs geeks:
CentOS 6.x supports lxc and cgroup. Lesser than 6.x, its impossible to have isolations.
1) Download lxc-0.7.5 source from http://lxc.sourceforge.net/download/lxc/
2)Do a manual install
   Ref http://wiki.centos.org/PackageManagement/SourceInstalls
3)Centos has lot of issues with lxc. I tried fixing some of them with patches available
Download centos container template from https://github.com/kalyanceg/lxc-centos
4)Keep the tar file in /var/cache/lxc and the lxc-centos file in /usr/local/lib/lxc/templates/
5)Create the vm using
/usr/local/bin/lxc-create -n <name of vm> -t centos -f {lxc_source_path}/doc/examples/veth.conf
6)Start vm
/usr/local/bin/lxc-start -n <name of vm>

Comments

Popular posts from this blog

Lessons from Memory

Started debugging an issue where Linux started calling OOM reaper despite tons of memory is used as Linux cached pages. My assumption was if there is a memory pressure, cache should shrink and leave way for the application to use. This is the documented and expected behavior. OOM reaper is called when few number of times page allocation has failed consequently. If for example mysql wants to grow its buffer and it asks for a page allocation and if the page allocation fails repeatedly, kernel invokes oom reaper. OOM reaper won't move out pages, it sleeps for some time and sees if kswapd or a program has freed up caches/application pages. If not it will start doing the dirty job of killing applications and freeing up memory. In our mysql setup, mysql is the application using most of the Used Memory, so no other application can free up memory for mysql to use. Cached pages are stored as 2 lists in Linux kernel viz active and inactive.
More details here
https://www.kernel.org/doc/gorman…

How we have systematically improved the roads our packets travel to help data imports and exports flourish

This blog post is an account of how we have toiled over the years to improve the throughput of our interDC tunnels. I joined this company around 2012. We were scaling aggressively then. We quickly expanded to 4 DCs with a mixture of AWS and colocation. Our primary DC is connected to all these new DCs via IPSEC tunnels established from SRX. The SRX model we had, had an IPSEC throughput of 350Mbps. Around December 2015 we saturated the SRX. Buying SRX was an option on the table. Buying one with 2Gbps throughput would have cut the story short. The tech team didn't see it happening.

I don't have an answer to the question, "Is it worth spending time in solving a problem if a solution is already available out of box?" This project helped us in improving our critical thinking and in experiencing the theoretical network fundamentals on live traffic, but also caused us quite a bit of fatigue due to management overhead. Cutting short the philosophy, lets jump to the story.

De…

Walking down the Memory Lane!!!

This post is going to be an account of  few trouble-shootings I did recently to combat various I/O sluggishness.
Slow system during problems with backup
We have a NFS mount where we push backups of our database daily. Due to some update to the NFS infra, we started seeing throughput of NFS server drastically affected. During this time we saw general sluggishness in the system during backups. Even ssh logins appeared slower. Some boxes had to be rebooted due to this sluggishness as they were too slow to operate on them. First question we wanted to answer, does NFS keep writing if the server is slow? The slow server applied back pressure by sending small advertised window(TCP) to clients. So clients can't push huge writes if server is affected. Client writes to its page cache. The data from page cache is pushed to server when there is a memory pressure or file close is called. If server is slow, client can easily reach upto dirty_background_ratio set for page cache in sysctl. This di…