Search results

@udo Nothing is physically connected to vmbr0 (IP address 10.0.0.1). When proxmox 3 was installed on this NODE, the proxmox network settings were configured so that the openvz containers would use a BRIDGED connection to the NODE NIC on eth0 (192.168.0.100). So, the containers would each have...

Good idea @udo Here's the "brctl show" command output: root@NODE:~# brctl show bridge name bridge id STP enabled interfaces vmbr0 8000.000000000000 no Here's another command "service networking reload" notice how it gives interesting error information...

@udo 3. Here's the NODE "ip route" output: root@NODE:~# ip route 192.168.1.114 dev venet0 scope link 10.0.0.0/24 dev vmbr0 proto kernel scope link src 10.0.0.1 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 default via 192.168.0.1 dev eth0 4. And here's the...

Ahoy @udo ! 1. Here's the "iptables" config on node: root@NODE:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt...

Help. I have proxmox 3 running on a bare metal machine. The 65GB OpenVZ container cannot reach the internet, DNS serves are configured right, During debian upgrade (not sure), something changed the network config of the containers, possibly the bridge, venet, or vmbr0 ?! Whatever happened...

Help. Same machine, the openvz containers cannot reach the internet, DNS serves are configured right, yet during debian upgrade it appears something changed the network config. root@proxmox:~# ifconfig eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx inet addr:192.168.0.100...

I upgraded to Debian 8 on the physical linux machine which proxmox VE is installed on. root@machine:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages...

Sounds good in theory but in practicality, is there's a massive catch. There's only one physical bare metal server at the location, and that's the server which is running the broken proxmox 3 on debian jessie 8 as the host. Inside proxmox 3 is the production openvz container which is about 250GB...

Read the upgrade guide only after the OS was upgraded to debian jessie 8. :eek: It says, to run vzdump to backup the openvz containers, and THEN to upgrade of the OS. :( In debian jessie 8, vzdump fails to run, due to a missing perl module, File/Basename.pm ... Queston, is it possible to...

@LnxBill thanks for the tips those are good ones to try. Upgraded to debian 8 jessie OS while proxmox 3 was still fully installed, before reading the proxmox documentation, because all previous upgrades of proxmox packages were very automatic. Suddenly jessie upgrade completes, reboot, and...

I upgraded the host node, from debian 7 (wheezy) to 8 (jessie). Debian 7 has been running proxmox 3.x for some time, with 2-3 openvz containers. I upgraded to debian 8. Now apt in debian jessie 8 wants to upgrade to proxmox 4.x So I consulted the guide here...

Re: upon fresh install of VE-2.1 and apt-get upgrade, containers disappear from Web U I just had the same exact thing happen. Proxmox 2.1 installed off a iso burned cd, then apt-get update, apt-get upgrade, and reboot. There are no templates in the web interface. Also, the directory that's...