On Fri, Aug 24, 2012 at 7:00 PM, Fajar A. Nugraha <[email protected]> wrote:
>> Aren't the default templates supposed to work with the default config file?
>
> It should. Which is why I thought you edit the config file. Try:
> - adding lxc.network.veth.pair=test-e0
No change.
> - run "ip link show" on the host, and for every interface that starts
> with a "veth", do "ip link del" on that interface. That is, assuming
> you don't currently have any containers or anything that uses veth
> running.
There are no veth's:
$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 00:25:22:2f:b9:40 brd ff:ff:ff:ff:ff:ff
4: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
52: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> - try the second link, which create the rootfs and config file by hand
> instead of using a script.
Well, foo. I need to end up with a debugged script, and I was hoping
that since lxc-create -t centos had worked for someone recently
(and lxc-create -t fedora works for me now), success wouldn't be far off.
I guess I'll try to understand lxc-start more.
- Dan
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Lxc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxc-users
