Search results

  1. B

    Some VMs fail to start after upgrading to 5.15.74-1-pve

    That worked this VM config boots now root@hv01:~# qm config 7001 agent: 1 balloon: 1024 bios: ovmf boot: order=scsi0;net0;ide0 cores: 2 cpu: host efidisk0: ssd-tank:7001/vm-7001-disk-0.raw,size=128K machine: pc-i440fx-6.0 memory: 4096 name: WC-DC01 net0: virtio=92:A9:D7:25:23:98,bridge=vmbr0...
  2. B

    Some VMs fail to start after upgrading to 5.15.74-1-pve

    No boot / gets windows failed to start dialog repair options etc root@hv01:~# qm config 7001 agent: 1 balloon: 1024 bios: ovmf boot: order=scsi0;net0;ide0 cores: 2 cpu: host efidisk0: ssd-tank:7001/vm-7001-disk-0.raw,size=128K machine: pc-i440fx-6.0 memory: 4096 name: WC-DC01 net0...
  3. B

    Some VMs fail to start after upgrading to 5.15.74-1-pve

    Had to do the same thing to get my Windows Domain Controllers to boot (Active Directory turns off caching on disk in the OS). Using VirtIO single with iothread checked. Had to uncheck to boot as blk_set_enable_write_cache: Assertion `qemu_in_main_thread()' failed was logging when trying to boot...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!