Search results

In my original response I said I used this guide. That includes running: blnsvr.exe -i

Task manager in windows shows 3.4 GB used. # free -h total used free shared buff/cache available Mem: 376G 128G 29G 149M 218G 245G But free -h shows total for the proxmox server. The Summary tab in the proxmox...

At the moment the Task Manager in windows says 3.3GB used Proxmox says 11.1GB used

Thank you for the suggestion but yes I did do the install. I used this as a guide: https://pve.proxmox.com/wiki/Dynamic_Memory_Management

I have a fresh install of proxmox pve-manager/5.1-43/bdb08029 (running kernel: 4.13.13-5-pve) I have installed memory balloon drivers 07/19/2017 61.74.104.14100 The ram reported in the OS does not match the RAM reported from the proxmox console. Any Ideas?

I am running a fresh install of 5.1-43 When I look at the hardware tab of a KVM it is missing these sections: -Hard drive -DC -Network Device I have found a way to temporarily fix this by clicking "CPU Options" then cancel. After that those items appear in the list.

We are currently having issues backing up just one VM on our Proxmox server. We are using the backup function in the web interface. All other backups work as expected. The following is the output from the task viewer output: INFO: starting new backup job: vzdump 510 --quiet 1 --mode snapshot...

I hate to say that it was a firewall issue. I have multiple internet providers and switched to a different gateway and then it started working. A needed port must have been blocked in the other one. Thanks fireon. It did break my zfsonlinux installation, and I had to remove and re-install that...

I have seen some talk abou this but wouldn't know what <key> to use. Some people with problems like this have errors stating what the <key> is. This is a listing of my keys on that machine: # apt-key list /etc/apt/trusted.gpg -------------------- pub 1024D/9887F95A 2008-10-28 uid...

when I try to update with apt-get update I get this error: E: GPG error: http://security.debian.org wheezy/updates Release: The following signatures were invalid: NODATA 1 NODATA 2 I have verified sources.list and read many articals on GPG keys but can't locate the problem # cat...

This was a lot of help, however I found there was a little more than those commands and I'm running the current version of MaxView. These are the complete set of commands that worked for me. the above instruction move the libssl.so.1.0.0 file but link the libcrypto.so.1.0.0 file. I guessed that...