Search results

I've got several Proxmox 3.1 machines that have a peculiar problem. After booting them up, an extra route is created that has to be deleted before the machine can talk to others on the same subnet. After booting, the routes look like this (public IPs masked): # route Kernel IP routing table...

Recently I discovered that the default /proc mount inside CentOS containers running under Proxmox 3.1 were mounted insecurely: # mount|grep " /proc" proc on /proc type proc (rw,relatime) Under older versions of Proxmox, I was able to correct this by running: mount -o remount,nosuid,noexec...

Due instability issues we're having with a Proxmox 3.1 cluster, we need to remove several servers from the cluster without migrating the OpenVZ containers off of them. This thread is not about the instability of the cluster, if you want to read about that, go here...

We have a couple dozen Proxmox servers, and about once a month, one of them will have a kernel panic and lock up. The worst part about these lock ups is that when it's a node that is on a separate switch, all other Proxmox servers on that switch will stop responding until we can find the server...

Since Proxmox 2.x is based is based on pre-3.x kernels, I'm assuming that it's subject to the same divide by zero crashes as Proxmox 1.x... is that right? See: http://forum.proxmox.com/threads/13392-Divide-by-zero-kernel-crashes Curtis

I have a few dozen servers running Proxmox and I occasionally get server lockups. I posted some of the kernel errors from the console on ServerFault and in two different incidents responders are blaming the kernel version that Proxmox runs on (including the latest versions of Proxmox)...

I just noticed that a few of my OpenVZ containers show memory usage of around 1.6GBs of ram (on the Proxmox virtual machines display). I wouldn't think much of it, but one of the containers in question is clone of containers that normally use less than 300MBs, and this clone isn't running...

On one of my servers, all OpenVZ containers seem to lose access to /dev/simfs for a few minutes each day between 5:00am and 5:10am. Or, at least that's what appears to be happening... scripts that are running during that time report issues with reading files. My first thought was to look for a...

So, after a bit of research, it looks like Proxmox 2.0 (if you want to use the OpenVZ kernel) will not support TRIM, which I believe is needed to use SSD in a production environment. I have recorded the rest of my notes in a related thread...

Anyone have experience enabling TRIM support for SSDs under Proxmox? I am using version 1.7 at the moment... if it is supported, I would be interested to know what version it was added. This will be for OpenVZ containers... Thanks, Curtis

Can anyone tell me if OpenVZ offers any protection for the host node from a malicious user that has root access to a container? Below is a thread regarding LXC that suggests that with LXC, containers do not provide much protection, but that's LXC...

Hello, Kir Kolyshkin was kind enough to create a patch for a small issue I reported here: http://bugzilla.openvz.org/show_bug.cgi?id=1814 However, I'm not entirely certain how to apply the proposed patch (http://bugzilla.openvz.org/attachment.cgi?id=1478) in a Proxmox environment. Ideas...

I've successfully moved a few XenServer CentOS guests to OpenVZ containers using the P2V migration instructions. However, one question that lingers for me is whether there is any performance penalty due to the fact that the guests I migrated had XenServer Tools installed (which is supposed to...

I understand that to add IP aliases to a specific OpenVZ container that you simply add them through the GUI in a comma separated list. I tested this (using venet) and it works great. However, I was wondering if there's a limit to the number of IPs that can be added this way? For example...

This is a reply to SuSt from this post: (http://forum.proxmox.com/threads/5913-Create-cluster-with-existing-OpenVZ-CT-on-node) I started looking at OpenVZ after a friend shared his experiences of running his business under OpenVZ for quite some time now and has been quite happy with it. So...

So, I've got two proxmox machines that I want to turn into a cluster to make it easy to migrate OpenVZ containers between them. At the moment, one machine has no containers and the other machine has only one. According to the documentation...

As I've come to find out, you can't monitor swap memory usage using the usual "free" command in OpenVZ as it always reports zero. This is because swap is handled by the HN. However, I found this great utility, vzfree, that is supposed to solve the issue. You can read about it here...

So, my hardware vendor sent a proxmox box to my remote colo facility without setting the IP on my proxmox box first. Since this box will not have network access at first, I need to provide my "remote hands" service with instructions on how to properly set the ip in proxmox. To have them change...

Sorry, I'm still pretty new to Proxmox, so I apologize if this question has already been addressed... Is Proxmox 1.7 something you can put on a public IP for remote management purposes, or is there some additional hardening that needs to be done before considering that? Thanks, Curtis

I'm installing Proxmox 1.7 on a system with raid 10 (adaptec 2405) and 4 2TB drives. I plan on using the system for OpenVZ containers and therefore will need to find a way around the 2TB limitation. At least one person on this forum got around this limitation by carving out a 30GB volume to...