On 07/22/2010 10:08 PM, Ferenc Wagner wrote: > Daniel Lezcano<dlezc...@fr.ibm.com> writes: > > >> On 07/22/2010 09:44 PM, Ferenc Wagner wrote: >> >> >>> # lxc-execute --name net -s lxc.network.type=phys -s lxc.network.link=eth0 >>> bash >>> lxc-execute: failed to move 'eth0' to the container : Message too long >>> >>> It might as well have some sense, but I definitely don't get it this >>> late. :) I give up now. >>> >> I think the error is wrong, perhaps the kernel is returning a wrong >> value or there is a bad error catch in lxc. But I think the problem >> may come from the kernel version< 2.6.35 because it does not support >> physical interface moving across namespace. Is it a kernel< 2.6.35 ? >> > Yes, it's 2.6.32. In my opinion a more sensible error message would be > nice, even if this is what the kernel reports. >
Fixed that was a bad error catch. It returns EINVAL now. I would have be happy to show a nicer message but the error is too deep in the code in a generic netlink layer. Fixed the core dump too. Thanks Ferenc for reporting this -- Daniel ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
