I know you said you have never enabled Hyper-V, but it's always something to check for when having issues since Windows can turn it on for you (thanks, Windows!) if you install other features like Windows Subsystem for Linux or Windows Sandbox, both of which use Hyper-V. That's kind of the point of VMs, right? They're effectively separate machines. It's very unlikely there's a direct correlation between creating one new VM and an existing VM starting to have issues.
I tried disabling and enabling VT-x/AMD-V, but it didn't help, and I haven't installed any Guest Additions or Host Extensions. Hardware virtualization is enabled in the BIOS, as it was disabled by default on AMD processors (or at least on mine). Does anybody know what could've caused this?Ĭould the 15 gigabytes fill up? I've only installed a few things like NASM, build-essential, grub, and a few other stuff for programming, and written an very basic hobby OS which couldn't have taken up more than 0,5 GB of space. I tried a number of things, increased the VRAM, enabled and disabled 3D acceleration, I've never enabled Hyper-V, but still it didn't work. I removed Kali Linux, but still, it didn't get to the login screen, VirtualBox changed it to 64-bit Ubuntu (it was 32-bit). It worked perfectly, until on day, I decided to install Kali Linux next to it, to learn hacking.
So I installed Ubuntu (guest OS) on VirtualBox, and gave it 4 gigs of RAM, 15 GBs of storage, 16 MB of VRAM (increased it to 64 MBs), on an AMD Ryzen 7 2700x, 16 GBs of RAM, GTX 1060 3 GB video card, on Windows 10 (host OS).
0 kommentar(er)
