Hi all,
I am using proxmox since a couple of months without any issues. Thanks to all of those involved in proxmox !!!!!!
Yesterday I found an issue with my openvz servers running on ubuntu 9.10. My server was rebooted due to a power failure. After that I couldn't reach some of the ubuntu vps anymore. After some investigation i found out that the issue is related to the network interface. The output from ifconfig is empty
after starting the network stack its working again
Does anybody can help me to solve this issue?
I found this https://bugs.launchpad.net/openvz-kernel/+bug/436130 Comment 44 ff
But this doesn't helped me. I copied the openvz.conf into the openVZ instance server104 /etc/init/openvz.conf.
Update: This happens only to karmic after an apt-get update. Its fine when running with the default template without any changes.
BR
Mr.X
I am using proxmox since a couple of months without any issues. Thanks to all of those involved in proxmox !!!!!!
Yesterday I found an issue with my openvz servers running on ubuntu 9.10. My server was rebooted due to a power failure. After that I couldn't reach some of the ubuntu vps anymore. After some investigation i found out that the issue is related to the network interface. The output from ifconfig is empty
Code:
siproxmox2:~# vzctl start 104
Starting container ...
Container is unmounted
Container is mounted
Adding IP address(es): 217.X.Y.56
Setting CPU units: 1000
Setting CPUs: 1
Set hostname: server104.test.net
File resolv.conf was modified
Setting quota ugidlimit: 0
Container start in progress...
siproxmox2:~# vzctl enter 104
entered into CT 104
root@user:/# ifconfig
root@user:/#
Code:
root@server104:/# start networking
networking stop/waiting
root@server104:/# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:300 (300.0 B) TX bytes:300 (300.0 B)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:217.X.Y.56 P-t-P:217.146.147.56 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1I found this https://bugs.launchpad.net/openvz-kernel/+bug/436130 Comment 44 ff
But this doesn't helped me. I copied the openvz.conf into the openVZ instance server104 /etc/init/openvz.conf.
Update: This happens only to karmic after an apt-get update. Its fine when running with the default template without any changes.
BR
Mr.X
