Ignore the win 8.1; that is just who microsoft wrote that article for. IT is also the one where PAE is the easyest explained.
For moe PAE/NX is a setting I have to activate / deactivate in the settings of the virtual machines. If there is no easy way (or you cannot find where) to disable this, I could see if the version of your VM runnning here (with PAE disabled) runs better in your system. This off course would mean that I export my version, and make it available for you to download again.
Does the issue not exist if you update beyond this commit? Or is it not just replicatable? Is there an issue youâre experiencing more severe keeping you from wanting to update to recent commits?
Any amount over 4GB I think should necessitate PAE. Thereâs a real threshold when PAE becomes a must, but this shouldnât affect the webuiâitâll be more at the âdoes Linux recognize my ramâ level.
Honestly, I think all fireworm issues can be tied back to the Minecraft server-software itself or some latent bug from leftovers in the filesystemâI really cannot think of how the cause can come from lower-level than this.
Sorry I havenât been able to address this so muchâwork has been pretty packed and I have a family vacation coming up until May. Iâll see if I can squeeze in an attempt with these HDD uploads.
As far as I understood it, this was only a necessety for 32-bit systems. PAE added 4 bits so that the adressing area was increased to 36-bit. 64bit systems do not have this memory limit as it has a far larger adress pool for memory. This shows itself in the way that any memory above the adressing area is not shown.
The trouble with the 32bit 4GB limit was that with 32 bit the entire system had a max of 4GB memory adress space available. This included space for processor cache and video card RAM.
So as long as he is running a 64 bit system, PAE should be unnescesary.
Example in hand:
I run my system without PAE/NX enabled, but with 16 GB memory. It is an ubuntu 64 bit server, and my MineOS happily repports all memory
Yes indeed, PAE is required to add/enable for 32-bit systems because 32-bit couldnât handle above 4gb. This is consistent with what youâre saying.
Iâve misspoken, though: PAE is necessary for many more systems than just 32-bit systems with more than 4GB of RAM. Many Linux distros (including what I believe is the case for 32-bit MineOS Turnkey using Wheezy) require PAE just outright, even if you donât pass the memory threshold.
That said, I donât think PAE should matter much in terms of getting MineOS up and running. Unless Iâve glossed over some really pertinent posts here, PAE should matter in pretty much two instances only: 1) did the system boot up without giving a PAE error? 2) did the system recognize and make available all the RAM expected?
And with 64 bit systems, as is this case and your own, PAE is irrelevant. Sorry for confusing contributions!
Serve old .isoâs with out huge issues, small irritations mostly. (wheezy with java7)
Started to serve new .iso and began not reaching webiu. (jessie w/ java8).
Went back to wheezy, the commit was1853741 (Ithink and very stable) Decided to update java7 to java8 due to âotherâ issues and began not to reach webui. Thought it was java related issue so did not report here and continued to troubleshoot. (Here is where the commit issue is, I had updated the webui to bcb4bd5? and did not notice.)
I would delete the troublesome servers and create new VMâs for frech installs, I noted at some point the commit moved past a previous commit to a new commit and the problem stopped. 2d22dc1, I think. I may have the sequence wrong, I assume you would know the order of commit updates.
so working with old .iso and update java 7 to java 8 i was able to replicate with commit 0e45bet, and noted if I updated the commit the problem would resolve.
At some point I was getting the same error with wheezy and java 7. That made me think it was a âcommitâ error. If that was true where were all the others posting up suffering the same problem? Only me.
This made me think it was more a combination of things than only just one thing making trouble so I wanted to load the interim commits to confirm and found out I did not know how to do that.
Yep, and this is why I find it interesting to test wether tNt would have the same faults on his server if he deactivated PAE, since I now runs a duplicate of his server where the WebUI crashes on his VM, but stays stable at mine. The MineOS and turnkey installations are equal, with the only difference being Vmware ESXI 6 (with PAE, 2 networkscards and floppydrive)vs Virtualbox 4.3 (without PAE and floppy drive, and only one Network card). Since the differences in all practicality is virtual hardware, and it is stable on my platform and not his. I canât imagine an empty virtual floppy drive, or a spare network card would have any effect. When I tried to run his VM with a pure import, it simply wouldnât start up beyond the âloading ramdiskâ message on boot.
CPUID Mask Expose the Nx flag to guest or ( Hide the NX/DX flag to guest).
"CPU Identification Mask
Hiding the NX/XD flag will increase vMotion compatibility between hosts, at the cost of disabling certain CPU perfomance features for some guest operating systems and applications"
Thinking this might shut off (hide) PAE as well, need to confirm.
" PAE also enables several advanced system and processor features, including hardware-enabled Data Execution Prevention (DEP), non-uniform memory access (NUMA), and the ability to add memory to a system while it is running (hot-add memory)."
IF DEP is enabled, PAE cannot be disabled. So have disable both DEP and PAE for windows machines.
VMware adds the ability to hot swap memory, to do this I think it turns on PAE, per above.
So If I turm off the memory hot swap option it might turn off PAE.
Still checking.
Could be boiling down to an ESXi issue as in another case of migrating VMâs. He can see PAE is on after migrating to ESX but can not when the VM is in ESXi.
" I moved this VM from ESXi into ESX, I was able to power back on the ESXi copy and there is no reference to PAE when it is running on my ESXi server. PAE only shows up on VMs running on my ESX servers and it is on every guest VM we are running is ESX, without exception it was VMs that were migrated over from ESXi, "
@hexparrot:
Is there some function for autmatically restarting the GUI? I am browsing through the log of my copy of @tNtâs server, and even though it seems everything is stable and up, I see several server starts in the mineos.log, and several instanses of the error we are hunting for. The only thing I really notice is that I occationally have to log back into the WebUI.