All VM's freeze on boot - 8.3

[IT-Invent]

Good morning,

I'm experiencing an issue and after countless searches on google and this forum, I'm unable to resolve it myself.
I have a proxmox 8.3 installation at the office where I prep my servers and everything there works fine (kernel 6.8.12-4)
However, I recently aquired a VDS to host these vm's in production. When I moved a VM to the new host (same kernel, same installation just different CPU) and I booted the VM (ubuntu 22.4) on the VDS, it got stuck on boot at random positions. Sometimes further than other times.
I then deceided to install a new VM on the VDS from scratch using a ubuntu live cd, this had the exact same issue.
Then I though it was maybe a ubuntu issue, I deceided to install a windows server.
Same problem, each time the windows logo pops-up to enter the setup, it freezes immediatly.

Logs do not show any issue or error so I'm unsure where to look further although I'm guessins that it's a problem on the VDS.
I already re-installed the master image on the VDS but the problem remains.

VDS specs:

CPU:
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          40 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   6
  On-line CPU(s) list:    0-5
Vendor ID:                AuthenticAMD
  BIOS Vendor ID:         QEMU
  Model name:             AMD EPYC 7282 16-Core Processor
    BIOS Model name:      pc-i440fx-5.2  CPU @ 2.0GHz
    BIOS CPU family:      1
    CPU family:           23
    Model:                49
    Thread(s) per core:   2
    Core(s) per socket:   3
    Socket(s):            1
    Stepping:             0

I'm not sure if VM info is needed but here's the windows mache info:

root@vmi2289583:~# cat /etc/pve/qemu-server/100.conf 
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
efidisk0: local:100/vm-100-disk-0.vmdk,efitype=4m,pre-enrolled-keys=1,size=528K
ide2: local:iso/26100.1.240331-1435.ge_release_SERVER_EVAL_x64FRE_en-us.iso,media=cdrom,size=5183590K
machine: pc-i440fx-9.0
memory: 2048
meta: creation-qemu=9.0.2,ctime=1732608017
name: test
net0: virtio=BC:24:11:FC:B3:4C,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsi0: local:100/vm-100-disk-1.vmdk,size=80G
smbios1: uuid=11cc8f91-e0ba-446d-9744-6830e11d1a6f
sockets: 1
tpmstate0: local:100/vm-100-disk-2.raw,size=4M,version=v2.0
vmgenid: 68d9f9b1-ae80-46e8-82d3-b9d595d3e773

 

[IT-Invent]

anyone has any pointers?

 

[IT-Invent]

Addendum, created a new VM, installing linux, same issue, the boot stops and it show me <TASK></TASK> instructions?

 

[VictorSTS]

It's unclear to me: are you trying to run nested virtualization with a rented VPS?
VPS -> PVE -> VMs with issues?

If this is the case, whether the PVE VMs work or not fully depend on how that VPS is configured and how the underlying hardware is configured.

 

[IT-Invent]

It's unclear to me: are you trying to run nested virtualization with a rented VPS?
VPS -> PVE -> VMs with issues?

If this is the case, whether the PVE VMs work or not fully depend on how that VPS is configured and how the underlying hardware is configured.

it's a fully separated virtual server indeed but the it's provided by the hosting company, according to them, it should work without issues.

 

[VictorSTS]

It obviosly doesn't There are too many moving parts here to pinpoint what could be the problem. I recommend that you find a provider that can rent a bare metal server, install your own PVE on it and run your VMs.