Code: Select all
<CpuIdTree>
<CpuIdLeaf id="1" eax="1764" ebx="371197952" ecx="2143216631" edx="3219913727"/>
</CpuIdTree>
I have a virtual machine (Linux Debian guest) as part of a larger software package and the lines from above are part of the included vbox configuration file.
Unfortunately, the virtual machine doesn't run; it starts booting, then several warning messages appear such as "invalid opcode"/"illegal instruction", and an automatic reboot is triggered (-> infinite reboot loop).
If I remove these 3 CpuIdTree lines shown above from the vbox file, everything appears to work (the guest system is correctly booting and running).
The Windows 10 host system is old as well (64bit Intel Core2 Quad CPU Q9550 from about 2009), but up to now it's been working ok.
(I've tried this with several VirtualBox version from 6.0.4 to 6.1.x, all showed the same behavior.)
So, what's going on? Why doesn't the virtual machine boot with the CpuIdLeaf configuration? What's happening if I remove these lines - can there be any surprising side effects?
Thanks,
od