Mitel Connect and Proxmox

[DH28]

We have a Mitel Connect HQ (phone system) server running on Windows. It was migrated from VMware to Proxmox and is currently working fine on a Proxmox 9.1.1 cluster.

When we try to migrate the same setup (or do a fresh install) onto Proxmox 9.1.6, the TMS and IPDS services crash immediately on the Mitel HQ server. It happens right away after the services start.

I can’t find any obvious differences between the Proxmox 9.1.1 and 9.1.6 environments. I’m not sure Proxmox is actually the cause, but Mitel support says Proxmox isn’t officially supported. That said, Mitel appears to run fine on our current Proxmox cluster (9.1.1).

Has anyone seen a similar issue when moving Mitel Connect HQ to a different Proxmox version, particularly with TMS/IPDS crashing immediately?

Thanks in advance for your thoughts,

Don

 

[news]

and may be you can show your vm config?

 

[DH28]

The first system works as expected.
BIOS SeaBIOS
Memory 16 DiB
Processors 4 (1 socket)
SCSI Controller Virtio
Hard Drive SSD-NFS
Network virtio

The second was a simple migration to the New SAN. So the same config.

BIOS SeaBIOS
Memory 16 DiB
Processors 4 (1 socket)
SCSI Controller Virtio
Hard Drive SSD
Network virtio

Also attempted a complete new install OS (2019) Mitel Connect. Get same result staring the services as the migrated server. Again may not have anything to do with Proxmox.

 

[alexskysilk]

The first system works as expected.
BIOS SeaBIOS
Memory 16 DiB
Processors 4 (1 socket)
SCSI Controller Virtio
Hard Drive SSD-NFS
Network virtio

The second was a simple migration to the New SAN. So the same config.

BIOS SeaBIOS
Memory 16 DiB
Processors 4 (1 socket)
SCSI Controller Virtio
Hard Drive SSD
Network virtio

Also attempted a complete new install OS (2019) Mitel Connect. Get same result staring the services as the migrated server. Again may not have anything to do with Proxmox.

The only thing I can think of is vcpu configuration. on a modern windows guest you really want to set it to x86_64_V3 or better. Avoid host without tuning, and QEMU/earlier X86_64 variants can have missing cpu features.