Search results

I've got the same problem restoring a CentOS 6 openvz on a proxmox 4.4 (originating from proxmox 3.4). TASK ERROR: unable to read version info I tried Eladio Gálvez tip but I still get this error. How can I force restore ?

If the cluster hosts 100 CT in 10 nodes of 10CT with local storage, I have 10 CT down if problem happens with 1 storage. Instead of 100 CT. That's my choice. I upgraded from 3.4 to 4.4 with hope this would be operational yet. I'm a bit disappointed by proxmox 4.4. I recently discovered too that...

What I wanted to say is : I don't want to see all my VM encountering difficulties (critical and not critical VM) if the shared storage has problems (bad sectors, raid rebuild, etc). That's why I prefer a not shared storage. I'm just surprise that I cannot use "live" migration with short...

I didn't choose shared storage because I will have many VM to deploy and I don't want to have problem with I/O disk, overload etc (still had). When problem with storage I prefer not have all VM in critical state. How can I choose this ? When I create a container it creates only lxc image.

I use "dir" type

Hello, Is it possible to migrate a container to another node with no long offline time ? Proxmox 4.4. Thx for any help.

OK thank you for information.

I'm surprised by your answer. I don't understand what's the point of filling min and max value for RAM allocation if the max is always taken on host... Do you mean RAM min/max allocation does not work only with Windows VM but should work with other kind of VM ?

When I set Share = 0 in allocated memory range, the memory used on host is OK (no more than memory min) but memory used in Task Manager (on Windows server) abnormally grows to 95%. Please help.

Hello, I have 128GB on host and created 2 VM with Windows Server 2012 (nothing running on the 2 Windows, just fresh install). When I fill 4096/102400 to auto allocation for each VM, I can start the first VM but fail for the second because there's not enough free RAM on host. Balloon drivers...