<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Howdy all, <o:p></o:p></p><p class=MsoNormal>I am running Virtual box on a windows 11 Lenovo ThinkPad host from 2020. The Kali Linux does not boot to a log in screen consistently, and I am often confronted with the following errors. <o:p></o:p></p><p class=MsoNormal>Of importance, I did have Hyper-V running on this machine a while ago, it was since turned off in windows apps and features, but that’s not to say remnants aren’t hanging around. <o:p></o:p></p><p class=MsoNormal>The VM guest has the following settings in the display tab: 3D graphics acceleration is enabled, and the graphics controller is set to VMSVGA. The video memory is set to 32 MB, the virtual machine has 3GB of RAM, and 2 CPU processors. <o:p></o:p></p><p class=MsoNormal>I would include the logs here, but NFB Net doesn’t allow us to include attachments, and I am not sure what I am looking for in terms of errors. I would be happy to include those privately for some of you to examine, if you would like. <o:p></o:p></p><p class=MsoNormal>The description of the screenshot was taken from picture smart for Jaws, so any inaccuracies are my own:<o:p></o:p></p><p class=MsoNormal>The image shows a black screen with white text, typical of a command-line interface. It contains error messages related to graphics hardware support. Key parts of the messages are:<br><br>- "vmwgfx seems to be running on an unsupported hypervisor."<br>- "This configuration is likely broken."<br>- "Please switch to a supported graphics device to avoid problems."<br><br>Below the error messages, you see "BusyBox v1.36.1 (Debian 1:1.36.1-9) built-in shell (ash)," indicating the system has dropped to a BusyBox shell, which is a minimalistic shell for system recovery or minimal environments. It prompts the user to enter ‘help’ for a list of built-in commands, and it is at the `(initramfs)` prompt, allowing further commands to be entered. <o:p></o:p></p></div></body></html>