virtualbox.org

I don't know guys.

From what I am reading here there is a real reason why this will never work.

ingenium, and arnuschky

• If you have installed the Windows OS in VBox with the VT-x/AMD-v switch off (as the logs show) and then turn it on that will not work.
  The OS in Windows case will not have the proper Kernel. It is one or the other. The only way to change the kernel (As far as I know) is to reinstall.

Of course I could be misreading here if so please disregard and I will go back to sleep now.

No people are complaining it doesn't work anymore after upgrading to 2.2.2, its either a bug or 2.2.2 does some testing which upsets the bios.

It's actually never worked for me in Virtualbox with Windows, though I've only tried the one Windows VM. Linux VMs in Virtualbox seem to work fine with VT-x enabled. So it may be the kernel issue...can you post a link to other people with this problem? I'm wondering if I can just drop in a replacement kernel for it instead of reinstalling.

ingenium wrote:I'm wondering if I can just drop in a replacement kernel for it instead of reinstalling.

Do both, install new VM and then copy the relevant parts over to the other VM.

A fresh install of Windows XP works with VT-x enabled.

The new copy was SP2, whereas the VM is SP3. I upgraded the new copy to SP3 and got it fully patched. It still worked, and the kernel modification dates are the same.

When I did an md5sum on the kernels, both were the same. So it's NOT the kernel.

md5sums:
ntkrnlpa.exe: 5ba7f2141bc6db06100d0e5a732c617a
ntoskrnl.exe: 7a95b10a73737ebf24139aaa63f5212b

More testing revealed that the original VM would boot into safemode with VT-x enabled. I created a new user, and the VM hangs when I login with either my old username or the new one. Any suggestions short of starting fresh?

EDIT: Uninstalling guest additions in the original VM fixed the problem. After re-installing it no longer hung. So something with guest additions was the culprit.

My initial install was with VT-x enabled, I think. Anyways, it worked with it, and stopped working after an upgrade.

But I'm happy to report that the problem vanished with my recent upgrade to 3.0.2!