virtualbox.org

Hi,
Trying to install a Win XP
Starts guru meditation failure when I format the disk in NTFS
Please help

From the log you posted:

00:00:04.390813 Host RAM: 2039MB total, 816MB available
00:00:06.053903   RamSize         <integer> = 0x000000003d200000 (1 025 507 328, 978 MB)
00:00:06.055066   VRamSize         <integer> = 0x0000000008000000 (134 217 728, 128 MB)
00:01:06.797837 VM: Raising runtime error 'HostMemoryLow' (fFlags=0x2)
00:01:06.797897 Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM"

If the last line gets truncated, the message is:

00:01:06.797897 Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM"

You're trying to allocate too much memory for the guest. Memory which you do NOT have available. Ergo, crash. You either need to free memory on the host, buy more memory, or (the easiest) lower the requirements of your guest to something like 512 MB RAM and 32 MB VRAM.

Hi, socratis

Thank you for a quick reply.
I set a RAM size 512.
Win XP installing, but it crash with "blue screen" after a 3 minutes

Please zip logs before attaching them.

In any case the VM log from the host doesn't really tell us anything about problems the guest OS is having. A screenshot of the BSOD might. How exactly are you installing XP? I.e. is this from a genuine install CD?

You say it is crashing during NTFS format. You are doing a quick format (only) right? I.e. you aren't trying to low level format a virtual disk.

Also, what is "MiniXP"?

Hi,

Trying two different distributive discs (MinXP - is an another XP disc). The problem still the same - BSOD
Trying set a RAM size to 379 Mb, the problem still the same
Trying a low level format - no result

I attached the ZIP of log folder

Nobody told you to try a low level format. Quite the opposite.

I await a screenshot of the BSOD. If it is going past too quickly then see section 12.3.5 of the user manual "How to record bluescreen information from Windows guests".

Please stop posting logs unless we ask for them - I already told you that guest OS bluescreens are not recorded there. Also, post one log only, as I don't really appreciate being handed five times the (unpaid) work!

In attach BSOD screenshot
What else I need to do?

Carefully consider each of the following paragraphs.

Why is the VM name filled with blanks? Create a new VM and give it a legal name.

What possessed you to use ".hdd" format for the virtual hard disk? Use dynamic VDI format, which is the native VirtualBox format and the default.

Connect the VDI to an IDE controller, not SATA. XP doesn't have native SATA support.

I would also turn off 3D acceleration. I doubt you need it. Or tell me what do you intend to use the XP VM for?

I'm concerned about the lack of memory on your host. Your host is XP with 2GB RAM, you should have at least 1GB available. If I was you I'd look at your XP host's task manager to identify what processes are running (Google will tell you what they are), who the memory hogs are, and what can be got rid of. On my XP host at home I only have 18 processes running. At work they insist on superfluous antivirus etc, so here it's 35 processes running right now (including Firefox).

Thank you very much. Now it`s working well.
Inviting you in Russia. Good vodka with a fresh caviar is guaranteed