Search results

  1. weehooey-bh

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    These VMs will not boot/reboot at all now? I do not believe anyone has experienced that. It may be a different issue. This issue is usually a stuck VM, power it off, power up and it boots without issue. After that, VM will reboot normally. One of the interesting things seems like it only...
  2. weehooey-bh

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    @Jonathan Hankins That is an interesting idea to Live Migrate it. Definitely will try that. Have you had any VMs hang more than once?
  3. weehooey-bh

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    Has anyone had the exact same VM stuck twice? I am asking because we purposely have left VMs running for extended periods of time (up to 65 days) without rebooting to attempt to learn about this issue. These are VMs that have experienced the problem in the past. There were on the exact same PVE...
  4. weehooey-bh

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    @vulture What do you need to do to get the test VM to hang? Asking because, after a hang, it seems to take a while before the same VM will hang again. Do you have to leave it for X days? Or is there something you can do to trigger it?
  5. weehooey-bh

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    Hey @Emilien Sure we can try that. One of the VMs that froze has been changed to cpu: host. Some of these VMs have been running on the same hardware for over two years and only switched to cpu: Westmere about a year ago. This same cluster was only updated to 7.x this year when the hanging...
  6. weehooey-bh

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    @Whatever thanks for adding to the data. Some additional information we have found: - It is affecting both HA and non-HA VMs - When a VM is booting, at some point the PVE console window resizes (when the OS and hardware agree on resolution?). The hang happens before the console resizes.
  7. weehooey-bh

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    What we have learned so far from our research and compiled from others in this forum post: - Windows does not report anything in bootlog (ntbtlog.txt) -- suggests issue happens very early in the boot process - Windows Server version does not appear to affect it -- 2016 to 2022 affected - Only...
  8. weehooey-bh

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    We are seeing the same behaviour since upgrading to 7.x. At first, we thought it was Windows Updates because they always break and you usually only reboot a Windows Server if you are applying updates. A sample of the machines that have hung: Windows Server 2019 Datacenter (1809) agent: 1...
  9. weehooey-bh

    Starting VM While Backup Running

    Thanks. At what point is it safe to start (resume) without fear of backing up the booting version of the drive? What if there are two drives?
  10. weehooey-bh

    Starting VM While Backup Running

    Just noticed something... the "Start" button has changed to "Resume". I suspect that once the dirty-bitmap has been taken, the "image" has been frozen and it is safe to start. It would be great to get confirmation if that is the case.
  11. weehooey-bh

    Starting VM While Backup Running

    We would like to power on a VM after starting a backup. When is it safe to do that if we want a clean backup of the VM's drive (assuming only one drive)? We have a VM with an old database on it. We prefer to backup the VM with it powered off to avoid any corruption of the old database. It...
  12. weehooey-bh

    VE 7.0-11: OVS Bond/Bridge/Ports disabled/failing after server reboot

    Did you get your issue resolved? I am wondering because we are having some issues with a fresh PVE 7 install and getting OVS to work. Perhaps your solution would assist us.
  13. weehooey-bh

    [SOLVED] Proxmox Backup Server and PVE Migration Network

    Thanks for the info. Makes sense that would be the approach. Have you implemented this or something similar?
  14. weehooey-bh

    [SOLVED] Proxmox Backup Server and PVE Migration Network

    Would the Proxmox Backup Server (PBS) work on the migration (backup) network if that is configured for the PVE cluster? Rather than use the main network connection for the cluster nodes, we would like to offload the backup traffic. Would we add a second interface and put it on the PVE...
  15. weehooey-bh

    Getting tons of (broken pipes) now on Backups.

    Found the issue. There was enough physical space but someone put a quota on the parent folder. Exceeding the quota did not show up until the next day.
  16. weehooey-bh

    Getting tons of (broken pipes) now on Backups.

    Part of scheduled backup: Manual backup:
  17. weehooey-bh

    Getting tons of (broken pipes) now on Backups.

    Except, it is not full. As further confirmation, we can manually run the backup to the same location without an error.
  18. weehooey-bh

    Getting tons of (broken pipes) now on Backups.

    We are experiencing a similar issue the backup location is Cephfs. Running the individual VM backups they work fine. It is only when they are run part of the scheduled backup do some of them fail with: How would we tell if the issue is that the storage or network is overloaded?
  19. weehooey-bh

    LXC container reboot fails - LXC becomes unusable

    @seneca214 two things: After updating the ip6tables, we do not seem to be having the issue. We are having trouble getting the ip6tables changes to stick after a reboot. Usually, we use ip6tables-save but none of the file names/locations seem to work. Thinking it was the Proxmox firewall, I...