When I do that, the reference to PAE in My Computer > Properties goes away. The only way I have found to disable it and get rid of it has been to change the /noexecute=optout to /execute. So I looked at all of my 2003 guest VMs and every one of them in "My Computer" > "Properties" says that PAE is enabled. you will see that PAE is clearly enabled and running. Multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /noexecute=optout /fastdetectĪs you can see, there is no mention of PAE in that boot.ini but if you look at the image I have attached. Below is the boot.ini from that VM:ĭefault=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS I see PAE when I right click "My Computer" from within the Guest OS (2003 Std) and select Properties. I have just tried replacing the /noexecute=optout or /noexecute=alwaysoff switch in the boot.ini with /execute and that does in fact remove PAE, but it also turns off DEP which we would prefer not to do if possible Since the particular Citrix Application VM only has 1GB of vRAM, I don't see the need for PAE and I would like to know if there is a way to tell ESX to not use it? So something about the combination of ESX forcing PAE down our throat and the way that it plays with DEP is causing this problem. So we tested that and sure enough, the memory error went away and people could use the Citrix App that they could not use before when the /noexcute switch was set to optout. I then looked at the remaining VMs in ESXi and none of them indicate that they are using PAE and I have confirmed that the Citrix VMs in question were not using PAE when they were on ESXi.Ī bit of googling indicated that is we disable Data Execution Prevention (DEP) with the /noexecute=alwaysoff switch in the boot.ini that would resolve our problem. After looking into the problem we discovered that when we view the properties on all of the VMs in ESX that they are all PAE enabled, even though there is no /pae switch in the boot.ini.
Today we had some users complain about a Citrix application was not working and was giving a memory error when they tried to run it. Recently I moved serveral Citrix Application Server VMs from our ESXi environment into our new ESX environment.
0 kommentar(er)
