Search results

This suggests you have an issue with your networking. What is your network config on each node?

Your management interface does not need to be on a VLAN. The recommendation is to keep it isolated from guest traffic. Consider it privileged traffic. If you would like to isolate using VLANs, that is okay. Please post your entire network configuration.

I am unsure if this relates to your EVPN and IPv6 issues, but we found that the SDN VXLAN does not support IPv6 peers. We have submitted a bug report: https://bugzilla.proxmox.com/show_bug.cgi?id=5398

Ah! That is much clearer. Thank you for the additional info. I would do something like the following -- keeping in mind that I only know what you have provided, and there are likely things about your environment that I do not know. You will need to decide how to use this information. One port...

Hi @babis430 We may have some confusion. My understanding from your original post is you presented eight vNICs from your UCS fabric interconnect to the blade server. eno1 eno2 eno3 eno4 ens210 ens211 ens610 ens611 Is this correct? Are these 10 Gbps connections? Also, I believe you said your...

If you have adequate backups, save yourself the trouble of upgrading and do a fresh install right to PVE 8.x

If you are delivering all traffic to the blade tagged, you will need to create a tagged interface for the management VLAN. The PVE Network docs explain: https://pve.proxmox.com/wiki/Network_Configuration If the traffic is untagged but on the wrong NIC, use the console to switch it in the...

On a Cisco UCS, you will not use or need LACP for the bonds. Look at something like “balance-alb”. Each of the four LAG member ports will go into a bond together. For example, if enoX are in a LAG and ensX are in a LAG, enoX will go to bond0 and ensX will go to bond1. If all your traffic is...

The vzdump backup will include any data in the VM that has been written to disk. The backup does not guarantee consistency for things like databases which may still have data in memory. The backup will be a single file on your NAS that can be restored to another PVE installation. Having the...

VM restores are full restores and will overwrite the previously restored VM. It will provide the same result as deleting the previous restore and then doing the new restore. The restore will take the full amount of time as all the data is restored.

Hi Steve You only will use `eno1` and `vmbr0` with VLAN tags. The PVE networking docs have everything you need: https://pve.proxmox.com/wiki/Network_Configuration

@David Herselman, this has been around for a long while. It appears to have been fixed in Debian, and we should see it soon... if I understand the Debian bug reports: Debian bug report 1008684 I think this means the fix has been accepted...

We just saw this issue with Windows Server 2022 and the most recent version of PVE (updated to be sure). The VM would not boot with the memory hotplug enabled. It would get to "guest has not initialized the display (yet)" and hang. Disabling the memory hot plug and it booted. During testing...

@wolfgang5505 Please review this thread carefully and the bug report related to it (link in thread). It is unlikely you are experiencing this problem with 6.4. You likely have a different issue. After you review and confirm you are having the same issue, then you should post detailed...

@dea we have experienced this on Lenovo and HP servers.

@mira regarding the snapshots, the most recent comment in the bug report seems to cover that: https://bugzilla.proxmox.com/show_bug.cgi?id=3933 @mira from our experience it is over 30 days. However, we only recently have had it happen multiple times to the same VM. Others with previous posts...

@dea until this week, we did not have any VMs that had this happen to more than once. Including those running for a long time (over 60 days) without a reboot. It was appearing that once it happened to a VM, it would not happen again. This was across multiple clusters and sites. To be clear...

@Moayad any update would be appreciated. We had been suspecting that the hung boot was only happening to each VM only once (at least in our situation). Unfortunately, this Patch Tuesday has led to a fresh round of hanging VMs.

@Huch this post is about VMs getting stuck when rebooting (mostly Windows). No one else has reported slowness related to this issue. You might have a different issue or two separate problems.

@itNGO It is interesting that you are seeing it on Ubuntu 20.04. Not many people are seeing this. Looking back over previous posts, you just get a black screen. What is happening with your VMs seems to be slightly different. I wonder if there is a clue in that. Would you share some details...