Ok, it seems like in one of the upgrades there was a broken dependency.
ifupdown package was removed in the process and after reboot it was not able
to start network interfaces properly
This issue is not vserver related.
On May 17, 2012, at 12:42 PM, John A. Sullivan III wrote:
> On Thu, 2012-05-17 at 12:30 +0200, Tomasz Pajor wrote:
>> I noticed that you added new kernel version.
>> 3.2.17-vs2.3.2.9-beng
>> and util-vserver is upgraded to 0.30.216-pre3034-squeeze0.2-1
>>
>> I'm experiencing a strange situation.
>>
>> After restart my main interfaces ip gets overwritten with one
>> from a vserver.
>>
>> When i turn vservers off, eth0 is not even up.
>>
>> When i switch eth0 up by hand and start vservers, everything works
>> properly.
>>
>> Have anybody experienced this situation?
>>
> <snip>
> Did anything else change? I have not experienced it myself but I recall
> a note in the VServer documentation that, if a guest has the same IP
> address as the host, stopping the guest will also remove the address
> from the host. Not 100% sure though and I don't know if removing the
> last address would down the interface - John
>
Received on Thu May 17 12:11:14 2012