On 09/13/2010 01:23 PM, Ralf Schmitt wrote: > <daniel.lezc...@free.fr> writes: > >> From: Daniel Lezcano<daniel.lezc...@free.fr> >> >> When a container is installed with 32bits binaries while we are >> running on a 64bits host, inside the container we are seen as >> 64bits arch. That leads to some problems for the package updates >> because the scripts will download 64bits packages instead of 32bits. >> >> This patch defines a configuration variable to set the architecture >> of the container. >> >> lxc.arch = i686 | x86 | x86_64 | amd64 >> > > Thanks. It mostly works. Setting the arch from x86 to x86 doesn't work > though: > > ,---- > | [local] ~/ # linux32 lxc-start -n g32 > | lxc-start: Device or resource busy - failed to set personality to '0x8 > | lxc-start: failed to setup personality > | lxc-start: failed to setup the container > | lxc-start: invalid sequence number 1. expected 2 > | lxc-start: failed to spawn 'g32' > | lxc-start: Device or resource busy - failed to remove cgroup '/cgroup/g32' > `---- > > Without the linux32 in front, the container does start and changes it > personality successfully.
Fixed and commited. -- Daniel ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
