Guru Meditation problem again

[smth]

Hello
I am trying to install Windows 2000 Advanced Server into VirtualBox and getting error: "A critical error has occurred while running the virtual machine and machine execution has been stopped."

I'm tried VirtualBox 5.0, 4.3, 3.2, and on all of them I getting the same error. With the exception of VirtualBox 3.2 just hangs up after "Setup is starting Windows 2000" and no error appeared.

I installed Windows 2000 from this iso image under Virtual PC, and it installs and runs properly. Then I tried to mount the drive with already installed Windows 2000 into Virtual Box (into all three versions, yes), but it is still not working and gives the same error.

My Host system is Windows Server 2003 Enterprise x64 Edition with Core 2 Duo E4500 CPU. It does not support VT-x, if it means anything. So, VirtualBox 5.0 is not running on the system without VT-x until I edit the VM file and set all "HardwareVirtEx" settings to "false". It should be possible to do the same through virtual machine settings, without editing the config file, but tabs with hardware virtualization are inactive and I can't change anything. Despite this, even when I succeeded to start virtual machine, it fails with an error.

I read the "previous topics" about that problem, but there is no solution. What do they suggest? Use only 1 CPU? I already use only one.

The first log file is when i tried to install Windows from iso image, the second is when i tried to run installed Windows from Virtual PC disk image.

[mpack]

VirtualBox 3.x? Pass. What are you expecting? A time traveller to go back to test and fix that version?

Use the current release, report any problems with that.

[smth]

In first post, I mentioned three versions, first of them was 5.0 (5.0.0-101573). Only after it did not work, I started checking previous versions.
Here's the log for 5.0, if it would change anything.

[mpack]

Yes, you mentioned several VirtualBox versions, but the only one you provided diagnostics for was 3.x, which was therefore the only option I could consider (or refuse to).

Some notes about your VM - in no particular order.

• In general I'm afraid I must note that your host is poorly suited to running VMs. You only have 2GB host RAM, and yet a 64bit host OS has been installed (usually the only reason to install a 64bit OS is to be able to use >4GB RAM). This means that only ~770MB is available for use by apps, so 512MB is around the maximum amount of RAM you could assign.
• The log is for an XP VM (according to the OS version in the settings), not Win2K.
• However, a Win2K ISO is mounted in the VM.
• In fact the ISO says that this is "Win2K Server Beta 3 RC1". The fact that it's for a beta release is not good: it may not be stable.
• 192MB may not be enough for a server version of Windows. The recommended minimum was 256MB. I suggest that you allocate at least that much, but no more than 512MB.
• The error is still "VERR_REM_TOO_MANY_TRAPS". This sounds similar to a triple fault, and usually means that the VM is doing something naughty with the hardware. The fact that you get the same fault with multiple VBox versions (including very old ones) is actually useful, since it indicates that this is not a newly introduced bug.

Personally, my suspicion falls on the fact that it's a beta. By definition it is not a stable release, and not a supported guest OS.

Where did you get this ISO?