On Wed 2011-10-19 (22:11), Papp Tamas wrote:
> What version of lxc package do you use?
See my first mail:
lxc version: 0.7.4.1
--
Ullrich Horlacher Server- und Arbeitsplatzsysteme
Rechenzentrum E-Mail: horlac...@rus.uni-stuttgart.de
Universitaet Stuttgart
On 10/19/2011 09:28 PM, Ulli Horlacher wrote:
> On Wed 2011-10-19 (21:24), Papp Tamas wrote:
>> On 10/19/2011 09:18 PM, Ulli Horlacher wrote:
>>
>>> root@vms1:/lxc# ps axf | grep vmtest1
>>> 31571 ?Ds 0:00 lxc-start -f /data/lxc/vmtest1.cfg -n vmtest1 -d
>>> -o /data/lxc/vmtest1.log
>>
On Wed 2011-10-19 (21:24), Papp Tamas wrote:
> On 10/19/2011 09:18 PM, Ulli Horlacher wrote:
>
> > root@vms1:/lxc# ps axf | grep vmtest1
> > 31571 ?Ds 0:00 lxc-start -f /data/lxc/vmtest1.cfg -n vmtest1 -d
> > -o /data/lxc/vmtest1.log
> > 2171 ?Ds 0:00 lxc-start -f /data/
On 10/19/2011 09:18 PM, Ulli Horlacher wrote:
> root@vms1:/lxc# ps axf | grep vmtest1
> 31571 ?Ds 0:00 lxc-start -f /data/lxc/vmtest1.cfg -n vmtest1 -d
> -o /data/lxc/vmtest1.log
> 2171 ?Ds 0:00 lxc-start -f /data/lxc/vmtest1.cfg -n vmtest1 -l
> DEBUG -d -o /data/lxc/vmt
On Wed 2011-10-19 (13:49), Brian K. White wrote:
> I haven't scrutinized your info in detail but one quick question, did
> you have vsftpd running in the containers
No. I have no ftp-service running at all.
> If you change the name of the container it will create a new cgroup
> based on the
On Wed 2011-10-19 (19:37), Papp Tamas wrote:
> > Besides my problem with "cannot stop/kill lxc-start" (see other mail), I
> > have now an even more severe problem: I cannot start ANY container anymore!
> >
> > I boot the container with:
> >
> > root@vms1:/lxc# lxc-start -f /data/lxc/vmtest1.cfg -n
On Wed, Oct 19, 2011 at 10:51 AM, Robert Pendell
wrote:
> On Wed, Oct 19, 2011 at 3:01 AM, Papp Tamas wrote:
>> On 10/19/2011 12:36 AM, Derek Simkowiak wrote:
>>
>>> But actually I think, lxc-virt.org sounds better.
>>
>> I disagree with lxc-virt.org.
>>
>> The difference between "contain
fedora 13 / Linux 2.6.34
I tried to create an sshd container, but received an error when I try
to start it:
lxc-create -n sshd -t sshd
...
# lxc-start -n sshd
/usr/local/lib/lxc/lxc-init is /usr/local/lib/lxc/lxc-init
sshd is /usr/sbin/sshd
lxc-init: Read-only file system - failed to create '/de
On 10/19/2011 1:24 PM, Ulli Horlacher wrote:
> Besides my problem with "cannot stop/kill lxc-start" (see other mail), I
> have now an even more severe problem: I cannot start ANY container anymore!
>
> I am sure I have overlooked something, but I cannot see what. I am really
> desperate now, becaus
On 10/19/2011 07:24 PM, Ulli Horlacher wrote:
> Besides my problem with "cannot stop/kill lxc-start" (see other mail), I
> have now an even more severe problem: I cannot start ANY container anymore!
>
> I am sure I have overlooked something, but I cannot see what. I am really
> desperate now, becau
On 10/18/2011 7:31 PM, Derek Simkowiak wrote:
> That MAC address has nothing to do with the bug; the host's bridge
> device (br0) will never assume a configured LXC MAC address as its own.
> Instead, the MAC address in question is the one of the virtual veth
> device, as shown with "ifco
Besides my problem with "cannot stop/kill lxc-start" (see other mail), I
have now an even more severe problem: I cannot start ANY container anymore!
I am sure I have overlooked something, but I cannot see what. I am really
desperate now, because this happens to my production environment!
Server h
I have some lxc-start processes which I cannot stop or kill:
root@vms2:/lxc# psg bunny
USER PID PPID %CPUVSZ COMMAND
root 27033 1 0.0 20872 lxc-start -f /data/lxc/bunny.cfg -n bunny -d
-o /data/lxc/bunny.log
root 26620 1 0.0 20872 lxc-start -f /data/lxc/bunny.cfg
On Wed, Oct 19, 2011 at 3:01 AM, Papp Tamas wrote:
> On 10/19/2011 12:36 AM, Derek Simkowiak wrote:
>
>> But actually I think, lxc-virt.org sounds better.
>
> I disagree with lxc-virt.org.
>
> The difference between "container" and "virtual machine" is already
> confusing enough. There is
Hello,
thanks for your answere. Of course I had allowed video devices for my
container, that was not the problem. I could use it with any programm which
i can give a parameter to use the specific video device.
i found a solution. i think it was the missing /dev/bus folder but i will
look into my
Hello,
i have one folder with two sub folders including nfs mounts.
/data/nfs_mount{1,2}
lxc config file:
...
lxc.mount.entry=/data /var/lib/lxc/trinity/rootfs/data none bind 0 0
...
In the container i can see the two folders but not the underlying nfs
mounts. I have mounted both nfs bevor star
On 10/19/2011 12:36 AM, Derek Simkowiak wrote:
> /But actually I think, lxc-virt.org sounds better./
I disagree with lxc-virt.org.
The difference between "container" and "virtual machine" is
already confusing enough. There is no virtualization layer in LXC, so
I don't think "virt" sh
>> 4. Which signal? SIGINT? SIGPWR? Both?
>
>Does only work for init based systems, not for upstart, like Ubuntu!
Dear Derek,
Sending a SIGINT to init will invoke the alsctrldel entry of the /etc/inittab
. A SIGPWR will (in absence of /etc/powerfail) call the powerfail entry. In a
common s
18 matches
Mail list logo
