Hi folks,
Occasionally I will have a VM lock up (UI remains on screen but windows Dow
not respond) and notice that the MEM size in xentop is greater than the
MAXMEM value in xentop, while at least one associated cpu is spinning
(xentop shows state as perpetually r aka running).
Memory ballooning
Sorry for the double post, I'm unfamiliar with google groups. Floyd: I'll
keep that in mind regarding the tools he suggests. For one, I'm not
installing chrome anytime soon. I'll try to stick to open source, but
honestly, I'm probably gonna focus on maintaining anonymity and
effectiveness with
I appreciate all the responses. The AppVM approached turned out to be ideal
anyway: what didn't get installed via pip to the templateVM got installed
to a dedicated OSINT "template" AppVM. That way, like steve suggested, I
can clone it at will so I can have a clean start point each time.
As an
Attempted fix: try a fedora based install. It seems successful thus far, it
installed following the same process. Just vi when making the config file
vs using nano since its not on the fedora based template.
Steps to be modified from cited guide:
