Recent content by aaron

do you mean this: What would be a use case you have in mind? Because there are ways to import disk images in a storage-agnostic way. Integrating special features for a very specific storage would need to have a good use case to warrant the effort of integrating it with Proxmox VE. Ideally...

One more follow up. By having the host part in there as well, it is very clear which subnet is used, when you are not using a /24, but for example a /26. For example with 10.10.20.81/26 as host IP: The result would be that the network ID address would be, 10.10.20.64/26 instead of 10.10.20.0 in...

Yeah, since the CIDR (/24) marks which part of the IP address defines the network, and which the host, it is easy for Ceph to calculate the network part from the configuration.

If you allow me some comment here ;) That classification regarding type1/2 hypervisors is a very strict approach that does not do justice to the nuances that have come up since it was coined back in the 1970s. See this quote from that same wiki article:

That is generally not a great idea as each Proxmox VE cluster will assume it is the sole user of a storage. If you would remove a VM and check the "Destroy unreferenced disks owned by guest" checkbox for example, and have a VM with the same VMID in the other cluster, those virtual disks would...

I assume this is a Linux guest right? If you run ps -auxwf for example, you have the STAT column. If a process is in D state, it is waiting for IO to finish. See man 1 ps in the PROCESS STATE CODES section. If a process is in that state you cannot kill it. Hard to say without taking a very...

If you see 4GiB less of memory in the node summary, then they are used for something else. But Proxmox VE won't be able to use them. So overall, another ~2 GiB of memory used doesn't surprise me too much. Regarding the mismatch of seeing 60GiB of RAM our of the 64 installed: Is there maybe an...

Can you share a few more details? For example, which summary shows 46 GiB? The one in the node summary? Keep in mind that other services on the host also need memory. For example the whole management stack that handles the guests, provides the API and web UI and so forth. So you are likely to...

The Balloon Service is provided by the VirtIO Iso. See https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers for more details.

Is the Balloon Device checkbox active in the VMs Memory configuration (Advanced section)? Is the Balloon Service installed and running in the Windows VM? The Balloon Device is needed to communicate with the VM regarding its memory usage (and therefore enabled by default). For Windows, that...

schau mal obs in /etc/pve/nodes noch Ordner von den alten Nodes gibt. die kannst du sicherheitshalber mal wo anders hin verschieben bevor du sie ganz löscht.

The main issue that happens here is if the backup target (storage, network, ...) is not fast enough to ACK a write. As the backup will halt the write operation of the VM until it got the ACK that this part of the VM disk in question has been written to the backup. So that can lead to slow IO...

A regular Proxmox VE cluster needs the majority of the nodes to be online to be fully functional. With 2/3 nodes down, that is not the case.

well, that is setup that is not officially supported, so there might be some edge cases and we don't have a lot of experience with it. regarding the /run/pve directory: is there a chance that the permissions are not as expected on some level? The /run directory should have the following...

The problem is that this node is part of a cluster, but cannot connect on any of the both networks to the remaining cluster: The result is that the service/protocol for the cluster communication is not working and as a result of this, the Proxmox Cluster File System (pmxcfs), which provides...