Search results

I can confirm time drift on VM running WIndows Server 2008R2. This machine acts as a Active Directory DC, and time drift causes wrong time on all machines connected to Active Directory. I found a temporary solution -- https://www.greyware.com/software/domaintime/v5/configuration/other/agent/...

My two Proxmox nodes was almost the same results, one less, one more. Here is the biggest uptime I have, node was rebooted for upgrade from 3.4 to 4.4

You can backup to ANY storage that you can mount. Just mount it, add 'Directory' storage, point it to your mount point, allow Backups in storage properties and that's all.

Seems to you have no free space on hard disk. Please check with df -h command.

You may try do the trick with IPMI BMC feature, that allow you to mount ISO image as CD/DVD drive and boot from it.

Running out of space on host?

VLAN and multicast may require some special settings in switch, please check it.

Hm... You bought this module, this means you pay money to them, and they don't answer? This is very bad.

Wow, didn't know that, thanks!

systemctl disable ntp

Here is detailed description of WHMCS+Proxmox and step-by-step guide: https://www.docs.modulesgarden.com/Proxmox_VPS_For_WHMCS

That's really good! Хорошо, что всё так легко обошлось :) Но свитчи ты на гигабит поменяй. Бэкап, небось, медленный?

What do you have and what do you want to get.

I have two Proxmox hosts, 196 Gb and 256 Gb RAM, dual Xeon, Supermicro, very similar to your configuration. Very standard servers. VMs with and without ballooning, Windows and Linux, on both nodes and I have never face with your problem. What is the difference?.. Is your RAM fast enough?

How many VMs on you host? What is host hw configuration? Is there all of your VMs configured to use memory ballooning? 256 Mb as Min is too small. Try to set at least 1-2 Gb. Here is thread from qemu-devel mailing list: https://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg05646.html

Can you show your setup configuration, both host and VMs?

Absolutely right. Also, disk device must be set to "IDE" in new virtual machine. It is possible to install VirtIO drivers from RedHat later and be happy with high-performance VirtIO disks. And one more thing. When I installed Windows 2008 (not R2!) in Proxmox VM, there were random BSODs...

Gre Great! Glad to help.

Yes, apply mergeide patch anyway.

First apply 'mergeide' patch to your system and yes, remove VMWare tools. All you need is described in Proxmox Wiki Migration article. Then just create VM with appropriate configuration, attach your images, even in native VMDK (flatten it first) format, but better convert it to qcow2 or raw.