OpenVZ Container in Proxmox 2 b3 without network

mechanicus

Renowned Member
Mar 30, 2009
54
0
71
Germany
Hello,

I don't know if it's 2.0 specific, but I now test OpenVZ the the first time in Proxmox VE 2.0 beta3.
I've installed
centos-5-standard_5.6-1_i386.tar.gz from http://pve.proxmox.com/wiki/
and
scientific-6-x86.tar.gz (renamed to scilinux-6.0-standard_6.0_i386.tar.gz) from http://download.openvz.org/template/precreated/

Problem: centos runs as expected well, but in scientific there is no network.

In centos with running network are in /etc/sysconfig/network-scripts/ the right configurateted files ifcfg-vnet0 and ifcfg-vnet0:0.
In scientific there are no files like thats.

In the web interface, the initLog of centos looks well, the one of scientific is failed:
Code:
starting init logger
Starting udev: /sbin/start_udev: line 291: /etc/sysconfig/network: No such file or directory
[  OK  ]

But why this?

Best Regards

Edit: It seems to be a mistake in the /sbin/start_udev. It has not involve Proxmox.
 
Last edited:
just started a sl6 template on one of our test boxes (using venet), works as expected.
 
Thank you. In the meantime, I've installed another template from http://download.openvz.org/template/precreated/contrib/scientific-6-i386-default-6.1-20111104.tar.xz, have unpack this and repack to scilinux-6.1-standard_6.1_i368.tar.gz.
After the installation the initlog in the web interface looks well:
Code:
starting init logger
Starting udev: [  OK  ]
But the network don't work. There is no interface venet0:0.
The mistake was, that there is no configuration file for the distri in /etc/vz/dists/
I copied the centos.conf to scilinux.conf, destroyed the container and make a new install.

Now it runs well! :D

May be it's helpful to post a hint during the installation, if a distri config file is missing. So it shows only "extracting ... " and at last "TASK OK".
 
Last edited:
thanks for feedback. how did you install your box? a recent install should have a 'scientific.conf' included.

post you 'pveversion -v'
 
I've download the proxmox-ve_20-784729f4-19.iso from your server an after installing with CD I have running "# aptitude update && aptitude full-upgrade"

My version:
Code:
# pveversion -v
pve-manager: 2.0-14 (pve-manager/2.0/6a150142)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-54
pve-kernel-2.6.32-6-pve: 2.6.32-54
lvm2: 2.02.86-1pve2
clvm: 2.02.86-1pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.7-1
pve-cluster: 1.0-12
qemu-server: 2.0-11
pve-firmware: 1.0-13
libpve-common-perl: 1.0-10
libpve-access-control: 1.0-3
libpve-storage-perl: 2.0-9
vncterm: 1.0-2
vzctl: 3.0.29-3pve7
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-1
ksm-control-daemon: 1.1-1
 
I am just confused how to make the container and VM access the internet in PMv2b3? I uploaded debian-6-i386 template and chose vmbr0 as the network and vmbr0 active on start. Do I need to install something like libvirt-bin to make vmbr0? The output of pveversion is as follows. Thanks! # pveversion -v pve-manager: 2.0-18 (pve-manager/2.0/16283a5a) running kernel: 2.6.32-6-pve proxmox-ve-2.6.32: 2.0-55 pve-kernel-2.6.32-6-pve: 2.6.32-55 lvm2: 2.02.88-2pve1 clvm: 2.02.88-2pve1 corosync-pve: 1.4.1-1 openais-pve: 1.1.4-1 libqb: 0.6.0-1 redhat-cluster-pve: 3.1.8-3 pve-cluster: 1.0-17 qemu-server: 2.0-13 pve-firmware: 1.0-14 libpve-common-perl: 1.0-11 libpve-access-control: 1.0-5 libpve-storage-perl: 2.0-9 vncterm: 1.0-2 vzctl: 3.0.29-3pve8 vzprocps: 2.0.11-2 vzquota: 3.0.12-3 pve-qemu-kvm: 1.0-1 ksm-control-daemon: 1.1-1
 
Hi,

I m new on this forum.
So i just install the lastest proxmox 2 on a server. My bridge vmbr0 is ok, but i still have no network on my new container openvz.

I try with a ubuntu and a debian but the problem still the same :

Next bellow the log of my proxmox server :

