vm disk type - can i change it?

dirtydevver

New Member
Sep 13, 2024
6
0
1
so i followed some videos that said choose "virtio block" as the disk type but now im reading that the latest versions i should have left it on "SCSI" for hard disk and the scsi controller as "virtio scsi single"

unfortunately i built a few windows servers and already configured them before i realised this and was wondering if there was a correct way to change this after the event, all attempts of adding a dummy drive and attaching and swapping over has led to blue screen of death.

i also went down a big rabbithole and done alot of hdd bench marking with different settings and noticed that when cache is left as default on windows even with local ssd's performance is so bad, even when same hardware was being used by hyper v. i noticed that changing this to writeback improved it alot, and its almost as good as hyper v now which i can live with. if there are any other settings i need to tweak then please let me know
 
unfortunately i built a few windows servers and already configured them before i realised this and was wondering if there was a correct way to change this after the event, all attempts of adding a dummy drive and attaching and swapping over has led to blue screen of death.
When the VM is turned off, you can detach the virtual disk and attach it again as SCSI via the Proxmox web GUI. Make sure to install the VirtIO SCSI driver first. If this gives you problems, you can detach it again and re-attach it as VirtIO Block again.
See also the Windows VM best practices for Proxmox.
 
  • Like
Reactions: UdoB
doesnt seem to work, so thought id share my setup incase there is something super obvious im missing

this is what its like when it works
virtio block Screenshot 2025-01-28 105426.jpg
so i remove hdd and then re-add it with hard disk (scsi0)
scsi Screenshot 2025-01-28 105658.jpg
i then update the boot options so it boots from the re-attched disk, but then i get this error message and eventually times out
error Screenshot 2025-01-28 105639.jpg

after the timeout it then goes to the windows error message below
error2  Screenshot 2025-01-28 105754.jpg

as you can imagine reverting this back then the vm boots
 
doesnt seem to work, so thought id share my setup incase there is something super obvious im missing

this is what its like when it works
View attachment 81507
so i remove hdd and then re-add it with hard disk (scsi0)
View attachment 81508
i then update the boot options so it boots from the re-attched disk, but then i get this error message and eventually times out
View attachment 81509

after the timeout it then goes to the windows error message below
View attachment 81510

as you can imagine reverting this back then the vm boots
The changing of the way the virtual disk is attached looks good and this would probably work fine for Linux (which has the VirtIO SCSI drivers built-in). I don't know how to troubleshoot Windows (as I almost never use it), sorry.