Updated log:
lxc-start 1466438493.256 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /var/lib/lxc/116/config
lxc-start 1466438493.256 WARN lxc_confile - confile.c:config_pivotdir:1817 - lxc.pivotdir is ignored. It will soon become an error.
lxc-start...
We need some assistance.. A server had it's power cut out and after starting it back up again, one of the containers could not start. Here's the log file:
root@vm21:~# cat 116.txt
lxc-start 1466384331.840 ERROR lxc_utils - utils.c:open_without_symlink:1626 - Input/output error -...
Hello,
We recently installed Proxmox v4.1 and migrated our VM's from the old Proxmox server to the new one. Our servers are all HP ProLiant. For some reason, we are no longer getting SNMP Alerts from the server in case a drive fails or other type of hardware.. How do we go about setting up SNMP...
As shown in the graphic represented below, our win 2003 machine is showing a very high cpu load when we enable 4 cores. If we enable just 2 cores, or just 1, the cpu load drops below 100% to a normal percentage??
We downgraded the kernal to 2.6.32-4 and also ran through this...
I searched the forums and found this thread which may be helpful..
http://forum.proxmox.com/threads/8444-High-loads-and-freezes-with-latest-2-6-32-7-pve-kernel?p=47745#post47745
We are running into a very strange issue where we have to give a KVM 1cpu/1core on an 8core node in order to get it booted up properly, and to keep the CPU process under 100%.. If we give it 2cores, the CPU process jumps over 250% when viewing the process monitor in webmin. If we give the KVM 4...
We recently P to V a Windows Server 2003 machine (32 bit) with 4GB of ram and 2CPU's. When setting up the VM, we configured the hardware to retain 4GB of ram, however bumped up the CPU's to 4. After doing so, the O/S is extremely slow and it takes about 30minutes to load up IIS. We then reduced...
We have a physical machine that needs to be converted to proxmox. We have converted machines in the past using the VMWare Conversion tool to a vmdk file, then loading the vmdk file into proxmox which worked well. That process seemed to only work for MBR based systems...
One of our oldest...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.