Search results

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...

@andrewrf for all the VMs that have hung, are you seeing the following: Only Windows VMs, Server 2012 or later Windows does not report anything in bootlog (ntbtlog.txt) -- meaning it had not got far enough in booting to start that logging Only hangs on a reboot and only if the VM has been...

@Moayad Here is the same data from another hung VM. It is the "classic" black screen, Windows logo and endlessly spinning balls. Power off (Stop) the VM, power on and it started normally.

@tom No one that we are aware of has reported "Getting Windows Ready". That is a different problem. Has anyone reviewed the information we provided that was requested by @Moayad ?

I have posted a link in the bug report to the data we captured: https://bugzilla.proxmox.com/show_bug.cgi?id=3933

Hi @Moayad please see the attached files. This VM is currently hung. We can leave it for an hour or two before it needs to get it back into production. Please let us know ASAP if there is something we can do further. A few notes: This is the first time we have seen a screen like this...

@itNGO are all the VMs that repeatedly freeze using version 6.0 or later of i440fx? # qm showcmd <vmid> --pretty | grep machine -machine 'type=pc-i440fx-6.1+pve0' \ I noticed that in your video. Also, in PVE Roadmap I noticed under 6.4: Support pinning a VM to a specific QEMU machine...

Hey @tstrand have you had this issue recently? If so, was it the same VMs or different ones?

Hey @itNGO thanks for the video. Most of our VMs were built in PVE and have only experienced the hang once each (that we know of). I just rebooted one that had 49 days of uptime and it rebooted fine. It had been one of the ones that had a problem earlier. Earlier today, rebooted another one...

@itNGO how do you reproduce it? We have some VMs too but have not found a way to reproduce the hang.