Windows XP won't start - Can't disable virtualization?

[Mr Wolf]

Hi to all!
I have a Windows XP 32 bit virtual machine created on a notebook which supports VT-x and I copied it on a netbook which doesn't support it, and the VM won't load, it always crashes.
In the log (which I attach), it says:
WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.
Can't understand why it says it's a 64 bit system.
By the way, the tab System -> Acceleration with the option for VT-x is greyed out in the netbook.
I tried in my notebook to disable it and then to copy again the VM in the netbook, but I always get the same problem.
Searching, I found similar problems, and it seems to be a VirtualBox bug (I have 4.3.20).

I tried to edit .box config file and set:
HardwareVirtEx enabled="false"
but didn't solve the problem.

Is there anything else I can try?

Thanks in advance

[Perryg]

Try the following in a command window ( must be in the folder that actually has VBoxManage.exe for it to work )

Code: Select all

VBoxManage modifyvm "Windows XP" --longmode off

[Mr Wolf]

Thanks for your answer, but it doesn't seem to work, nothing changed.

[mpack]

Try same command, except the last part should be "--hwvirtex off".

As to why it says that you have a 64bit OS: I asked the devs about that recently. They say that newer .vbox file versions record whether the VM is 32bit or 64bit, but when given an older .vbox file the software has to guess, and they guess in what they think is the less risky direction. In your case the guess is wrong. I guess the code is a bit new.

I'm surprised that you say "--longmode off" had no effect. It should have stopped telling you that the guest was 64bit. Though of course you'll continue getting the VT-x not supported error until that too is disabled, which the hwvirtex command should do.

[Mr Wolf]

Thanks for your answer!

Ok, I've just tried again, but got the same damn problem! It starts, got a blue screen and reboots with the menu asking if I want to start in safe mode.

By the way, this time I tried opening a command prompt as administrator, even if it didn't complain the first time.
In the log, that Warning is still there.

So, the problem could be .vbox file which is not "compatible" with newer VirtuaBox versions? I made this VM several versions ago, I think. ...

I just copied it in the netbook because I needed a device to use with it, since VirtualBox unfortunately still doesn't support USB 3.0.

[Perryg]

Post the guests *.vbox file as an attachment. Compress it first.

[Martin]

It starts, got a blue screen and reboots with the menu asking if I want to start in safe mode.

So "won't start" is not a Vbox problem, but something inside the guest (or in the VM definition).
Can you disable the automatic restart and tell us the error code / message on the blue screen?

[loukingjr]

If it is a .vbox file problem you could try just making a new XP 32bit VM but instead of creating a new drive just attach the .vdi and see if it will boot.

[mpack]

Does the VM boot in safe mode?

How exactly was this VM moved to a new host?

[Mr Wolf]

Thanks for your answers!

First of all, I moved the VM both by copying and pasting the whole folder and exporting the VM.

The VM can boot in safe mode.
I can't understand if this is the expected behaviour if the virtualization option is enabled, but the computer doesn't actually support it. I mean: should it boot anyway and crash? And allow to boot in safe mode?

Perhaps, creating a new VM and use the old hard disk vdi is something I can try when I have time. I wonder if it can work.

Here's a screenshot of the BOSD:


I also attach the .vbox file

[Perryg]

What is this front end? It looks like a browser with tabs.

Two things that might cause your issue. You have two network adapters one natnetwork and one internal, both activated. If they have not been setup on the second host it could cause an issue. You can verify if that is causing this by disabling the network temporarily.

Another thing although rare is the first host used a different type of processor. Intel and the new one is AMD. Booting in safe mode and doing a search for new devices might feel this one out.

[Mr Wolf]

It's TeamViewer interface, can't live without it.

I have only one NAT network adapter, but, if the problem depends on processor, you centered the point: the notebook on which I made the VM is Intel Core I7, while the netbook on which I copied it is AMD C-60.

In Safe Mode, it recognizes correctly the processor.

EDIT: I've just searched information about sptd.sys from BSOD, and found it's related to Daemon Tools, which I had installed. I uninstalled Daemon Tools, removed that file from windows\system32 and... voilà, it starts!