https://pve.proxmox.com/mediawiki/api.php?action=feedcontributions&user=Twocell&feedformat=atomProxmox VE - User contributions [en]2024-03-28T10:49:51ZUser contributionsMediaWiki 1.35.11https://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2375Windows 2003 guest best practices2010-08-21T23:41:43Z<p>Twocell: </p>
<hr />
<div>==Introduction==<br />
<br />
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. Please feel free to add to it, even if just to pose a potential best practice.<br />
<br />
==Power settings==<br />
<br />
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".<br />
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.<br />
<br />
==Disk==<br />
<br />
===raw vs qcow2===<br />
Raw file format provides better performance while qcow2 offers advanced features such as copy on write and snapshots.<br />
<br />
===virtio storage drivers===<br />
Use virtio dirvers for best performance.<br />
<br />
===UNTESTED: caching===<br />
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?<br />
<br />
===UNTESTED: sparse disk===<br />
Use a utility like [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx SDelete] to zero out a drive and take advantage of ext3's sparse file handling.<br />
<br />
==Network==<br />
Use e1000 NIC. It's stable and performs well.<br />
<br />
==Page File Settings==<br />
This is a placeholder as I'm not sure what the optimum page file settings are. My guess is that it's best to create a small static page file and assign plenty of RAM.<br />
<br />
==Sources and further reading==<br />
[http://www.linux-kvm.org/page/Tuning_KVM www.linux-kvm.org/page/Tuning_KVM]</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2374Windows 2003 guest best practices2010-08-21T23:38:41Z<p>Twocell: /* Disk */</p>
<hr />
<div>==Introduction==<br />
<br />
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. Please feel free to add to it, even if just to pose a potential best practice.<br />
<br />
==Power settings==<br />
<br />
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".<br />
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.<br />
<br />
==Disk==<br />
<br />
===raw vs qcow2===<br />
Raw file format provides better performance while qcow2 offers advanced features such as copy on write and snapshots.<br />
<br />
===virtio storage drivers===<br />
Use virtio dirvers for best performance.<br />
<br />
===UNTESTED: caching===<br />
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?<br />
<br />
===UNTESTED: sparse disk===<br />
Use a utility like [http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx SDelete] to zero out a drive and take advantage of ext3's sparse file handling.<br />
<br />
==Network==<br />
<br />
Use e1000 NIC. It's stable and performs well.<br />
<br />
==Sources and further reading==<br />
[http://www.linux-kvm.org/page/Tuning_KVM www.linux-kvm.org/page/Tuning_KVM]</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2373Windows 2003 guest best practices2010-08-21T23:11:14Z<p>Twocell: /* Introduction */</p>
<hr />
<div>==Introduction==<br />
<br />
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. Please feel free to add to it, even if just to pose a potential best practice.<br />
<br />
==Power settings==<br />
<br />
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".<br />
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.<br />
<br />
==Disk==<br />
<br />
===raw vs qcow2===<br />
Raw file format provides better performance while qcow2 offers advanced features such as copy on write and snapshots.<br />
<br />
===virtio storage drivers===<br />
Use virtio dirvers for best performance.<br />
<br />
===caching===<br />
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?<br />
<br />
==Network==<br />
<br />
Use e1000 NIC. It's stable and performs well.<br />
<br />
==Sources and further reading==<br />
[http://www.linux-kvm.org/page/Tuning_KVM www.linux-kvm.org/page/Tuning_KVM]</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2372Windows 2003 guest best practices2010-08-21T23:09:33Z<p>Twocell: </p>
<hr />
<div>==Introduction==<br />
<br />
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. <br />
<br />
==Power settings==<br />
<br />
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".<br />
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.<br />
<br />
==Disk==<br />
<br />
===raw vs qcow2===<br />
Raw file format provides better performance while qcow2 offers advanced features such as copy on write and snapshots.<br />
<br />
===virtio storage drivers===<br />
Use virtio dirvers for best performance.<br />
<br />
===caching===<br />
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?<br />
<br />
==Network==<br />
<br />
Use e1000 NIC. It's stable and performs well.<br />
<br />
==Sources and further reading==<br />
[http://www.linux-kvm.org/page/Tuning_KVM www.linux-kvm.org/page/Tuning_KVM]</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2371Windows 2003 guest best practices2010-08-21T23:06:34Z<p>Twocell: /* Disk */</p>
<hr />
<div>===Introduction===<br />
<br />
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. <br />
<br />
===Power settings===<br />
<br />
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".<br />
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.<br />
<br />
===Disk===<br />
<br />
==raw vs qcow2==<br />
Raw file format provides better performance while qcow2 offers advanced features such as copy on write and snapshots.<br />
<br />
==virtio storage drivers==<br />
Use virtio dirvers for best performance.<br />
<br />
==caching==<br />
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?<br />
<br />
===Network===<br />
<br />
Use e1000 NIC. It's stable and performs well.<br />
<br />
===Sources and further reading===<br />
[http://www.linux-kvm.org/page/Tuning_KVM www.linux-kvm.org/page/Tuning_KVM]</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2370Windows 2003 guest best practices2010-08-21T22:59:55Z<p>Twocell: /* Network */</p>
<hr />
<div>===Introduction===<br />
<br />
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. <br />
<br />
===Power settings===<br />
<br />
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".<br />
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.<br />
<br />
===Disk===<br />
<br />
Use virtio / raw for best performance.<br />
<br />
===Network===<br />
<br />
Use e1000 NIC. It's stable and performs well.<br />
<br />
===Sources and further reading===<br />
[http://www.linux-kvm.org/page/Tuning_KVM www.linux-kvm.org/page/Tuning_KVM]</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2369Windows 2003 guest best practices2010-08-21T22:59:16Z<p>Twocell: /* Sources and further reading */</p>
<hr />
<div>===Introduction===<br />
<br />
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. <br />
<br />
===Power settings===<br />
<br />
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".<br />
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.<br />
<br />
===Disk===<br />
<br />
Use virtio / raw for best performance.<br />
<br />
===Network===<br />
<br />
Use e1000 NIC.<br />
<br />
===Sources and further reading===<br />
[http://www.linux-kvm.org/page/Tuning_KVM www.linux-kvm.org/page/Tuning_KVM]</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2368Windows 2003 guest best practices2010-08-21T22:58:43Z<p>Twocell: </p>
<hr />
<div>===Introduction===<br />
<br />
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. <br />
<br />
===Power settings===<br />
<br />
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".<br />
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.<br />
<br />
===Disk===<br />
<br />
Use virtio / raw for best performance.<br />
<br />
===Network===<br />
<br />
Use e1000 NIC.<br />
<br />
===Sources and further reading===<br />
[http://www.linux-kvm.org/page/Tuning_KVM]</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2367Windows 2003 guest best practices2010-08-21T22:49:09Z<p>Twocell: </p>
<hr />
<div>===Introduction===<br />
<br />
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. <br />
<br />
===Power settings===<br />
<br />
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".<br />
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.<br />
<br />
===Disk===<br />
<br />
Use virtio / raw for best performance.<br />
<br />
===Network===<br />
<br />
Use e1000 NIC.</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2366Windows 2003 guest best practices2010-08-21T22:43:30Z<p>Twocell: </p>
<hr />
<div>===Introduction===<br />
<br />
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, but hopefully soon it will be a comprehensive document.<br />
<br />
===Power settings===<br />
<br />
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".<br />
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.</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=Windows_2003_guest_best_practices&diff=2365Windows 2003 guest best practices2010-08-21T22:42:31Z<p>Twocell: First edit / placeholder</p>
<hr />
<div>==Introduction==<br />
<br />
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, but hopefully soon it will be a comprehensive document.<br />
<br />
==Power settings==<br />
<br />
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".<br />
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.</div>Twocellhttps://pve.proxmox.com/mediawiki/index.php?title=User:Twocell&diff=2364User:Twocell2010-08-21T22:34:00Z<p>Twocell: my card</p>
<hr />
<div>Sherman Boyd<br />
<br />
sherman@twocell.com<br />
<br />
1-480-570-8081<br />
<br />
[http://www.twocell.com www.twocell.com]</div>Twocell