Search results

I am just wondering if updates for LXC and the features it offers could be defined a bit more on the expected availability. This really seems the one place where 4.x took a step backwards in comparison to the 3.4 / Open VZ solution. In particular we are interested in the following: 1. Live...

Ok, so hoping this helps others as they make the journey from 3.4 to 4.0. For us it has went pretty well, but there are a number of gotcha's that we will point out. First, the "plan" as originally stated and then expanded upon worked well. We were able to move both OpenVZ images and KVM...

Can you provide more details on this and maybe even steps to accomplish. It is on local storage. Thanks!

You will have to tweak the conf file for the machine, but 10.04 does indeed work. You also need to edit the /usr/share/perl5/PVE/LXC/Setup/Ubuntu.pm file and add: '10.04' => 1, # lucid LTS To the $known_versions hash and then update on if statement to include this version as well: if...

Somehow one of my storages does not have thin provision on it (ZFS storage if that matters) and I migrated a number of machines to it. Is there a way to enable thin provisioning (yes I know about the check box) AND then have the images shrunk to be thinly provisioned. Of course would prefer if...

Thanks for the quick reply. My suggestion would be to create this as a parameter that can be passed on the cluster creation command so that you can specify the host / interface you want. Just makes things more flexible for setup.

We are in the process of rebuilding (well creating new) a cluster running on 4.0. We have three interfaces on each of the machines. Two 1G which are front facing and used for accessing the virtual machines with public IP space and a 10G used for our storage network running on private IP space...

Tried that, but this only ends up with the container not starting and the message: Simultaneously requested dropping and keeping caps being logged. I am sure it has to do with the configurations in /usr/share/lxc, just unsure at this point how to resolve this problem in a way that does not...

I am hoping to rely on the wisdom of the group to help with an item we are having issues with since upgrading our OpenVZ container to LXC on a 4.0 system. One of them requires capabilities applied to a binary so that it is able to open ports 80 / 443 for web services but still run as an...

That was exactly the fix for this, sorry I did not find this in my searching before post. Appreciate the prompt reply!

We are converting our OpenVZ containers on 3.4 to LXC in 4.0. So far this has been a simple process and worked without issue until this container. It is running CentOS 5.11 and when we run the ptc restore get an error "unsupported redhat release 'CentOS release 5.11 (Final)'". Tried to modify...

Yes of course that is possible, but since this setting is at the top level every server then sends out with the same e-mail address. If $hostname is allowed you get stuff like: proxmox@server1.excel.net proxmox@server2.excel.net ... This way if the message does not make it clear which machine...

We are in the process of building a new cluster using 4.0. I noticed under the Datacenter -> Options section a Email from address field with the hint of root@$hostname. We would like to change this to proxmox@$hostname but the edit entry is not matching that as valid. It is instead checking...

Any chance this has been addressed in 4.0? This seems as well like it should be easy to accomplish and we have a couple of KVM machines where it would be helpful.

We just currently expanded a cluster from 2 nodes to 3 nodes on our 3.4 system. We have a mixture of KVM / VZ images running and were looking into the upgrade process. Since we need to have very little to no downtime based on the servers functions I do not see the standard upgrade procedure as...

I personally was not ever able to get a fix for this problem, other than every restart to run the commands listed in the first post. HOWEVER, this node was part of a cluster and I was able to wipe it completely, now am fully patched and have not experienced the issue since. Not sure if you...

This ended up being an issue with the fact that we are using a wildcard certificate for services so that everything is trusted when you access the web UI. Ended up copying the key / pem from one of the original nodes over to the new node /etc/pve/local/pve-ssl.key and pve-ssl.pem files and away...

There is no firewall, but I cannot access 8006 even directly to the new node. I tried running pvecm updatecerts --force and received the following: # pvecm updatecerts --force Signature ok subject=/OU=PVE Cluster Node/O=Proxmox Virtual Environment/CN=cor-vst-03.excel.net Getting CA Private Key...

We have been for a long time running a two cluster node system and working great. We needed to expand things so we added another node and attempted to join the new box to the cluster. This seems to have worked "partially" but we definitely do not have functionality needed. For example if we...

Tried that and got: # insserv -v insserv: creating .depend.boot insserv: creating .depend.start insserv: creating .depend.stop Restarted and nothing different. Not sure why it is not following order. Might try and place dependencies on the zfs-mount server in the pve services. The problem...