Jan 16 22:59:16 proxmox pvestatd[1517]: starting server
Jan 16 22:59:18 proxmox pvedaemon[1476]: <root@pam> starting task UPIDroxmox:0000060C:000008FD:4F149DB6:vzstart:100:root@pam:
Jan 16 22:59:18 proxmox pvedaemon[1548]: starting CT 100: UPIDroxmox:0000060C:000008FD:4F149DB6:vzstart:100:root@pam:
Jan 16 22:59:18 proxmox kernel: warning: `vzctl' uses 32-bit capabilities (legacy support in use)
Jan 16 22:59:18 proxmox kernel: CT: 100: started
Jan 16 22:59:20 proxmox pvedaemon[1476]: <root@pam> end task UPIDroxmox:0000060C:000008FD:4F149DB6:vzstart:100:root@pam: OK
Jan 16 22:59:21 proxmox kernel: vmbr0: no IPv6 routers present
Jan 16 22:59:22 proxmox kernel: venet0: no IPv6 routers present
Jan 16 22:59:22 proxmox kernel: eth0: no IPv6 routers present
Jan 16 22:59:23 proxmox pvedaemon[1477]: <root@pam> successful auth for user 'root@pam'
Jan 16 22:59:23 proxmox pvedaemon[1931]: starting openvz vnc proxy UPIDroxmox:0000078B:00000B09:4F149DBB:vncproxy:100:root@pam:
Jan 16 22:59:23 proxmox pvedaemon[1479]: <root@pam> starting task UPIDroxmox:0000078B:00000B09:4F149DBB:vncproxy:100:root@pam:
Jan 16 22:59:29 proxmox pvedaemon[1477]: <root@pam> successful auth for user 'root@pam'
Jan 16 22:59:30 proxmox kernel: veth100.0: no IPv6 routers present
Jan 16 22:59:31 proxmox kernel: eth0: no IPv6 routers present
Jan 16 23:00:50 proxmox kernel: eth0: no IPv6 routers present
Jan 16 23:01:46 proxmox postfix/master[1274]: reload -- version 2.7.1, configuration /etc/postfix
Jan 16 23:01:46 proxmox kernel: eth0: no IPv6 routers present
Jan 16 23:01:46 proxmox postfix/master[1274]: reload -- version 2.7.1, configuration /etc/postfix
Jan 16 23:01:46 proxmox kernel: vmbr0: port 1(eth0) entering disabled state
Jan 16 23:01:46 proxmox kernel: device eth0 left promiscuous mode
Jan 16 23:01:46 proxmox kernel: vmbr0: port 1(eth0) entering disabled state
Jan 16 23:01:47 proxmox postfix/master[1274]: reload -- version 2.7.1, configuration /etc/postfix
Jan 16 23:01:47 proxmox kernel: device eth0 entered promiscuous mode
Jan 16 23:01:47 proxmox kernel: r8169 0000:04:00.0: eth0: link up
Jan 16 23:01:47 proxmox kernel: vmbr0: port 1(eth0) entering forwarding state
Jan 16 23:01:48 proxmox postfix/master[1274]: reload -- version 2.7.1, configuration /etc/postfix
Jan 16 23:01:58 proxmox kernel: eth0: no IPv6 routers present
Jan 16 23:02:03 proxmox kernel: eth0: no IPv6 routers present

There is nothing

On my container i have :

cat /var/log/syslog

Jan 16 22:01:53 test dhclient: Copyright 2004-2010 Internet Systems Consortium.
Jan 16 22:01:53 test dhclient: All rights reserved.
Jan 16 22:01:53 test dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jan 16 22:01:53 test dhclient:
Jan 16 22:01:53 test dhclient: Listening on LPF/eth0/de:19:94:dc:05:76
Jan 16 22:01:53 test dhclient: Sending on LPF/eth0/de:19:94:dc:05:76
Jan 16 22:01:53 test dhclient: Sending on Socket/fallback
Jan 16 22:01:54 test dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 16 22:01:57 test dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 16 22:02:00 test dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jan 16 22:02:07 test dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Jan 16 22:02:16 test dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jan 16 22:02:23 test dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jan 16 22:02:31 test dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Jan 16 22:02:42 test dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Jan 16 22:02:55 test dhclient: No DHCPOFFERS received.
Jan 16 22:02:55 test dhclient: No working leases in persistent database - sleeping.
Jan 16 22:02:55 test postfix/master[331]: reload -- version 2.7.1, configuration /etc/postfix

Its so strange i havent got any error message.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!