Search results

Hi, What says the output `pvecm status` when only 3 nodes are online? Could you also please provide us with the output of `pveceph status` command.

Do you have a firewall? if yes, could you please temporarily disable it? May you share with us also the output of `ip a` and the network configuration of the Proxmox VE `cat /etc/network/interfaces`.

Okay now could you temporary disable the `split lock` in your Proxmox VE host [0] and see if that fix the issue? Since I see the following in the syslog you've provided when you start the VM: Feb 12 15:40:02 proxmox pvedaemon[90429]: <root@pam> end task...

Thank you for the log! May you try to set the CPU of the 105 VM as `Host`?

Could you please share the VM config and the syslog during the VM start to see if there is anything interesting? What the VM OS Linux or Windows?

You may check the `traceroute` from both clusters. this should give more information.

Could you please check the timedatectl and the `systemctl status chrony` command to see if crony service is installed and active?

Hi, Hard to say without checking the syslog during the time of the failure. Could you please post the syslog?

Hi, Have you checked the syslog during the backup time? Do you see any high I/O during the backup?

Hi, Could you please provide us the test ping of `download.proxmox.com`. Did you edit the `/etc/hosts` file?

Thank you for the syslog and the VM config! It looks like the PCI device is fail to passthrough, could you please check the IOMMU groups to see if all related devices are passed to the VM? find /sys/kernel/iommu_groups/ -type l I would also try to disable power saving by adding...

Yes, exactly! you want traffic from the outside arriving on the physical NIC `enp2s0` to get forwarded into your VM. Also make sure that there is no firewall on both Windows and your PVE.

Ah, when i re-check the network configuration I see post-up iptables -t nat -A POSTROUTING -s '192.168.1.1/24' -o vmbr0 -j MASQUERADE post-down iptables -t nat -D POSTROUTING -s '192.168.1.1/24' -o vmbr0 -j MASQUERADE Could you try set `enp2s0` instead of `vmbr0` i.e.: post-up iptables -t nat...

Can you chekc if you can ping 8.8.8.8 from the Windows VM? If that works, then NAT is fine, but your DNS might be off. In that case, try setting your DNS server in Windows to something like 8.8.8.8 or the same DNS you have on your PVE in `/etc/resolv.conf`.

Ok just update the network config in your Proxmox VE `/etc/network/interfaces` as the following, (You may have to edit the private IP in the `vmbr0` to 192.168.x.x instead). After you modified the configuration run the `ifreload -a` command to apply the config. # network interface settings...

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.