Error on
Error on
Hello. When i try to setup a Debian VM on my Windows 11 i got stuck after click install button. It show screen at attachment. I am trying to install without graphic ui because of homework requirement. My laptop is Acer Nitro 16 AN16-41(A new version of Nitro 16) CPU is AMD Ryzen 7840HS With 780M graphic, GPU is RTX 4060. I tried bot Virtual Box 7 and last version of 6, and also tried Debian 12 and 11.7, And i dont remember but i think i tried install also ubuntu too for testing an i think it also stuck too. Why booting stuck that screen. Is because of kernel incompatible? And any solution for that problem? Thank you for all answer already.
- Attachments
-
- resim_2023-09-07_154157139.png (24.63 KiB) Viewed 4714 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Error on
Provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
Re: Error on
Of course. Here is the log file.
- Attachments
-
- Test 6-2023-09-07-16-20-03 Log.zip
- (28.57 KiB) Downloaded 36 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Error on
The log shows you allocating RAM which your host doesn't have.
OTOH, 16MB is not enough graphics RAM. That should be maxed out (128MB). See settings|Display.
Next up, you have Hyper-v enabled on the host. This interferes with VirtualBox.
RAM allocated to a VM needs to be real, available RAM. Not paged, and not already in use. You need to shut down some RAM hogs on your host, and/or add more RAM to the host.00:00:52.026845 Host RAM: 15556MB (15.1GB) total, 1923MB available
...
00:00:52.219741 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
OTOH, 16MB is not enough graphics RAM. That should be maxed out (128MB). See settings|Display.
Next up, you have Hyper-v enabled on the host. This interferes with VirtualBox.
To disable Hyper-v reliably, see HMR3Init: Attempting fall back to NEM (Hyper-V is active).00:00:52.220116 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
00:00:52.305232 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:52.305446 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...