virtualbox.org

Hello,I managed to install the latest version of Kali Linux on VBox.
Problem is, everytime I try to boot it up, I get:

ExceptionCode=0x80000003 ExceptionFlags=0x00000000 ExceptionAddress=00007ffe05ca2c92

Logs attached below, please help

Is there something you are not telling us about?

00:00:04.512451 CPUM: MXCSR_MASK=0x2ffff (host: 0x2ffff)
00:00:04.512451 CPUM: Microcode revision 0x06000822
00:00:04.512451 CPUM: Changing leaf 13[0]: EBX=0x340 -> 0x340, ECX=0x3c0 -> 0x340
00:00:04.512451 CPUM: MSR fudge: 0x00000017 IA32_PLATFORM_ID
00:00:04.512451 CPUM: MSR fudge: 0x000001a0 IA32_MISC_ENABLE
00:00:04.512451 CPUM: MSR fudge: 0x0000002c P4_EBC_FREQUENCY_ID

Are you trying to fake a CPU ID?

no?...
i got it to work a couple of hours ago but when i restarted the machine it fucked up again
how do I make it to show the real CPU ID? or prove that I have a real one lol
also, how can i fix this?

I'm pretty sure that's not default behaviour (though without owning a PC using that same AMD CPU I can't be 100% sure), I'm sure it's a result of using the various VBoxManage modifyvm <vm> --cpu-profile or the older VBoxManage setextradata <vm> "VBoxInternal/CPUM/xxx" APIs to try to fake the hardware signature of a PC. As you can see from the log extract above, it's trying to fake an Intel CPUID on an AMD processor. This can't have happened by accident.

Well, how can I undo this? I just installed VBox a couple of days ago and I guess I did something wrong somewhere(even though the app work then broke again) so Im pretty new at this

No, you can't do this by accident as I already said. It would be like threading a dozen needles by accident - it didn't happen. If you didn't do it then someone else created the VM. Or this is normal behaviour with an AMD CPU: which I've never seen reported before.

To settle the matter, zip up the .vbox control file that goes with this VM, and post the zip here. We'll soon see if these mods are in the control file.

Well, I dont have the same VM since I tried reinstalling and uninstalling for the last couple of days, but I have one that shows the same error and CPU switching

I'm seeing the exception, I see where it refers to in the source code, however that doesn't really tell me what causes it.

I return to my original question - is there anything unusual about this host? For example, is it a VM?

It might also be worthwhile to download the ISO again, or at least compare checksums on it.

The host is a 5 year-old Win 8, and Im guessing it maybe has to do with missing/corrupt system files, its not a VM.
Tried both .iso and the standalone vbox .ova from Offensive Security website, with no luck, so Im sure its not the .iso.

When I last got it to work, I reinstalled VirtualBox and it temporarily missconfigured my network, thus I had to do ipconfig /release /renew /flushdns, which made it work only once, after rebooting, I never got it working again.