2003 R2 64 bit system memory greater than 4GB will result in blue screen

[postchen]

2003 R2 64 bit system configuration with 4GB or more memory will result in a blue screen
XP and 2003 R2 32-bit systems can be solved by adding "args: - cpu host, lm=off". How to solve the blue screen of 64 bit systems?

 

[cwt]

Did you migrate the VM or did you installed it from scratch? Afaik you have to choose „Standard PC“ during the 2k3 setup, if I remember correct.

 

[postchen]

Did you migrate the VM or did you installed it from scratch? Afaik you have to choose „Standard PC“ during the 2k3 setup, if I remember correct.

Built on PVE with a configuration of 1 core and 2GB, and later modified the memory capacity, the screen will turn blue when turned on. After testing, it was found that the screen will not turn blue when the memory is below 4GB, and it can be used normally when turned on.

 

[BobhWasatch]

For i440 that may be the max memory.

 

[postchen]

For i440 that may be the max memory.

With the same configuration and settings, both XP and 2003 R2 32-bit systems can run normally with 8GB of memory allocation.

 

[postchen]

After testing, if the CPU type is not set to host, there will be no blue screen. Is there a better solution besides modifying the CPU type? Because I want to use the host type

 

[cwt]

Did you try to disable NUMA?

 

[postchen]

Did you try to disable NUMA?

The situation is still the same when turning off NUMA
After comparison, if the CPU type uses host, the CPU has an additional vt-x instruction set. I want to block this instruction set and test whether it will not cause a blue screen, but I have not found a method to block the instruction set.