Search results

Perfect. Basierend auf meinen Infos weiter oben war der Befehl: pvesm set local-enc --is_mountpoint yes Und das Ergebnis ist in /etc/pve/storage.cfg zu sehen: dir: local-enc path /rpool/data/ content backup is_mountpoint yes maxfiles 7 shared 0

Fantastisch. Probier ich nachher gleich mal aus und kommentieren hier! Vielen, vielen Dank!

Das klingt genau nach dem was ich suche. Kannst du mir noch etwas im Detail weiterhelfen? meine /etc/pve/storage.cfg dir: local path /var/lib/vz content iso,vztmpl maxfiles 7 shared 0 zfspool: local-zfs pool rpool/data content images,rootdir...

scheint nicht zu funktionieren. Bei einem Neustart von PX passiert (anscheinend) folgendes: - PX startet, sieht dass es angeblich ein storage mit "directory-type" geben sollte, findet es nicht (da es ein encryptetes dataset ist für welches es noch keinen Schlüssel hat und welches ich noch nicht...

tut mir leid den Thread ge-hijacked zu haben aber meine Fragen passen bislang so schön zu der Frage des ersten Posters. Der Grund für meinen Wunsch nach einem verschlüsselten Dataset ist dass ich 2-3 VMs habe die "at rest" verschlüsselt lagern müßen. Da bitlocker meines Wissens nach nicht für...

AH, jetzt verstehe ich: Schritt 1: Jetzt bootet Proxmox, schaut in das Dataset sieht aber logischerweise nur den leeren Mountpoint. Schritt 2: Dann komme ich und lade manuell den key und mounte daraufhin das Dataset. Schritt 3: Ich starte manuell 1 VM, die schaut nach ihren disks und voila die...

Hi Dominik, das habe ich nicht ganz verstanden. Du sagsts: "pve sollte dann beim starten ganz normal die disks sehen" - aber pve hat doch schon längst gestartet bis ich manuell das PW eingegeben habe und das Dataset gemountet habe. Schau bitte nochmal über meine BEschreibung des Vorganges...

Ich hätte hier mal eine Folgefrage: mal angenommen ich schaffe das, was sich der originale Fragesteller hier vorgenommen hat und verschlüssele ein Dataset welches ich in PRoxmox einbinde und lagere in diesem Dataset VMs welche NICHT auf Autostart stehen. Jetzt bootet Proxmox, schaut in das...

I spoke too soon. Yesterday, after your suggestion, I could move my mouse across the win10 screen and get top the login window. Unfortunately I couldn't get past the welcome screen. After a few reboots, trying different things, I can now again, not get to the login window despite the settings...

YES, YES, YES. that solved it! It was set to VirtIO-GPU - no idea why, it has been a long time since I used this VM but I really needed to regain access! Thank you so much!

THanks for the hint but: - tried another browser per your suggestion without luck - I restarted the guest a couple of times already hoping for the best ;-) - display adapter is and always was vnc. changed it to spice and back to vnc I guess I'll look around for a Win10 rescue / Boot CD and see...

Running a Proxmox Virtual Environment 5.4-13 and have a Win10 Enterprise KVM I can't access. Due to some stupid circumstance, it only has a local IP so is not reachable via internet. I connect to it via browser using the VNC console built into Proxmox, I can see the screen but clicking around...

Thanks for explaining, I now understand the issue a bit better and will know how to proceed or what the problem is if this comes up again :-)

I managed to restore my container by unchecking the "unprivileged container" check box. How do I know if my container used to be privileged or unprivileged? I assumed when restoring it would restore to the same as when the backup was taken? found this thread with a workaround and more...

OK, I just realized that after the failed restore the whole container is missing :-( and when trying to restore again, same error as above.

Running Proxmox 5.3-12 with latest backups. Trying to restore a backup I made a few minutes ago. Here is the log of the restore: extracting archive '/mnt/pve/local-nfs/dump/vzdump-lxc-108-2019_04_10-22_01_01.tar.lzo' tar: ./var/spool/postfix/dev/random: Cannot mknod: Operation not permitted...

I think I might have had a blonde moment. I figured out I made a mistake and had overcommitted my hosts memory so the Windows 10 client might have really been right in that the huge amount of RAM it was showing as "driver locked" was indeed actually used by other VMs and not available hence it...

I assume this is where to get the correct balloon driver: https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/index.html I had previously used the 0.1.141 stable version but will try the 0.1.160 latest version.

Hm, still seeing this problem. memory consumption goes up to 10GB with nothing running. The VM has been assigned 2GB RAM min and 12GB RAM max. Here is a typical scenario. (This is produced by the RAMMap tool fro mSysinternals) - I googled driver locked memory and it seems related to...

would you mind elaborating please? I have used ZFS snapshots before and borg too I am just not sure how to combine those. Please share your solution at least the concept of it.