Search results

Which memory mode is best for Proxmox on a Dell PowerEdge T620 server?

I have a Dell R515 server that I upgraded so that all 8 hard-drives are solid state. Specifically, I have 8 of these SSDs in a RAID 10: Samsung V-NAND SSD 860 EVO 1TB SATA 6Gbps Model MZ-76E1T0 Model Code: MZ-76E1T0E After a few months, Proxmox kept emailing me this error regarding...

Proxmox provides 3 options for backup compression: LZO (fast) GZIP (good) ZSTD (fast and good) Which of these 3 would be most efficient for "Rsync --fuzzy Synchronization", which uses a previous backup at an offsite destination as the basis for minimizing data transfer of the most current...

I just noticed the default backup compression has changed to zst. Proxmox has been pretty great in terms of keeping up with the latest "fast and good" compressions. LZO was new to me before I started using proxmox and now they introduce me to zst. If Proxmox uses it, it is probably pretty good...

Interesting. I notice the Proxmox GUI for KVM has a "Hardware" tab with a sub-option "Display": Promox GUI for LXC has (instead) a "Resources" tab with no sub-option for display: I assume Proxmox GUI cannot give "Display" to LXC unless the LXC technology already inherently possesses...

Using Proxmox, I want to do some testing on an Ubuntu 18.04 server with the GNOME desktop installed. Can a LXC container handle a Desktop being installed, or must I use KVM? In my test so far, I've installed the desktop on top of Ubuntu 18.04 server using this one command: sudo apt install...

I don't care what method I use as long as it works every time and I can automate it.

Where is the Official Proxmox documentation that addresses the best practice for removing old kernels? So far, none of the posts I've read (in the forum) satisfy me regarding this topic. Partly, this dissatisfaction is due to the fact that different posters are suggesting different practices...

In Proxmox 5.1-41, after switching a Windows 2012 VM's Network Device from E1000 to VirtIO (and installing the latest stable VirtIO drivers), I've had users of physical workstations (that use a client/server application hosted by this virtual machine) say that application performance has been...

Windows 2012 R2 on Proxmox 5.1-36: I'm currently trying to upgrade my Virtio drivers to see if that fixes the issue.

see log attached

We're using Proxmox 4.4-5, and one of our virtual machines (vm 103) stopped during a backup. In the attached log see this line and the others lines around it: Jan 4 23:45:34 proxmox2 vzdump[45375]: ERROR: Backup of VM 103 failed - VM 103 not running Although our NFS share itself had plenty of...

Is it still a security risk to run a docker container inside of an LXC container in Proxmox 4.2-11? If so, this surprises me. I thought LXC containers, well, "contained" the things installed onto them. It therefore surprises me that something installed into a LXC container could so easily gain...

This attached log, shows the same virtual machine being backed up slowly in Proxmox 4.1.

This attached file shows a backup log of when the snapshot-mode backups were fast in Proxmox 3.0.

In Proxmox 3.0, my daily snapshot-mode-backup took 37 minutes to create a 78gig backup file. After installing Proxmox 4.1, this same virtual machine now takes an hour and 40 minutes (1:40:00) to create the same 78gig backup file. When I backup the same virtual machine using stop-mode backup, it...

Typically I can download 63 MB is less than a minute. Take a look at this:

I'm not even clear that it is Proxmox's fault. Could it just be the debian Jessie servers causing this?

No, I'm talking the "Update" button on the tool bar (in Proxmox 4), the one that opens a console in a web-browser-window and you type 'y' to download the updates. That's what's slow.

This last set of updates are downloading quite slow: between 10 to 25 KB/sec (taking over 20 minutes per server). The slowness seems to be server-side, because the local connection is 50mb down and 10mb up, while nothing else on the internet is downloading slow. Its not that big of a deal, but...