using Parallels Desktop Pro 11.1.3 reading the parallels KB, it appears that suspending and pausing a VM are essentially the same as far as resources go. the kb states that the VM will release memory and not use any CPU cycles when in a paused state, same as a suspended VM. however suspending will allow you to actually close parallels desktop and restart your mac. a VM in a paused state will be reset if you close parallels and/or restart your mac. but, when i look at resources, i notice that my paused VM is still wired to the memory that was allocated to the VM and even consumes a small amount of CPU cycles (less than 1%). so is the KB incorrect? am i missing something? or is there a bug/problem with the way parallels pauses a VM?