1

Activity monitor shows me that I have 11Gb wired but only 5Gb used for 2 processes (others are neglible). Where are other 6GB? When I try to start new virtual machine with 500M RAM it says that I do not have enough so looks like this memory is indeed used.

Update: It turned out that Parallels was using 12Gb for windows by default. Still I don't know where to look for actual memory usage.

enter image description here enter image description here

  • 1
    Don't supposed you could sort by "Real Mem" and take another screenshot for us? Note that the two top processes there are taking 8GB alone. – Alistair McMillan Feb 9 '15 at 16:55
  • 1
    So you have a total of 16GB RAM. Used 15.92. You also have 11GB wired memory (information that can not be moved due to the current usage (swap). – Ruskes Feb 9 '15 at 16:56
  • The VM is looking at the Memory used and since it is (currently) 15.92GB it tells you it can not run. What is interesting is you have huge Kernel memory usage? why is that? what is it doing? – Ruskes Feb 9 '15 at 17:20
  • Uploaded second screenshot – Poma Feb 9 '15 at 18:41
  • @Buscar웃 so it is actually using all 15.9G. But I don't see any apps using that much, the numbers just doesn't add up. – Poma Feb 9 '15 at 18:42
1

Difficult to find any hard and fast sources here but I think the problem you are seeing is because you are running two hypervisors at the same time.

There are various places online where you can find people discussing problems when people try to run various combinations of Parallels, Fusion and VirtualBox at the same time.

I thought this post from one of the VirtualBox developers was particularly interesting:

VT-x [the virtualisation tech inside Intel processors] is designed such that there can only be one entity using it at a time. That's why you can't use VT-x when it's already in use by, say, Hyper-V (and why Type 1 hypervisors suck :P ).

One relatively minor difference with OS X is that it's currently the only OS which has APIs to enable and disable VT-x. Windows/Linux/Solaris just don't care and everything is up to the hypervisor. But that is really a minor difference.

The short story is that VT-x is not designed to be shared (that's meant to be a security feature). Because operating systems typically do not offer VT-x management APIs, one and only one hypervisor "owns" VT-x on a given logical processor at any moment. The way to "share" VT-x is to initialize and un-initialize VT-x (aka enter/leave VMX root mode) around every execution of guest code. Hypervisor A comes in, enables VT-x, runs guest code, disables VT-x. Hypervisor B does the same. If both/all hypervisors do this, VT-x can be "shared".

So my guess is that the two hypervisors are trying to share the virtualisation features of the Intel chip in your machine, but one (or both) of them has caused the system to loss track of the resources on your machine.

I'd try closing one and then the other to see if the memory figures return to something normal. If closing both doesn't help, I'd reboot and start again.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .