I have several VM's, each one is required to have a 128MB minimum swap file on the boot drive.
Only Microsoft knows why, it's a real pain in the butt, especially when you are configuring your RAID systems to operate a certain way.
Further, to this 128MB swap file on the first drive, I've added the option to have a Windows "System Managed" swap file on one of my other logical drives; One which I would LIKE it to use as the primary swap file.
Windows doesn't seem to know that it is supposed to do this.
Is there a reason why? Is there something else I need to configure, besides setting "system managed size" for the drive I want the swap file on?
As you haven't mentioned OS/architecture -> check this out for XP/2003 x64 -> http://support.microsoft.com/kb/889654/en-us ;-)
What did you mean by “swap file”? Did you mean page file? Could you please elaborate this?
By the way, swap file (as it’s called in Windows 95/98/ME: Win386.swp) or page file (in Windows NT versions including Windows 2000 and XP: pagefile.sys).
For more information about appropriate page file, you can refer to:
How to determine the appropriate page file size on my server
Yes, a page file is what I mean; sorry if the nomenclature is incorrect.
OS: Windows Server 2008 R2, 64bit. The VM's are running Server 2008 Standard, or Enterprise.
The problem isn't determining the size of the swap file, it's trying to figure out why Microsoft won't manage a swap file on another drive, when I've set it to do so. It doesn't make sense to me.
C: drive has a 128MB page file.
D: drive is set to "System Managed" page file.
Now, if I run the server with those specs, it doesn't make a "System Managed" swap file on the D: drive. It just cries & whines about not having a proper swap file size, and uses the 128MB one.
If I set the C: drive to "System Managed", it creates a swap file equal to the memory size.
The primary question being, why wouldn't it, in the first setting, use a swap file of 128MB on the C: drive then, create another swap file on D:, equal to Memory... minus 128MB?
I hate to resurrect a really old thread, but it is still showing up in searches.
This occurs when the swap file is created on a drive attached to the SCSI chain. Hyper-V guests initialize their swap files before the virtual SCSI driver is fully loaded. Reassign the VHD from the SCSI chain to the IDE chain and restart. Like real IDE, only one drive per virtual IDE controller is ever active at a time, so I usually connect swap drives to "Secondary channel (1)" where it will share with the less-utilized virtual DVD drive.