Unable to start Openvz with proxmox

Darkie

New Member
Sep 16, 2015
25
0
1
Hey,
I cant start(or it is starting and i dont see any kind of console) my debian 7 container, its a completely new one.
I have no idea why it won't start, i hope someone will help me out :)
Screen: prntscr.com/8hbffr
Thank you!
 
Last edited:
Hello Darkie.

Do you have any other OpenVZ containers that work without problems?

Can you please post the output of the following command:

Code:
pveversion -v
 
root@deb1:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1
 
Hmm, same error on console, but i can join the container.
The problem is, that the container has no internet connection. Not in Routed mode (venet) and not in Bridged mode. :/
Hope you could help me :P
Thank you
 
Nothin...
But there is an error with the update command:
https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages The requested URL returned error: 401
W: https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages The requested URL returned error: 401

You should try the wiki. This is well documented how to run updates.

https://pve.proxmox.com/wiki/Package_repositories

You might want to make sure your system is configured properly, as it seems like there hasn't really been any configuration done yet.
 
My sources.list:

apt-get update && apt-get upgrade have absolutely no effect on the proxmox version :(

read again the upgrade docs.

two issues:
1. you use the wrong commands
2. you use the wrong repository
 
read again the upgrade docs.

two issues:
1. you use the wrong commands
2. you use the wrong repository
I dont find anything in the docs that would help. Which repository and commands should i use instead? Oo

Did you fix the pve subscription source?
Which subscription source? Do you mean the enterprise one? I removed it beacuse its a commertial one...
 
Hello, you need to have pve-no-subscription :

Code:
deb download [DOT] proxmox [DOT] com/debian wheezy pve-no-subscription

(Not allowed to add link ...)
 
Thank you very much!
Now the versions are:
root@deb1:~# pveversion -v
proxmox-ve-2.6.32: 3.4-163 (running kernel: 2.6.32-41-pve)
pve-manager: 3.4-10 (running version: 3.4-10/73ab1bcf)
pve-kernel-2.6.32-41-pve: 2.6.32-163
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-19
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-11
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
The problem now is, that there is no connection to the internet in the container :/
Its in bridged mode.
root@deb1:/# ping 8.8.8.8
connect: Network is unreachable
root@deb1:/# 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:65536 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)
 
Last edited:
Thank you very much!
Now the versions are:
The problem now is, that there is no connection to the internet in the container :/
Its in bridged mode.
Now that the updates are out of the way, do you have a dhcp server that is reachable from that bridge?