> Well, "fixed" is not fair as it implies anything was ever broken. > > LXC never claimed to provide a virtual reboot function in the first place. > LXC is in many ways like chroot. And just like chroot, it's a low level > tool that you build fancier things on top of. It runs processes in a > namespace. It is not a full virtual hardware system like vmware. You > build the fancier higher level stuff on top of that yourself, such as > modifying the container init scripts fairly heavily to remove or modify > the stuff that does not work or makes no sense in the context of a > container. There is no boot loader or kernel or kernel modules for > instance, so any init scripts that deal with those need to be removed or > short circuited. And it's not lxc's job to do that, you have to. > Arranging for the host system to stop & restart a container when the > container requested a reboot was like that. > > Now LXC ships with a reboot service which is a great convenience and > improvement, but it's not fair to to LXC to call this a fix. >
I disagree. Trying to migrate from openvz (which has a working reboot/shutdown inside the guest) to lxc this was one of the show stopper bugs / features that prevented me from using lxc in a production environment to replace openvz. John ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
