0

My guest is a vm ubuntu 16.04 on Virtualbox with host windows. Once I start vm, it goes to pause automatically several times. Without changing the amount of memory for guest, is there a way to disable auto-pause ? (This state is a warning from VB to let me know windows might experience lack of memory) Kian William

Kian William Nowrouzian
  • 1
  • I assigned like 1024 M to guest, for host I used readyboost to make up the amount of ram I assigned to guest. Amount in readyboost is around 4096 MB and the ram to my laptop is 2 GB. If readyboost is considered a different type of ram, the answer to your question is positive. – Kian William Nowrouzian Mar 07 '17 at 07:14

2 Answers2

0

I notice this situation on my CentOS VS while I have another Ubuntu VS opened for weeks. When I close that Ubuntu, CentOS stop auto pause. So I think it maybe the memory issue.

guang chen
  • 1
0

Using different RAM types, memory caching applications or other host techniques that affect access to physical RAM may affect RAM allocation of the guest in VirtualBox.

If we can't avoid such techniques in the host we may try to enable pre-allocation of RAM for a virtual machine with the following command:

VBoxManage setextradata <vmname> VBoxInternal/RamPreAlloc 1

Another cause for issue with RAM allocation may come from guests that had memory ballooning enabled.

Takkat
  • 142,284
  • I did the command above, the host window went nut, quite frozen and vm did not start at all in such a way that I did a cold boot for host. – Kian William Nowrouzian Mar 10 '17 at 07:39
  • Also, to disable RamPreAlloc , assigning 0 to it is enough? I mean in the body of the same command. – Kian William Nowrouzian Mar 11 '17 at 08:30
  • A crash on starting a VM set to pre-allocate its RAM further indicates there is a hardwar issue with your RAM. Check for RAM errors with memtest. – Takkat Mar 11 '17 at 08:40
  • I can not call it a crash, I assigned all ram to vm according to the RamPreAlloc 1, it is quite natural when I try to use a host program , it does not respond. Regarding vm, I was not exact, it started , but it loaded about 29 percent and very slowly, may be if I waited more, it would run. Any way, I returned back RamPreAlloc to 0 via vboxmanage command again, is it enough or there are other things I got to do? – Kian William Nowrouzian Mar 11 '17 at 12:01
  • @KianWilliamNowrouzian: you may also want to assign an execution cap to your CPU in case you use all cores for your VM. – Takkat Mar 11 '17 at 14:40