virtualbox.org

Hi,

I hope someone here can help me. If I try to install a new or import a Virtualbox allways showes me a Guru Error.

Cheers,
Jonas

00:00:04.107865 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:04.178523 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

Try disabling Hyper-v.

00:00:03.905490 Host RAM: 8113MB (7.9GB) total, 1372MB available
...
00:00:04.107557 RamSize <integer> = 0x0000000080000000 (2 147 483 648, 2 048 MB)

Then add more RAM to your host, or reduce the allocation to the guest OS, because you can't afford the amount you already allocated to the VM.

Then choose the correct OS template: Windows 7 is NOT the correct template to use with Windows Server 2019. And incidentally, I doubt you'll find Windows Server 2019 very pleasant running with such restrictions on RAM and CPU.

00:00:04.107554 NumCPUs <integer> = 0x0000000000000001 (1)
00:00:04.107756 VRamSize <integer> = 0x0000000001200000 (18 874 368, 18 MB)

No way 1 core and 18MB graphics RAM is enough for any modern Windows install. 2 cores and 128MB is what you need.

Hi,

Thanks for the reply but it still doesn't work.

Jonas.Stadler wrote:it still doesn't work.

Because you still have Hyper-V running:

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

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

RAM is still tight, even tighter than before:

00:00:03.934383 Host RAM: 8113MB (7.9GB) total, 607MB available
00:00:04.144095 RamSize <integer> = 0x0000000080000000 (2 147 483 648, 2 048 MB)
00:00:04.144319 VRamSize <integer> = 0x0000000001200000 (18 874 368, 18 MB)

Reboot your host then run only Virtualbox. Leave other apps off until the VM is running so it can get its block of RAM. With 3D acceleration off you may find low Video RAM is OK.

Still Windows 7 template:

00:00:04.104865 Guest OS type: 'Windows7_64'

Number of processors still 1:

00:00:04.144093 NumCPUs <integer> = 0x0000000000000001 (1)

Set the processor slider to 2.

Jonas.Stadler wrote: it still doesn't work.

Well, that's hardly a surprise since you don't seem to have fixed a single one of the config issues I raised.