Proxmox VE 9.1.1 – Windows Server / SQL Server issues
- Thread starter tigro11
- Start date
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
no, changing FS ( zfs / Lvmthin / btrfs) implies formatting.can i convert to Lvmthin without moving all the vms?
perfect,no, changing FS ( zfs / Lvmthin / btrfs) implies formatting.
Thanks
of course.
it's not really a migrate.
perfect, so I make a backup of the VMs on a NAS, recreate the LVMthin filesystem and then restore the VMs on the new filesystem, right?
we can't confirm each step neither detail each step.
backup as safety , always.
but restore can be skipped :
from Node \ Shell , you can
then "Wipe disk" from PVE UI \ Node \ Disks , the correct disk /!\ , then "Create Thinpool" from Node \ Disks \ Lvm-thin
then moving SQL vdisk to new Storage.
backup as safety , always.
but restore can be skipped :
from Node \ Shell , you can
zpool detach one 1.8TB , this breaks ZFS mirror , but will continue to work , no interruption.then "Wipe disk" from PVE UI \ Node \ Disks , the correct disk /!\ , then "Create Thinpool" from Node \ Disks \ Lvm-thin
then moving SQL vdisk to new Storage.
Hi,
I have exactly the same issue, and my setup is close to your and I also use zfs. Fresh Proxmox 9.1.1 installation, with VMs migrated from ESXi 8, where everything was working perfectly.
My VMs are two Windows Server 2019 machines (one RDS, one database server), fully up to date and optimized for Proxmox.
After a few hours of use, users report a minimum 10-second latency that appeared after the migration, directly inside the application — whether accessed via RDS or directly on the database server.
We did not have this latency before, so it clearly comes from Proxmox. After many unsuccessful tests, here is what I ended up doing:
Hopefully this can help you
PS: I should have expected Proxmox 9 to be unstable with Windows. For example, when uploading a Windows ISO via the web interface, the file gets corrupted — I had to upload it via SSH instead.
PS2: This post was corrected and rewritten with ChatGPT.
I have exactly the same issue, and my setup is close to your and I also use zfs. Fresh Proxmox 9.1.1 installation, with VMs migrated from ESXi 8, where everything was working perfectly.
My VMs are two Windows Server 2019 machines (one RDS, one database server), fully up to date and optimized for Proxmox.
After a few hours of use, users report a minimum 10-second latency that appeared after the migration, directly inside the application — whether accessed via RDS or directly on the database server.
We did not have this latency before, so it clearly comes from Proxmox. After many unsuccessful tests, here is what I ended up doing:
- Downgraded VirtIO drivers from 285 to 271
- Downgraded QEMU from 10.1 to 9.2
- Downgraded Proxmox by reinstalling from 9.1.1 to 8.4.16
Hopefully this can help you
PS: I should have expected Proxmox 9 to be unstable with Windows. For example, when uploading a Windows ISO via the web interface, the file gets corrupted — I had to upload it via SSH instead.
PS2: This post was corrected and rewritten with ChatGPT.
Last edited:
What CPU emulation did you use? There are plenty of threads about not using "host" and/or discussing CPU virtualization flags at least in newer Windows versions, for example thread https://forum.proxmox.com/threads/e...nce-10-gbit-virtio-speeds.179064/#post-830582
I used x86-64-v2-AES then host (XEON GOLD 5515+)What CPU emulation did you use? There are plenty of threads about not using "host" and/or discussing CPU virtualization flags at least in newer Windows versions, for example thread https://forum.proxmox.com/threads/esxi-→-proxmox-migration-host-cpu-vs-x86-64-v4-aes-performance-10-gbit-virtio-speeds.179064/#post-830582
This setting didn't improve sql response time but I keept "host" as setting