Search results

Proxmox tries to allocate only as much as RAM as a VM currently needs through the help of the ballooning driver. While Linux has them by default, and Windows needs them to be installed through the Qemu Guest driver, I couldn't find much info whether there are any (native) ones for Mac OS...

According to the Windows guest the CPU usage seems quite normal. Is this a fresh Windows install? Did you see a sudden increase in CPU utilization with this VM or is it always using this amount of system resources? Your htop output suggests that the KVM thread for this machine uses about 45%...

Die einfachste Variante wäre wohl die Ausgabe simpel in eine Variable zu speichern, das würde dann in etwa so aussehen: output="$(megaclisas-status)" pvesh set /nodes/<node>/config -description $output Ich habe megaclisas-status noch nicht verwendet gehe aber einmal davon aus dass dieses...

While it is not recommended to run Proxmox with mixed versions, you should be able to safely do so as long as you need for the update. The usual approach here is to add the 7.2 node to the cluster, migrate all VMs and containers from an existing node to the new node. After the node does not have...

Well due to the problem being rather elusive, I'm not sure whether there is a direct way of testing this. I guess all you can do for now is to wait and see, and occasionally check the logs...

It is supposed to be there. This is called a Logical AND assignment (&&=), your problem is most likely an out-of-date browser. The &&= parameter was added, for example, in Chromium version 85 and Firefox version 79 Could please tell me what Browser you are using and which version you are...

2 Möglichkeiten: Über die API --> https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/config Über die PVE Shell Die pvesh funktioniert ähnlich wie die API, du kannst sie auf die "gleiche" Art ansprechen. Beispielkommando um Hinweise bzw. eine Beschreibung einzufügen: pvesh set...

Hi Spiro! According to this thread these messages do not pose any threat to your system, they "just should not happen". Still, if you follow the link that Dominic suggested, it seems somebody else was able to resolve this by running pvecm updatecerts.

SMART overall-health self-assessment test result: PASSED seems to imply that your device is healthy. Though, when I run smartctl locally there are a lot more entries after === START OF SMART DATA SECTION ===. Especially entries after Error Information might be of note here. Did you accidentally...

You are right, this very much sounds like a problem with your device. Please run smartctl -a <device>, this should be able to tell you if something is wrong.

This sounds like the backup job is stopped by your system for some reason, perhaps the OOM Killer? You could try to monitor memory/system resource usage during the backup, are there any abnormalities? Still, some more information would be nice. Please attach your VM config qm config <vmid>...

Es gibt das PiMox Projekt für Proxmox auf dem Raspberry. Installation aber natürlich auf eigene Gefahr ;)

Sorry, I was thrown off by the picture you included because that looked like non-quorate cluster behaviour to me. I could reproduce the same problem you were facing myself. It seems to stem from trying to rename a node that contains guests. The pmxcfs (manages the /etc/pve directory) does not...

Renaming a node in a cluster can be a bit finicky, it seems you forgot to change the corosync config which is linked at the very bottom of the renaming a node page. The problems you are experiencing here are most likely from the desynchronized corosync configurations. Following the steps...

Are you accessing the website via http or https? Usually this problem occurs because the server sends an empty message when accessed via http. What happens when you explicitly type https before your url?

If you want to support Proxmox directly and want to help keep it Free and Open-Source then hop on over to https://www.proxmox.com/en/proxmox-ve/pricing and check out the different options. ;) A subscription also comes with some benefits of course. For example, access to the stabler and more...

I take it you mean e.g. an option in the GUI to filter which VMs to display in the Datacenter / per node? If you encounter a bug or want to suggest a feature you can always do that over at https://bugzilla.proxmox.com/ I found two reports that relate to VM sorting in the GUI: Sorting of the...

This is actually intended behaviour in the sense that it is trying to tell you that this is something that you really should not be doing. While running a privileged containers puts your host system at risk, this risk is worsened by making the container nested. Enabling nesting, like you stated...

Wow this is quite the rabbit hole. From what I could gather it seems that development of the qemu-guest agent started around mid 2011, at which point Debian Lenny was already superseded by Debian Squeeze. I could find neither release nor source for any qemu-guest-agent packages from around this...

If you want to automate this you can put the script in the common startup folder accessible via WinKey + R and typing shell:common startup This should run for every user once they login.