cannot use virtualbox on intel 10th gen processor on Debian 10

[bigdata]

HI,

I recently purchased a laptop PC with a new 10th generation Intel processor.

It seems that virtual box does not support this type of graphics processor (which is included in the processor itself: I do not have a separate graphics card).

because I manage to launch virtual box but not to start debian 10 : debian 10 starts correctly but as soon as I identify myself it shows me a black screen and starts again.

Thank you in advance for your help.

I need debian for my work on this machine

[BillG]

"It seems" is not very convincing. What evidence do you have that the problem is caused by the graphics processor? What graphics processor does you PC have?

I have no problem running VIrtualBox on a 10th Gen Intel processor i5-10400 with Intel UHD graphics 630.

[bigdata]

everything suggests that it is a problem that comes from the graphics card which is integrated in my intel i5-10210U processor.

I don't see where the problem could come from.

all my drivers are up to date.

and i also think its a display issue as it puts black screens.

[multiOS]

Sorry, but at this stage you're just guessing. Many people get to the same situation and usually it's a problem with the way the Virtual Machine has been created /set up, or the fact that it can't access some feature on the Host PC.

With the VM shut down, right-click on the VM entry in the VirtualBox Manager and select "Show in...". Zip the .vbox file and attach the zipped file to your response message using the 'Upload Attachment Tab and hopefully someone will be able to identify the problem for you (or confirm/discount your initial suspicion). If your 'new' laptop doesn't currently display file extensions, please change the setting in the Windows file manager so that you can identify the correct file.

[bigdata]

hi,

here is my initial .vbox file (with which I installed debian 10).

I also have a pack extension file.

link of VM and Debian : mega.nz/file/fr5ETICL#_xaAIZ4lptsT5IfPgO8C5uTQT5bbSDsfFc4KQOPgQMI

link of extension pack : mega.nz/file/vmwzXSKK#IjJsqMd7VO_7XJmHnb9RIqfDcV9-rUm0_248oL8wOb0


I am not the only one in this case I have 2 friends who have the same problem with an new generation processor.

they therefore went to Vmware (which works correctly).

Thank you for your help

[scottgus1]

Try those log attachments again, please, per MultiOS's instructions:

attach the zipped file to your response message using the 'Upload Attachment Tab

Forum gurus don't go to 3rd-party sharing sites for things that can be posted using Upload Attachment.

[bigdata]

ok here is the .zip file

[bigdata]

and here logs

[scottgus1]

One thing i see right off:

00:00:05.963711 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)

Video RAM is too low. Max out that slider.

Also:

00:00:05.964355 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available

Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

[bigdata]

I therefore increase the amount of ram in video and I deactivate the hyper V

I tried and I tell you

Thank you

[bigdata]

ok i managed to enter the virtual machine but after a little while, as soon as I go to the terminal, the session is locked and it is impossible to reconnect to the virtual machine.

It should be restarted every 5 minutes.

[bigdata]

So I manually deactivate the Hyper-v of my PC

I can't even connect to my VM as soon as I enter the password there is a black screen then the connection interface.
it happens continuously.


should I activate the hyper V or leave it off ?

[bigdata]

ok both commands work, I restarted my PC, always the same problem

[bigdata]

Hi,

I found the problem that came from the security of Windows: it is the isolation of the kernel which was activated and which does not allow virtulization !

if someone has the same problem, you can suggest it.

Anyway, thanks for your help.

[scottgus1]

it is the isolation of the kernel which was activated

Could this have been: "Windows Defender > Device Security > Core Isolation"?