Hi group,
I have a short, maybe stupid
question, where or how can I see the available
memory. Not the memory of each VM I need to know
how much memory is availably global wide. (Short-term and
Long-term memory)
Regards York
add cpu and hdd activity and all that as well lol. xentop is another way to only show only activity for each vm but I find it more accurate then qubes-manager.
Before 3.1 I use to just add all the ram up from all the vms with a calculator, but after 3.1 they changed the way how dom0 handles ram, probaby for a very good reason, but there is now now way to tell for me when what vm is giving back ram or not. or how much total being used or free.
what I do is show inactive vms and keep qubes-manager open at all time and look for triangles to see if there is a problem in a vm to shut it down when needed. Like Justin Cooper(Salute) for Hillary's server haha unplug it(Shut it down) for a second and restart it see if it persists.
I never saw in a Campaign, a candidate say go to my website and we will be fact checking everything in real time haha. Pioneer.
if you get really paranoid just wipe the vm and recreate it.
Hi,
I'm answering my question by myself because I think I found a
solution for my question. The command "xl info" show at least the
virtual memory, but I think it would be a nice thing at the Qubes
VM Manager to show the hardware info global wide ;)
Regards York
--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/abc91a4b-8495-cdd2-c4dd-f7205fab7681%40cryptea.net.
For more options, visit https://groups.google.com/d/optout.
Its still confusing to me to figure exactly how much ram i have available to use for vms. or if all memory is being given back when shutting things down.
In 3.0 all memory was loaded by dom0. So I would just watch the qubes-manager and make sure missing memory from dom0 matched up to total of the vms. But since 3.1 though dom0 is limited to 4gb so accounting for all the memory manually that way is not possible anymore.
I figure I need at least 1700mbs for dom0 before things start crashing and I just consider my available memory w/e is extra in dom0.
this because I don't have alot of ram and never have more then 4 available anyways.