Managing OpenVZ container with Proxmox VE 2.0 beta

martin · Oct 7, 2011

We just uploaded updates, including the creation and management of OpenVZ containers.

Just run aptitude update/upgrade on your 2.0 beta system.

Happy testing, waiting for feedback!
__________________
Best regards,

Martin Maurer
Proxmox VE project leader

bread-baker · Oct 7, 2011

I just created 2 ct's

i have a 2 node cluster. fbc10 and fbc158 are the node names.

i used pve at fbc10.
both ct's used debian 6.0 std template.

the 1-st ct uses venet ,
- networking works.
- ssh into ct using root password worked
- vzctl enter displays:

Code:

vzctl enter 999
Warning at /etc/pve/openvz/999.conf:1: invalid value for ONBOOT ("0"), skipped
entered into CT 999

for the 2-nd container, i used bridged network
i used pve on fbc10
created ct onto fbc158
results:
main issue is networking does not work yet. here is some info :

Code:

root@homenet-fbc158 /etc/vz # vzctl enter 998
Warning at /etc/pve/openvz/998.conf:1: invalid value for ONBOOT ("0"), skipped
entered into CT 998
root@test998:/# ifconfig -a
eth0      Link encap:Ethernet  HWaddr d6:ee:ac:cc:4f:de  
          inet addr:10.100.100.198  Bcast:10.100.100.255  Mask:255.255.255.0
          inet6 addr: fe80::d4ee:acff:fecc:4fde/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:9 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

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:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:224 (224.0 B)  TX bytes:224 (224.0 B)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          BROADCAST POINTOPOINT 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)

root@test998:/# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0   inet static
 address 10.100.100.198
 netmask 255.255.255.0
 network 10.100.100.0
 gateway 10.100.100.2

root@test998:/# cat /etc/resolv.conf
search fantinibakery.com
nameserver 8.8.8.8

also I was not able to open console for the container on fbc158 from pve screen fbc10

from pve at fbc158 i could connect to the ct running on fbc158

if there is anymore testing or info needed please let me know.

bread-baker · Oct 7, 2011

also pressing console does not always work . when it does not something like this displays:

it eventually works after trying a few more times.

bread-baker · Oct 7, 2011

I tested this
setup another bridged network ct.
using pve at fbc158, for a container on fbc158 .
same result can not ping out .

next I'll try bridged net ct , but this time not using dns settings from host.

here is a screen shot at confirm create ct:

same result ,

Code:

root@homenet-fbc158 /etc/vz # vzctl enter 996
Warning at /etc/pve/openvz/996.conf:1: invalid value for ONBOOT ("0"), skipped
entered into CT 996
root@test196:/# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: venet0: <BROADCAST,POINTOPOINT,NOARP> mtu 1500 qdisc noop state DOWN 
    link/void 
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether fe:7f:98:cd:6c:b4 brd ff:ff:ff:ff:ff:ff
    inet 10.100.100.196/24 brd 10.100.100.255 scope global eth0
    inet6 fe80::fc7f:98ff:fecd:6cb4/64 scope link 
       valid_lft forever preferred_lft forever
root@test196:/# cat /etc/resolv.conf
search fantinibakery.com
nameserver 8.8.4.4
nameserver 8.8.8.8
root@test196:/# ping 10.100.100.158
PING 10.100.100.158 (10.100.100.158) 56(84) bytes of data.
^C
--- 10.100.100.158 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

martin · Oct 7, 2011

I filed a bug for the veth issue, see https://bugzilla.proxmox.com/show_bug.cgi?id=15

martin · Oct 7, 2011

which browser/java OS do you got on your desktop?

Martin

bread-baker · Oct 8, 2011

that was probably using firefox 7..0.1

I'll try using chrome instead.

bread-baker · Oct 8, 2011

martin said:
which browser/java OS do you got on your desktop?

Martin

after switching to Chrome, I have not had any issues with console.

tom · Oct 8, 2011

... and what combination has issues?

bread-baker · Oct 8, 2011

tom said:
... and what combination has issues?

Using firefox 7.01 on ubuntu lucid , pressing the console key ends up not connecting as the pic I uploaded shows.

that has not happened at all using chrome.

tux · Oct 9, 2011

Code:

dpkg: error processing /var/cache/apt/archives/pve-manager_2.0-7_all.deb (--unpack):
 error setting ownership of `./etc/vz/conf/ve-pve.auto.conf-sample': Function not implemented
configured to not write apport reports
                                      dpkg-deb: subprocess paste killed by signal (Broken pipe)
Preparing to replace usbutils 0.87-5 (using .../usbutils_0.87-5squeeze1_amd64.deb) ...
Unpacking replacement usbutils ...
Preparing to replace ssh 1:5.5p1-6 (using .../ssh_1%3a5.5p1-6+squeeze1_all.deb) ...
Unpacking replacement ssh ...
Processing triggers for man-db ...
Processing triggers for install-info ...
Errors were encountered while processing:
 /var/cache/apt/archives/pve-manager_2.0-7_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

cannot update.

SOLVED. if you set manual a link /etc/vz/conf/ - remove it and create /etc/vz/conf/ again.

madcook · Oct 10, 2011

Hi

Now I testing Version 2.0/de5d8ab1 and try to limit IO on VM, can some one*explain how to do this?

dietmar · Oct 10, 2011

madcook said:
Now I testing Version 2.0/de5d8ab1 and try to limit IO on VM, can some one*explain how to do this?

Just set a rate limit on the network adapter (kvm only). Or do you want to limit disk IO?

madcook · Oct 10, 2011

yes, I mean limit disk IO on OpenVZ

dietmar · Oct 11, 2011

madcook said:
yes, I mean limit disk IO on OpenVZ

Well, AFAIK OpenVZ only allows you to set 'ioprio' (0 to 7) - you talk about that?

madcook · Oct 11, 2011

I hoped that on new version will be possibility to limit disk IO, this is biggest problem on VM`s.
Not exactly about 'ioprio', do you thing 'ioprio' can help with limit disk IO?**

dietmar · Oct 11, 2011

madcook said:
I hoped that on new version will be possibility to limit disk IO, this is biggest problem on VM`s.
Not exactly about 'ioprio', do you thing 'ioprio' can help with limit disk IO?**

No, ioprio is set anyways by default (4). There is also the 'blkio' cgroup, but I never tested that so far.

madcook · Oct 14, 2011

When I load hard disk on VM on OpenVZ *in*diagram was not any*actions (write or read) but on Node IO 40-50%, this will be fixed on final version?

agismaniax · Oct 27, 2011

i'm testing proxmox ve 2.0 beta and upgraded to latest version. why i can not Create New Container?

tom · Oct 27, 2011

just run 'aptitude update' and 'aptitude safe-upgrade' -do you get any errors?

to check the version, pls run 'pveversion -v' and post it here.

Managing OpenVZ container with Proxmox VE 2.0 beta

Proxmox Staff Member

Member

Member

Member

Proxmox Staff Member

Proxmox Staff Member

Member

Member

Proxmox Staff Member

Member

Member

New Member

Proxmox Staff Member

New Member

Proxmox Staff Member

New Member

Proxmox Staff Member

New Member

agismaniax

Guest

Proxmox Staff Member