All of lore.kernel.org
 help / color / mirror / Atom feed
From: mkatiyar@gmail.com (Manish Katiyar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel development using linux containers (LXC ) ?
Date: Wed, 29 Jul 2015 13:23:18 -0700	[thread overview]
Message-ID: <CAE0An6fJje+q++Dx=OtX7Lu-j15aEOh=igyrRu+2XC4MafUcag@mail.gmail.com> (raw)
In-Reply-To: <4E5779AD88B2F040B8A7E83ECF544D1A61365D@SJCPEX01CL03.citrite.net>

On Wed, Jul 29, 2015 at 1:07 PM, Jeff Haran <Jeff.Haran@citrix.com> wrote:
>>-----Original Message-----
>>From: kernelnewbies-bounces at kernelnewbies.org [mailto:kernelnewbies-
>>bounces at kernelnewbies.org] On Behalf Of Manish Katiyar
>>Sent: Wednesday, July 29, 2015 11:51 AM
>>To: kernelnewbies
>>Subject: Kernel development using linux containers (LXC ) ?
>>
>>Hi,
>>
>>I've been playing and reading about control groups and linux containers
>>recently and was wondering if there are any existing recipes on how to setup
>>a kernel environment in containers. Google hasn't been helpful so far (or
>>maybe I'm not searching properly).
>>
>>I've used VMs for dev in past (Qemu, uml etc.), but looks like it may be
>>interesting to have it in containers. Given that they share they same OS image
>>as host, I'm not sure if its possible without making the host OS crash.
>>
>>Any suggestions.
>>
>>Thanks -
>>Manish
>
> I'm not sure what your goal is here, but it sounds to me like you might want to be googling for "linux namespaces".

I'm sorry. I see that my previous mail had a key word "development"
missing. What I was trying to find out was that is it possible to
setup and use linux containers/cgroups to do kernel development.
Things like writing and test kernel modules, debugging kernel,
attaching gdb etc. etc. which normally require Qemu, busybox or other
VM techniques since containers are much lightweight and if anyone has
recipes for that setup to do development without crashing the host OS.

Any hints appreciated. I looked for "linux namespaces" but it doesn't
give me what I want.

  reply	other threads:[~2015-07-29 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 18:50 Kernel development using linux containers (LXC ) ? Manish Katiyar
2015-07-29 20:07 ` Jeff Haran
2015-07-29 20:23   ` Manish Katiyar [this message]
2015-07-29 20:35     ` Greg KH
2015-07-29 20:49     ` Greg Freemyer
2015-07-29 21:03       ` Manish Katiyar
2015-07-30 12:47         ` Grzegorz Dwornicki
     [not found]           ` <55BA1D1C.2010500@gmail.com>
     [not found]             ` <CAOP-CUfXgbh94WeUGLhL4v=0FaGd7nre50NN4YgTcecvpVnPtg@mail.gmail.com>
     [not found]               ` <55BA2EBD.7000800@gmail.com>
2015-07-30 14:09                 ` Grzegorz Dwornicki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE0An6fJje+q++Dx=OtX7Lu-j15aEOh=igyrRu+2XC4MafUcag@mail.gmail.com' \
    --to=mkatiyar@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.