Search results

well if you want to be able to move your containers from one hardware node to another without adjusting IPs and routing this is what we do, especially with scarse real IPv4 addresses. we'd greatly appreciate the ability (or even automatism) to generate those /32 routes per container on each...

Hi we are trying to solve the following issue: we created a linux vmbr2 bridge and assigned a dummy IP to it: 10.10.10.10/32 we also created a LXC using this vmbr2 as bridge to this container for its veth (eth0). assign 192.168.1.1/32 on it's eth0 and setting the default-gw to 10.10.10.10 the...

back again for a single-ip-networking-setup :) here is what needs to be done: hypervisor: have a bridge (eg vmbr2) and assign it an IP like 10.1.1.1/32 the add an IP route for a container: ip rou add 10.10.10.10/32 dev vmbr2 within the container (assuming eth0 is connected to vmbr2 at the...

assuming a new server with PVE5 is out of the question: simply create your sdc1+sdd1 partitions and add those into the md2 mirror - no need to hassle around with missing and copying the partitionschema, then extend the pve volumegroup; now you should probably make sure you have backups of your...

well, if this were possible during the restore of a former VE container this might be an option, though I don't see where this would be possible to do during this openvz restore to lxc ...

hi patch was tested and works with sarge (especially when migrating from old openvz-backups). I guess at the moment the only way to get a template would be to generate an empty debian v3.x using proxmox-ve-3.4 and then back it up and restore it and then generate the template from the lxc. for...

well, patch is quite easy: in /usr/share/perl5/PVE/LXC/Setup/Debian.pm change this line: if !($version >= 4 && $version <= 10); to this one: if !($version >= 3 && $version <= 10); thx hk

well, the same argument could be made vor debian v4 :) please consider letting admins do what they want and change the debian release requirement to v3. regards, hk

well, I was more looking to authenticate users at the mailgateway not doing some fetchmail-config. thx hk

Hi is there some reasoning behind the support for debian>4 only? if not please enable also v3 debian to be started in lxc environment... regards hk

Hi If I remember correctly previous PMG could authenticate users via pop3 backends for different domains. Is there anything like this planned for PMG5? (Migrating multiple mailservers to be integrated via LDAP is no easy task especially if those servers don’t use LDAP :)). Thx, hk PS. Great...

Dear Wolfgang, thank you for your reply, we will engage another testinground. As for the IPv6 prefixes longer than /64 it's a general rule for ip-address-autoassignment to work on a broadcast network you need /64, otherwise this won't work, but for example for point-to-point-links it's always...

hmm - noone?

Well, besides databases should support proper locking and transaction-processing and therefore be reboot-safe in terms of data corruption if a node breaks, starting the VM on another node should leave no data corruption if things are done the right way. Having said this, I know...

well, at least they seem to work on patching :) https://virtuozzo.com/virtuozzo-addresses-intel-bug-questions/

In the end, it’s open source and we will help ourselves anyways...

Well, would ask to reconsider as RedHat provides updates and OpenVZ is certainly spinning their update-machine, it would be a nice move to repackage this kernel for 3.4 ad those still in need.

in the meantime ... found that PVE5 is already helping by configuring container interface post-up and pre-down scripts accordingly. for IPv6 this is also done, but is not sufficient one can not set eg fe80::1 as gateway, but only obvious non local addresses, funfact also link-local IPv4 as...

Hi the main question is: where could we hook startup and shutdown scripts for containers in proxmox? we connect containers to a linux-bridge and then add host-routes with "ip rou add 10.11.22.33/32 dev vmbrXX" on the hypervisor, we also add a host-route within the container direct at the...

well, to make things short, the issue is with this quite "creative" bios-update-app: afulnx -> http://hargrave.info/articles/afulnx.html elaborates quite nicely. now, Mr. Hargrave nicely provided a gitrepo for this module to build: https://github.com/romanhargrave/amifldrv but in the end I...