Re: LXC: autostart feature does set all interfaces to state up.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 18.07.2013 16:50, schrieb Jim Fehlig:
> Richard,
> 
> I think you should have cc'd the bug assignee when discussing this issue
> upstream.  Adding him now...

Oh, sorry for that!
I thought I did so after pointing Marius to the thread in the mailing list archive,
but obviously I forgot.

Thanks,
//richard

> Regards,
> Jim
> 
> 
> Daniel P. Berrange wrote:
>> On Wed, Jul 17, 2013 at 11:33:22PM +0200, Richard Weinberger wrote:
>>   
>>> Am 12.07.2013 03:36, schrieb Gao feng:
>>>     
>>>> On 07/11/2013 07:58 PM, Richard Weinberger wrote:
>>>>       
>>>>> Am 11.07.2013 11:49, schrieb Daniel P. Berrange:
>>>>>         
>>>>>> On Thu, Jul 11, 2013 at 11:44:48AM +0200, Richard Weinberger wrote:
>>>>>>           
>>>>>>> Am 11.07.2013 11:42, schrieb Gao feng:
>>>>>>>             
>>>>>>>> On 07/11/2013 03:18 PM, Richard Weinberger wrote:
>>>>>>>>               
>>>>>>>>> This morning I've installed a wrapper around ip to show me the process tree upon ip link ... down is used.
>>>>>>>>> The log showed this:
>>>>>>>>>
>>>>>>>>>   769 ?        Ss     0:00 /usr/lib/systemd/systemd-udevd
>>>>>>>>> 17759 ?        S      0:00  \_ /usr/lib/systemd/systemd-udevd
>>>>>>>>> 17764 ?        S      0:00  \_ /usr/lib/systemd/systemd-udevd
>>>>>>>>> 17772 ?        S      0:00  \_ /usr/lib/systemd/systemd-udevd
>>>>>>>>> 19477 ?        S      0:00  |   \_ /bin/bash /sbin/ifdown veth5 -o hotplug
>>>>>>>>> 19910 ?        S      0:00  |       \_ /sbin/ip link set dev veth5 down
>>>>>>>>>
>>>>>>>>> Now I have to urge to use a "Kantholz". ;-)
>>>>>>>>>
>>>>>>>>>                 
>>>>>>>> hmmm...
>>>>>>>>
>>>>>>>> it's systemd... I have no idea now... :(
>>>>>>>>               
>>>>>>> TBH it is not systemd's fault.
>>>>>>> OpenSUSE's /usr/lib/udev/rules.d/77-network.rules did not white list veth* devices.
>>>>>>> Therefore systemd-udevd called ifup/down and other hotplug magic.
>>>>>>>             
>>>>>> Ah ha, that's a nice issue :-) I assume you've filed a bug against opensuse
>>>>>> to fix this ? Can you post a link to the bug here for the sake of archive
>>>>>> records.
>>>>>>           
>>>>> Sure:
>>>>> https://bugzilla.novell.com/show_bug.cgi?id=829033
>>>>>
>>>>>         
>>>> It's good news we know what causes veth device down. :)
>>>>       
>>> How does Fedora deal with veth devices?
>>>     
>>
>> Well the udev script you mention above does not exist on Fedora and AFAIK
>> there's no other udev script which runs 'ifconfig down' on NICs.
>>
>>   
>>> SUSE folks think that this is a more likely a libvirt issue and closed my bug report as invalid...
>>>     
>>
>> If you remove or modify the 77-network.rules file does it fix the problem.
>> If so, then it is obviously not a libvirt issue.  IMHO it is completely
>> bogus for udev to be arbitrarily ifdown'ing any interface.
>>
>> Daniel
>>   

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]