Search results

Try typing ENTER into the console. Usually this happens when the log in prompt does not get properly redrawn, sending ENTER to the container should trigger that.

Could you post the config of the affected VM in its entirety? That would be helpful to see if some other options may interfere here. Please provide the output of the following two commands: qm config <VMID> and qm showcmd <VMID>, replace <VMID> with the ID of an affected VM. Thanks!

Yeah sorry, so far nobody has taken up this issue yet (it also impacts other issues, outlined here [1]). We have discussed on how we could solve this, but this would require major changes on how we handle UPIDs and would possibly impact other products as well. So a fix is likely still a while...

You can read about the different types in the documentation [1]. [1]: https://pbs.proxmox.com/docs/technical-overview.html#change-detection-mode-for-file-based-backups

As far as I understand it, it is a linked library of the process that runs the VMs. So it will be loaded at runtime. To my understanding this means, yes you will need to re-start the VM process. Or in other words, restarting the VMs that use TPMs need to restart at least those VMs.

You probably need to restart at least the affected VMs for this change to be effective.

This is probably a little confusing, but this is meant as proxmox-backup-manager disk zpool list. I guess it was assumed that from context that would be clear and that you don't need the somewhat convoluted “proxmox-backup-manager” in-front of every command in the text. For just reporting bugs...

The command you ran also unset the option iothread. Meaning the default would apply again, and the default is to turn it off. Turning that feature on and off requires a VM restart. Hence, your changes did not apply immediately.

It shows up now for me ;) takes a little while to sync if I remember correctly. Community subscriptions should be enough :)

So all of these are related to the windows versions that the backend expects: wxp is “Microsoft Windows”, Version “XP/2003” w2k is “Microsoft Windows”, Version “2000” w2k8 is “Microsoft Windows”, Version “Vista/2008” win7 is “Microsoft Windows”, Version “7/2008r2” win8 is “Microsoft Windows”...

Thanks, Johannes, for the pointer, I updated my original answer to be relevant to PMG, the short answer is that yes PMG HA should also work with only two nodes. The clustering algorithm in PMG is fairly different from PVE.

Sorry just realized this is about PMG, yes a two node cluster is supported with PMG. HA should work fine, but you might need to carry out a manual recovery to get full functionality back in case of a full disk failure on a node. See the documentation [2]. [2]...

Depending on your setup, you could also just try to disable those protections for your Proxmox VE host. Unless you can't trust the person running the instance (in which case, why can you edit files /usr/share?) there should not be much of a privacy concern there. We don't do any telemetry...

Your solution will probably reset if the respective file or package gets updated. The easier way to do this, is to set your browser (and/or maybe OS) to always prefer dark mode. The UI should respect that by default, so you don't need to modify Proxmox VE at all. Firefox has this setting under...

What is the file system of the VM you created a backup from? There are known limitations of restoring files from proprietary file systems such as NTFS and ReFS. There was also a bug in the file restore UI that might prevent the file restore window from opening, you might need to apply the...

Hm that would be a bit tricky, as we always have at least two realms available, and we can't know which one the user wants to use when logging in, before they've selected it. If we were to redirect them right away, but they don't want to use the OpenID realm, there would be no way to overrule...

Again, the manufacturer of the storage might supply a plugin that can do that, but we currently don't offer a first-party solution for this problem, yes. There is a more detailed overview of how to deal with this situation over in our Wiki [1]. [1]...

The storage is marked as is_mountpoint, which means that it needs to be mounted before Proxmox VE can use it as a storage. You can achieve that adding an entry to your /etc/fstab or adding a mount unit. Either way, I'd suggest you check out how that storage is mounted on the original node and...

This currently isn't an option unless your FC SAN has a specific storage plugin in for Proxmox VE that you could use. LVM-thin's approach is sadly not really compatible with shared storages and LVM itself has not proper support for efficient snapshots. One workaround could be you use your SAN...

You do get to decide what is and is not offensive to you, but I get to decide what is and isn't appropriate speech and tone for discussions here and this: is decidedly not appropriate. Especially after the only thing that was pointed out to you was that the manual and Wiki explicitly discourage...