Search results

ok, maybe you could avoid the warning when you are using adduser --system --no-create-home tss internally

Thanks for the fast fix. There is still an issue: Warning: The home dir /var/lib/tpm you specified can't be accessed: No such file or directory Adding system user `tss' (UID 111) ... Adding new user `tss' (UID 111) with group `tss' ... Not creating home directory `/var/lib/tpm'.

The required packages are already published in the community repo, but there seems to be a issue in it: You need to call upgrade twice as the first call is failing, see below (care: there are two calls to upgrade within it): account@host:~$ sudo apt-get update && sudo apt-get -V dist-upgrade...

Hi all, I want to create a backup of our a VM on a existing Thinpool. As it is only a temporary backup before an upgrade of the VM (and we have an external backup job as well) it is okay when the backup is on the same machine as the VM itself (as I don't know where Proxmox is storing snapshots...

What is is the opposite of this? So I can add a `post-down` event?

Thanks, this works :)

Hi all, I had to setup a fresh installation of Proxmox. As we don't have enough IPv4 adresses, we had used a NAT on our old installation. But this works now only partially. I can connect from outide to my VM via port 20222, but the VM can't reach any internet adress (e.g. for updating the...

Well thank you. Before I could store remaining VMs with DD the RAID destroyed itself completely be losing partition data. Nevertheless thank you :-)

Hi all, we have currently some hardware issues with out server (1 defect HDD and 1 HDD which only works for a limited time in a RAID5 :-/). Because of this the filesystem got some issues. Now I can login into the system via ssh, but the Web-GUI doesn't responds anymore. As I can still access...

Our Proxmox system contains currently one small SDD and a bigger HDD. Now I created a container on SDD. Is it possible to add another virtual hard disk (on HDD) to a container or is it only possible using a VM?

I tried two different settings: First try (installed virtio driver during installtion): - HDD: VirtioIO - Network: VirtioIO - Processor: default (kvm64) - Memory: Dynamic Size Second try (without additional driver): - HDD: IDE/SATA - Network: Realtek - Processor: Ivy Bridge/host (host = Xeon...

Not sure where to report bugs, so I'm doing it here. With Proxmox 4.4 & 5.0b2 it is not possible to run "Capturing Reality"* in a Windows VM (tried it with Win10, 8.1 and 7). If I start this software the licence windows need ~30min until it appears. So I'm not able to activate a free trial...

Found the issue when host is crashing: Combining GPU passthrough with RAM balloning seems to be broken. Our system has 128GB memory. I have enabled balloning with 4GB at minimum and 128GB at maximum, so the VM can use all free memory. Without GPU passthrough Windows starts. With GPU passthrough...

I currently trying to passthrough a GPU to my VM. System: - Intel Xeon 2630v2 (no embedded GPU) - 2x Nvidia 770 GTX I performed a fresh installaion of proxmox 4.4 and followed this guide. If I now start a VM with GPU passthrough host is always crashing (even with a fresh created VM at first...