On 06/01/2011 07:26 AM, Mihamina Rakotomandimby wrote:
Hi all,
When I create a container, I usually created it with only one NIC:
[...]
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.ipv4 = 41.204.96.2/28
lxc.network.name = eth0
After a minor kernel update lxc-start does not work any more:
root@vms2:/lxc# lxc-start -f bunny.cfg -n bunny -d -o /dev/tty
lxc-start 1306913218.901 ERRORlxc_namespace - failed to
clone(0x6c02): Invalid argument
lxc-start 1306913218.901 ERRORlxc_start - Invalid argument
On 06/01/2011 10:25 AM, Ulli Horlacher wrote:
On Wed 2011-06-01 (10:18), Daniel Lezcano wrote:
root@vms2:/lxc# lxc-start -f bunny.cfg -n bunny -d -o /dev/tty
lxc-start 1306913218.901 ERRORlxc_namespace - failed to
clone(0x6c02): Invalid argument
Can you show the content of
On Wed 2011-06-01 (10:30), Daniel Lezcano wrote:
On 06/01/2011 10:25 AM, Ulli Horlacher wrote:
On Wed 2011-06-01 (10:18), Daniel Lezcano wrote:
root@vms2:/lxc# lxc-start -f bunny.cfg -n bunny -d -o /dev/tty
lxc-start 1306913218.901 ERRORlxc_namespace - failed to
On 06/01/2011 10:45 AM, Ulli Horlacher wrote:
[ ... ]
2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous mode
2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5: link is
not ready
This is strange, because I have not configured vetheBqcj5.
It is
On 06/01/2011 11:17 AM, Daniel Lezcano wrote:
On 06/01/2011 10:45 AM, Ulli Horlacher wrote:
[ ... ]
2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous mode
2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5: link is
not ready
This is strange, because
On Wed 2011-06-01 (11:17), Daniel Lezcano wrote:
On 06/01/2011 10:45 AM, Ulli Horlacher wrote:
[ ... ]
2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous
mode
2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5: link is
not ready
This is
Hi,
Can you reboot on console by lxc-console in a container?
HostOS: Ubuntu natty
lxc version: 0.7.4-0ubuntu7.1
I make a natty container on natty host.
# lxc-create -t natty -n natty01
I start the container, and run lxc-console, then run reboot on the console.
# lxc-start -n natty01 -d
On 06/01/2011 11:55 AM, Papp Tamas wrote:
On 06/01/2011 11:17 AM, Daniel Lezcano wrote:
On 06/01/2011 10:45 AM, Ulli Horlacher wrote:
[ ... ]
2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous
mode
2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP): vetheBqcj5:
On 06/01/2011 12:25 PM, Ulli Horlacher wrote:
On Wed 2011-06-01 (11:17), Daniel Lezcano wrote:
On 06/01/2011 10:45 AM, Ulli Horlacher wrote:
[ ... ]
2011-06-01 10:34:53 [ 5228.816214] device vetheBqcj5 entered promiscuous
mode
2011-06-01 10:34:53 [ 5228.817240] ADDRCONF(NETDEV_UP):
On 06/01/2011 03:06 PM, Ulli Horlacher wrote:
On Wed 2011-06-01 (14:40), Daniel Lezcano wrote:
root@vms2:~# lxc-checkconfig
Kernel config /proc/config.gz not found, looking in other places...
Found kernel config file /boot/config-2.6.32-32-server
--- Namespaces ---
Namespaces: enabled
On 06/01/2011 12:33 PM, KATOH Yasufumi wrote:
Hi,
Can you reboot on console by lxc-console in a container?
HostOS: Ubuntu natty
lxc version: 0.7.4-0ubuntu7.1
Good catch, thanks for reporting !
Fixed with this patch.
Index: lxc/src/lxc/commands.c
Hey guys!
I know, I know... This is like 9 months old. But I finally got caught
between a rock and a hard place on Fedora 15 and was researching that
problem (which others have pointed good pointers to on this list - thank
you very much - got me going again) and I kept constantly running into
On Fri, 2011-05-13 at 22:32 +0200, Daniel Lezcano wrote:
From: Daniel Lezcano daniel.lezc...@free.fr
We ignore the line of in the configuration file not beginning by lxc.
So we can mix the configuration file with another information used for
another component through the lxc library.
Wow...
14 matches
Mail list logo