[Solved] guest windows xp does not start

[Expert]

Hello!
Host: Win 8.1 x64, hardware notebook pentium N3520@2.16GHz, 4gb DDR3

at vm startup appear logo screen winxp, and hangs in this state.

What I was trying to do
1.installed different version VirtualBox, incl 4.3.40, 5.0.32, 5.1.14
2.Extension Pack is installed on the host. The same version as VirtualBox.
3.changed settings vm, incl disable usb controller.
4.installed net framework 4.6, on the host of course
5.searched on the forum by tag XP ,but min limit on 4 characters not allow search. I looked last 10pp this part, solution not found

help solve the problem. Log file attached.

[mpack]

Apart from searching on the forum, none of the changes you made are appropriate (relevant). E.g. every VirtualBox version runs XP well, so changing versions won't affect the problem at all. VirtualBox doesn't use .NET.

You don't have an extension pack, and therefore can't use any USB device later than USB1.1, however lack of USB should not cause a hang, it should cause an error or the device simply won't work.

If XP doesn't boot then it means that either that the boot disk is corrupted (either internally, or due to a host drive problem), or the VM "recipe" doesn't match the expectations of the XP image.

Where did this XP image come from?

[Expert]

Thanks for the reply!

You don't have an extension pack,

Yes, I reinstalled the VirtualBox a few times and the last time I can't to install extension pack. Start up the file Oracle_VM_VirtualBox_Extension_Pack-5.1.14-112924, and instead of running the installer, launches directly VirtualBox, and installation is not performed.

Where did this XP image come from?

this image from another computer. Checked this image for more performance desktop computer - it works. Only give an error when the RAM is less than 512mb - "the memory could not be written 0x00000000.... etc"

desktop configuration AMD X4 740@3.2GHz, 8Gb DDR3, Win7 x64.
On the notebook setting RAM 512, and 1024mb - same hangs.

VM "recipe" doesn't match the expectations of the XP image.

who is - "recipe" ?

[mpack]

Every virtual machine is built to a specification defined by it's settings. I call this the recipe, for obvious reasons.

If you change the recipe of an XP VM (e.g. while moving it from one PC to another), then a selection of bad things can happen, from loss of activation to crashes to boot failures.

[Expert]

mpack, how can I check this recipe? and where to change it?
With the same settings on one computer works on another not.

[socratis]

Every virtual machine is built to a specification defined by it's settings. I call this the recipe.

Recipe = VM settings.
Right-click on the VM, show in Explorer. That .VBOX file are the settings. ZIP it and attach it here. Do the same from the computer it works. Attach that one too here. See the "Upload attachment" tab below the reply form.

[Expert]

done

[scottgus1]

Not quite done, unfortunately, those are .vbox-prev files. They are backups taken by Virtualbox when VB needs to modify the .vbox file. Try again, please. Be sure your host OS is set to show known extensions.

[scottgus1]

Where did this XP image come from?

this image from another computer.

How did you move the image? There's a right way and a bunch of fraught-with-possible-errors ways.

[Expert]

sorry, now it's in the attachment

How did you move the image? There's a right way and a bunch of fraught-with-possible-errors ways.

image downloaded from another PC(where is running it) on local network, checksum converges. Read the guide how to move VM, i have in GUI's manager just this one VM.

[scottgus1]

image downloaded from another PC

Exactly how did you do that? Just the virtual disk file, or by the tutorial? In other words, did you just copy the disk file and make a new guest on the new host to run the disk file? Or did you copy the entire guest folder? Or did you import it?

Being that the UUIDs on the hard disks between the two .vbox's are different, and the virtual disk is called "Captiva-disk1.vmdk" I infer that this was an appliance being imported, not an exact folder copy.

Try unregistering and deleting the guest off the bad host, and copying the entire guest folder off the good host to the bad one then re-registering it on the bad host. Try again to run it.

[Expert]

Or did you import it?

Yes, imported file with the extension .ova

what did now:
on the bad host, in VirtualBox Manager right-click on the VM ->Remove. Default Machine Folder(VirtualBox VMs) ->deleted manually.

with a good host copied VirtualBox VMs to the bad one, then in VirtualBox Manager ->Machine ->Add .vbox Try again to run ->also hangs


in this state.

[socratis]

1. Start the VM. Not from a saved or paused state. Clean start.
2. Take the steps required to generate/observe the error. In your case, wait for 10 minutes.
3. Shut down the VM (if it hasn't aborted by itself). Not saved, not paused. Completely shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
4. Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
5. Save the first log, ZIP it and attach it in your response (see the "Upload attachment" tab below the reply form).

Do this for both the working and the non-working computers.

[Expert]

done!

[scottgus1]

In the not working log:
00:00:03.436317 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.
00:00:03.512460 HM: HMR3Init: Falling back to raw-mode: VT-x is not available

Although the guest type is being reported as Windows XP, like my XP 32-bit guests are, something about the failing guest thinks it should be 64-bit, and the host PC claims to not have VT-x to support it. The CPU, "Intel(R) Pentium(R) CPU N3520" if I read right, does have VT-x. See I have a 64bit host, but can't install 64bit guests