Search results

Have you already resolved the issue? If not, have you also configured GPU passthrough for the Windows machine? How is the Windows machine configured (e.g. qm config <windows-vmid>? Windows VMs are sometimes very sensitive to changes in hardware and virtualization configuration, so it'd be best...

Welcome to the Proxmox forum, sagiziv3! There are no trivial questions as somebody else might be facing a similar problem, so don't shy away from asking them here. Have you already found a solution? If not, the reason that you can't see the mounted HDD when you're trying to create a LVM...

Welcome to the forum, josh.burry! By default, the login credentials for the Proxmox WebGUI are the same as for the root user that you have set up when installing PVE on your home server. That's why it will tell you root@pam in the user field (PAM is the native authentication module on Linux)...

Guten Morgen! Es ist interessant, dass die Segmentation Faults mittlerweile scheinbar auch auf anderen CPU Cores auftauchen. Es wäre zwar noch interessant zu wissen, welche Cores das von der CPU Topologie genau wären (das kann man sich mit lstopo aus dem Paket hwloc). Soweit ich sehen kann...

I'm sorry that it came across that way, I'm just trying to find a solution to your problem and I haven't fully understood your configuration yet, which lead me to a false conclusion. As far as I understand now, you cannot ping the ESXi host and VMs on the ESXi host from another VM running on the...

It is not possible to clone a cluster by copying the corosync.conf file, as there are many more steps involved in the process of creating a cluster and joining to a cluster, e.g. setting up and sharing SSH keys between each other and correctly configuring corosync in the process. Even if it...

You haven't sent me information about the network interface that is configured on a PVE VM that cannot reach ESXi VMs. But as far as I can see, that since the ESXi VMs can be pinged from the outside (that is, your cluster), the ICMP packets can be routed to the ESXi/PVE VMs fine, but cannot be...

I could not reproduce the issue you described with an ESXi 8.0 host running as a VM on a Proxmox VE 8.2.4 node and trying to: - ping a ESXi VM from a VM running on the same node, - ping a ESXi VM from a VM running on a different node in the cluster, - ping a PVE VM on the same node from a ESXi...

Hey nomadmike! You can import the backups from your previous PVE VMs with the vma-to-pbs utility that is documented at [1]. It is meant to be installed on a PVE node with apt install proxmox-vma-to-pbs, where you can also mount the shared folder from your Windows machine as a SMB/CIFS and then...

How did you write the Proxmox VE installation ISO onto your USB drive? Have you verified the ISO via a sha256sum that is shown on the download page at [1]? If the checksums don't match, the ISO image was somehow corrupted and should be redownloaded. Otherwise, when writing the ISO image onto an...

If nothing else happened (e.g. the VM failed to start/crashed), these are harmless warning messages that are caused when a QEMU guest is trying to write to a register that might be present in the host CPU, but is not exposed to the QEMU guest itself. This can happen for intentional unhandled...

You are still using the Proxmox VE Enterprise Repositories, which are for PVE subscribers that have an active subscription. If you don't have any, you will need to switch to the non-subscription repositories as described at [1]. [1]...

Hey chindajiu! Thank you for the boot log. I've noticed that you're running the Linux kernel version 6.8.4-2, which is unfortunately notorious for instability on many systems as can be seen across the forum, e.g. at [1]. I'd suggest you to do an upgrade of your PVE installation either through...

Could you check if the VM might still be running with qm status 101 and systemctl status 101.scope? It might be that the VM got stuck during a task before (e.g. a backup) and wasn't started again. If it seems to be running, you could try to stop it manually with systemctl restart 101.scope.

Welcome to the forum, junkleybr! Was the Proxmox VE server where the disk failed in a cluster? If so, then the VM configurations are stored distributed on the other nodes and you can recover them from by removing the old node (as described at [1]), setting up a new node (with the VM data disk...

The system log is very short and not helpful for solving the problem. Could you post the boot log and a bit more from the system log? Please ensure to run both as a privileged user (root), as there will be more information that can be helpful to solve the problem. FYI, you should disable...

Hello n7qnm! Have you already found a solution to your problem? If not, it would be helpful to know how you changed the HostKeyAlgorithms on your nodes, as if the settings is too exclusive it could restrict the nodes from sshing into each other and therefore the WebGUI shows the other nodes...

Hey Crash1601! Es tut mir leid zu hören, dass der Fehler zurückgekehrt ist. Ich wollte noch einmal fragen, ob du neben dem BIOS Firmware Update auch die laufenden Microcode Updates von Intel über die Debian Repositories beziehst (wie ich oben beschrieben habe)? Wenn ja, wäre es sinnvoll diese...

You can retrieve the boot log with dmesg > sysboot.log (for information about any warnings/errors when setting up the system). It will be saved into the file sysboot.log. You can retrieve the system log from the last boot with journalctl -b -1 -e. The -b -1 argument tells the journal to output...

Welcome to the forum, chindajiu! If a "crash"/"freeze" means that the server is shutting down or is completely unresponsive, it sounds like a CPU stability issue. In that case, it would be interesting if you've made any changes in the BIOS settings to the CPU and if you've installed the most...