Difference between revisions of "Windows 2003 guest best practices"
|Line 10:||Line 10:|
Use virtio for best performance.
Revision as of 01:06, 22 August 2010
This is a set of best practices to follow when installing a Windows 2003 guest on a Proxmox VE server. Right now it's a work in progress, written by a Proxmox noob but hopefully soon it will be a comprehensive and reliable document.
In order for the Windows 2003 guest to shutdown cleanly in the event of a shutdown on the Proxmox VE host you need to enable "Allow system to be shut down without having to log on". It can be found in the policy editor here: "Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Shutdown: Allow system to be shut down without having to log on", by running: gpedit.msc.
raw vs qcow2
Raw file format provides better performance while qcow2 offers advanced features such as copy on write and snapshots.
virtio storage drivers
Use virtio dirvers for best performance.
Under disk properties in Windows 2003 you can turn off the disk cache (Windows caches writes in ram). KVM enables it's own writethough caching which relies on the Debian hosts caching (I think). Plus modern disks have a sizable hardware cache. Do we really need all this chained redundant caching?
Use e1000 NIC. It's stable and performs well.