Search results

hi, i'm having problems with PVE 2.0 that seems to be related to memory. i've found this thread: http://forum.proxmox.com/threads/8195-RAM-and-SWAP-for-OpenVZ?highlight=java i've followed VSwap instructions, but i can't get a simple application running even whith 8000M memory and 4000M swap...

hi, i usually change these settings in HN because of requirements on my vms: - /etc/security/limits.conf : * - nofile 65535 - /etc/sysctl.conf: net.ipv4.tcp_keepalive_time = 600 - Inside container: echo tmpfs /dev/shm tmpfs defaults 0 0 >> /etc/fstab mount...

thanks for quick response. so, just to clarify and calm my admin-paranoic brain: any dump/export can be imported in 2.0 with 100% compatibility and without performing any additional task?

we planned to migrate our 6 node environment by getting one node empty of mvs, updating and then moving vms again to that node. as clustering system is completly diferent our approach is not possible. can we just dump mvs, move tgz over the network and import them again in new(updated) nodes?

i've installed RC1 and when configuring ldap in auth settings i can't see any way to filter ldap query. on most servers we usually only allow to appear on system (getent passwd) a subset of our whole user tree. is that possible in PVE 2?

all our servers are usually ldaped with specific settings, mainly group filtering. is there any diference in using your integrated ldap auth than tipical pam+ldap setup?

what pam service is pve using?

i hope that developers will give us a migration script. oh, and what about exporting/importing dumps? will this require any manual modification or intervention?

do you mean changing all cfgs by hand one by one?

hi, we're planning to migrate to PVE 2.0 as soon as is released. will it be needed any manual intervention besides updating/upgrading packages? there will be any compatibility issues between versions? will be possible to add a 2.0 node to a 1.x cluster? (then migrate all VMs and upgrade the...

I'm also interested in this question, i would like to close port 111. I guess you only need that port if you plan to use clustering, but I'm not really sure. Let's see if some admin/guru give us any answer.

# pveversion -v pve-manager: 1.8-17 (pve-manager/1.8/5948) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.8-33 pve-kernel-2.6.32-4-pve: 2.6.32-33 qemu-server: 1.1-30 pve-firmware: 1.0-11 libpve-storage-perl: 1.0-17 vncterm: 0.9-2 vzctl: 3.0.26-1pve4 vzdump: 1.2-12 vzprocps: 2.0.11-2 vzquota...

ok, that could be a workaround. but I still would like to know if this limitation is by design, a bug or something else.

do you mean if I keep those running? I usually use vzctl enter when preparing container, but once i've settled up i just connect through ssh.

hi, one of my dumps is failing: 10012: Nov 12 12:29:23 INFO: suspend... 10012: Nov 12 12:29:26 INFO: Can not suspend container: Resource temporarily unavailable 10012: Nov 12 12:29:26 INFO: Error: foreign process 15195/21339(lockd) inside CT (e.g. vzctl enter or vzctl exec). 10012: Nov 12...

hi, i've been working on a zimbra-proxmox environment and i've created this simple script to check errors on /proc/user_beancounters can be used in nagios or in any other monitoring system feel free to add it to wiki or any other place. #!/bin/bash # script for checking system counters on...

ok, i'll try that and i'll update this thread with results. anyway, do you have any plans regarding external/additional storage devices for openvz? seems to be a quite common issue around forums and lists and i'm not sure the amount of coding effort it requires.

ok, so i assume that if mounted fs is an iscsi volume it can be used that way. i'm i correct?

hi, i know is unsupported: http://forum.proxmox.com/threads/6195-vzquota-doesn-t-honour-VE_PRIVATE but i would know if i must open a bug for this. i've configured some containers on a samba mounted resource. in my 134.conf i have: VE_ROOT="/mnt/samba/vzbase/root/134"...

i've just found the problem. quota file had private dir harcoded, so i just removed /var/lib/vzquota/quota.134 and started container. everything seems to be ok now. is there any other problems i can face? i've updated original post with new info.