Search results

Proxmox VE does not install auditd by default. If you want to use it, you should install it via apt install auditd. The message you see come from some other part of the kernel using a related mechanism to limit the amount of log messages. By default, the Linux kernel is configured so that the...

Depends, both are not stable releases at this point, so there aren't many guarantees about what will and will not work. That being said, in general the Proxmox VE API is fairly stable and there this should work at least in theory. Please note though, that you should use neither in production at...

Danke für die Infos, was sagt denn der Befehl df -h /var/tmp?

Wenn warten eine Option in dem Fall ist, dann ja. Am besten auf der Node mal journalctl -f ausführen während der Upload läuft und dann den Output hier posten. Bitte gerne!

ZFS over iSCSI hilft leider in dem Fall nicht viel, wenn Synology selbst nicht das ZFS anbietet. Leider ist die Benennung hier etwas verwirrend, aber ZFS over iSCSI bedeutet, dass auf einem Host ZFS Volumen via iSCSI an ein PVE Cluster zur Verfügung gestellt werden. Nicht, dass auf einer iSCSI...

Well I think the problem would be that we don't have many French-speakers on staff, so it'd be hard to moderate a French-language forum for us. But this is just my two cents.

Glad to hear that. You could try to debug this further, but to be honest, this is somewhat expected. You can mark this thread as “solved” by clicking the “Edit Thread” button on top and selecting the “Solved” prefix. This helps other user with the same problem find a solution. Thanks!

So I looked into the “CPU Flags” you mention here are “Hyper-V Enlightenments” (hv_spinlocks, hv_reset) [1]. Can you try simply adding this line to your config: args: -cpu...

I think you are just misunderstanding the format here. The documentation [1] here mentions that each flag you want to specify, needs to be prefixed by either a “+” or a “-”. If you prefix the flag with a “+” it will be enabled. If the flag is otherwise enabled, prefixing it with “-” would...

Yes that makes sense, I'm assuming this fixes the issue for you? If so, please mark this thread as solved by adding the “Solved” prefix via the “Edit Thread” menu above. Thanks!

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”...