Search results

Hi, In this case you have to set up a router/NAT for your VM, which means the VM sits behind a private IP like `10.0.0.x` and then Proxmox `masquerades` the traffic out through your public IP as mentioned in the wiki guide. Could you please share the network configuration you used?

Could you share what you did in order to see where the issue was? Is your goal to assign a public IP for the Windows VM or a private IP with NAT in order to reach the VM through Remote Desktop?

Hi, Could you please share the VM config and the syslog when you start the VM? You can get the VM config using `qm config <VMID>` and the syslog during start the VM you can run the `journalctl -f` command and start the VM.

Thank you! To understand the situation (correct me if I not understand correct!). The issue is that your main NIC `enp2s0` has the server's IP, but `vmbr0` is set to `manual` with no `bridge-ports` defined. That means the VM's virtual NIC is essentially `bridged` to nothing... so it can't reach...

Please provide us with the network configuration from the Proxmox VE server `cat /etc/network/interface` and the Windows VM config `qm config <VMID>` as well as the screenshot of the network configuration inside the VM. This can help us identify where is the issue.

Thank you for testing! Could you please run the following command on the `rsthost2` node and provide us with the output? grep -r "192.168.165.22" /etc/ I would also check the the Corosync on which IP uses `rsthost2` node you can run `ss` as the following command: ss -tulpn | grep corosync...

Thank you for the logs, could you please disable the firewall temporary to see if the issue related to the firewall config, especially for the Corosync traffic UDP ports 5404 and 5405.

May you provide us more log entries? And please post the output of `pvecm status`.

Have you restarted the `systemctl restart pveproxy.service pvestatd.service`? Do you still can't SSH to the another node from the hostname even after you modified the /etc/hosts? Could you please provide us with the syslog from the `rsthost2`?

Hi, Maybe you forgot to change the /etc/hosts IP?

Could you tell us which step the VM stuck or did not work after migration?

Hi, Did you read our wiki guide about migrate to Proxmox VE [0]? If you have a specific question, feel free to ask to give you more advice [0] https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE

Hi, How you removed the VMs? Can you try manually remove the unused LVs using `lvremove` command e.,g.: lvremove path/to/VM/del-vm-101-disk-0

Hi, Did you try to do memory tests? you can use Memtest86+ tool.

Did you also check the syslog?

Thank you! Could you please also post the VM config?

Hi, What say the following command from PowerShell? Get-Service QEMU-GA

Hi, Can you please check if the `net.ipv4.ip_forward=1` on the Proxmox VE node? you can run the following command to check: sysctl net.ipv4.ip_forward If not you may have to set it e.g.: sysctl -w net.ipv4.ip_forward=1

Hello, Proxmox VE is based on Debian, this means if your box can run the Ubuntu and Debian the Proxmox VE should run on it. As far as I know the `i5-4590T` supports Intel VT-x, this means the KVM should work as well.

Hi, Maybe the VM runs into a timeout while trying to boot! Please, could you try to boot manually from the CLI: qm start 103 --timeout 600