From: sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: Kir Kolyshkin <kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Masahiko Takahashi <masahiko-3NddpPZAyC0@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Pavel Emelianov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Subject: Re: [DRAFT] Container mini-summit notes v0.01
Date: Wed, 17 Oct 2007 17:52:16 -0700 [thread overview]
Message-ID: <20071018005216.GA916@us.ibm.com> (raw)
In-Reply-To: <46FABD9D.50407-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Oren Laadan [orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org] wrote:
|
| (sorry from the delay, been away :)
|
| Eric W. Biederman wrote:
| > "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> writes:
| >
| >> Sorry, I was focusing on the virtual server needs.
| >>
| >> devpts is it's own fs so I was fully expecting to make it mountable
| >> multiple times so a container can have it's own /dev/pts/0. So what
| >> other virtual devices would we want to be able to rec-reate for a
| >> migrated application? (I wonder (a) what gregkh will say about having
| >> a device namespace, and (b) what the sysfs implications will be)
| >
| > Depends. There are things like the loop device that could be interesting.
| > There may be some others. I haven't looked at it enough detail to get
| > beyond the fact that in some sense it isn't just limited to pts devices.
| >
| > A multimount devpts is interesting though.
|
| Devices I had to deal with (in zap) so far - to be able to ckpt/restart
| (and migrate) a desktop session:
|
| * /dev/rtc (e.g. for mplayer)
|
| * /dev/dsp
|
| * /dev/random ? (to isolate entropy pools ?)
|
| * virtual consoles - e.g. in zap, an X server that uses a virtual device
| runs inside a pod/container/VE (and X per-se requires a virtual console)
|
| * virtual terminals - e.g. in zap we allow access to a pod from the host
| without a need to run 'sshd' inside and setup a network in the pod. (Then
| with a suitable utility and network access to the host, this also allows
| sort of remote (a-la serial) console access).
| >From inside the pod it looks like /dev/tty{1,2,..}, so one can run 'getty'
| processes inside the pod. From the outside (for the admin, e.g.) it is an
| extended /dev/tty that has an extra ioctl to multiplex access, so the
| admin (program) can ask to be connected to tty X of pod Y, and it will
| connect to that console (like connecting via serial line).
This sounds really interesting. Were these devices part of a complete
device namespace ? IOW, does say /dev/tty2 in each pods have the same
major/minor number (4,2) ? Does each '/dev/tty2' have a separate entry
in sysfs ?
| The main advantage is that as a virtual device it can be migrated (with
| its buffers, if not empty, as they reside inside the pod) so upon restart
| they go with the 'getty' processes that use them. The (old) admin will
| see the line dropped, and the (new) admin after the migration can connect
| at the new machine.
|
| Oren.
|
|
| _______________________________________________
| Containers mailing list
| Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
| https://lists.linux-foundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2007-10-18 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46DE9E1C.6010309@fr.ibm.com>
[not found] ` <46DEEBED.5010303@openvz.org>
[not found] ` <46DEEBED.5010303-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-09-06 11:22 ` [DRAFT] Container mini-summit notes v0.01 Cedric Le Goater
[not found] ` <46DFE2E3.20003-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-09-06 12:00 ` Kirill Korotaev
[not found] ` <20070905135357.GE1403@sergelap.austin.ibm.com>
[not found] ` <6599ad830709050700y278d653eu371375c2fc107ef@mail.gmail.com>
[not found] ` <20070905143808.GG1403@sergelap.austin.ibm.com>
[not found] ` <46DF35DA.1090102@cs.columbia.edu>
[not found] ` <20070905235828.GA32475@sergelap.austin.ibm.com>
[not found] ` <46DFBE60.6030404@fr.ibm.com>
[not found] ` <20070906153243.GA15436@sergelap.austin.ibm.com>
[not found] ` <20070906153243.GA15436-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-09-08 20:26 ` Eric W. Biederman
[not found] ` <m1wsv0x5sv.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-09-10 14:18 ` Serge E. Hallyn
[not found] ` <20070910141834.GA5866-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-09-10 16:09 ` Eric W. Biederman
[not found] ` <m1642iqz6x.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-09-26 20:14 ` Oren Laadan
[not found] ` <46FABD9D.50407-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2007-10-18 0:52 ` sukadev-r/Jw6+rmf7HQT0dZR+AlfA [this message]
[not found] ` <20071018005216.GA916-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-10-30 4:35 ` Oren Laadan
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=20071018005216.GA916@us.ibm.com \
--to=sukadev-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=masahiko-3NddpPZAyC0@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org \
--cc=xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox