Search results

I didn't try it, but my research suggests that the modern tooling would be CAPI (Cluster API). Rancher supports CAPI with Rancher Turtles and on the Proxmox VE side, you need a Cluster API Provider.

Feature Request: https://bugzilla.proxmox.com/show_bug.cgi?id=5667

Feature Request: https://bugzilla.proxmox.com/show_bug.cgi?id=5667

Feature Request: https://bugzilla.proxmox.com/show_bug.cgi?id=5667

My VDI use-case is providing applications (not full desktops) that run on a central server to multiple users.

With SPICE being deprecated by Red Hat it is a bad idea to depend on it in the long term - at least until somebody shows interest in maintaining it and developing it further. The GNU/Linux ecosystem (mainly the big DEs) seem to focus on the RDP-protocol for remote-desktop use cases. There is a...

There is a related issue: https://bugzilla.proxmox.com/show_bug.cgi?id=1222

I'd argue that "en_US.UTF-8" should be installed and set as the default on a server-system.

Others in the forum mentioned (e.g. here) that round-robin will break in some cases and you better use a reverse proxy. You can either install that externally (some people do so on OPNsense), on a HA VM inside of PVE or on multiple PVE-hosts (HAproxy, VIP, keepalived, sticky sessions) as...

There is an entry on ServerFault where ebtables and bridge are mentioned. Hope that helps. And there is a german thread about this topic.

Linux uses free memory as disk cache. Detailed explanation: http://www.linuxatemyram.com/

So fixed memory size means the memory is never available for the host or other VMs, even if ballooning is on and the VM doesn't use the memory itself? What are the reasons for using fixed size memory (as the default)?

CentOS 7 has the same behaviour on HP Servers (with p410i). https://bugs.centos.org/view.php?id=13184

I checked the tuned profiles that Red Hat distributes in their systems. The profiles "virtual-guest" and "virtual-host" both use vm.swappiness=10. According to this the PVE installer should use a lower default value than 60 (which is the Debian default).

In the meantime the issue was created here.

If you can afford the downtime it should be an easy solution to just use the "stop" backup mode. That should stop the DBMS, then the OS and thus give you a consistent state to back up. You may want to tune some things (e.g. GRUB timeout) to make the VM boot faster. @tom (proxmox staff member)...

Are there downsides to enabling NUMA? I'm just wondering why it's not set by default. As this option is exposed in the GUI I think we should have a Wiki article for it. https://pve.proxmox.com/wiki/NUMA

I can verify the problem and the solution. My CentOS 7 VM would not recognize the LVM configuration if I use SCSI or VirtIO in PVE -- even though it is a SCSI disk in VMware.

I think you misunderstood me @robhost. I had the same problem as @bizzarrone as the restore process gets stuck if I try to restore a qcow2 kvm backup on a lvm-thin datastore. No share access involved - just local to local. Other users seem to have the same problem...

You mean it's only a GUI problem? For me it ate up resources until the host went down.