Am Dienstag, den 10.06.2008, 22:54 -0700 schrieb John R Pierce:
Ruslan Sivak wrote:
John R Pierce wrote:
whats cat /proc/meminfo say?
# cat /proc/meminfo
MemTotal: 6104064 kB
...
HighTotal: 0 kB
HighFree:0 kB
LowTotal: 6104064 kB
LowFree:
On Wed, Jun 11, 2008 at 9:04 AM, henry ritzlmayr [EMAIL PROTECTED] wrote:
How many VMs are running and how much memory do they consume?
This memory is not shown in DOM0 any more.
The total memory should be visible within xentop.
Or with :
# virsh nodeinfo
CPU model: x86_64
Tim Verhoeven wrote:
On Wed, Jun 11, 2008 at 9:04 AM, henry ritzlmayr [EMAIL PROTECTED] wrote:
How many VMs are running and how much memory do they consume?
This memory is not shown in DOM0 any more.
The total memory should be visible within xentop.
Or with :
# virsh nodeinfo
CPU
On Wed, Jun 11, 2008 at 4:46 PM, Ruslan Sivak [EMAIL PROTECTED] wrote:
While it seems to make sense (and both xentop and virsh nodeinfo) show the
right amount of memory, even when I shut down one of the VM's, free and top
still think I only have 6GB of ram.
That is normal, the memory that was
Tim Verhoeven wrote:
On Wed, Jun 11, 2008 at 4:46 PM, Ruslan Sivak [EMAIL PROTECTED] wrote:
While it seems to make sense (and both xentop and virsh nodeinfo) show the
right amount of memory, even when I shut down one of the VM's, free and top
still think I only have 6GB of ram.
That
MHR wrote:
On Wed, Jun 11, 2008 at 8:36 AM, Ruslan Sivak [EMAIL PROTECTED] wrote:
I guess it has something to do with the ballooning driver for Dom0. It
looks like I just tried to allocation too much memory to DomU and the box
went down hard. I think there's a setting in xen to the min
On Wed, Jun 11, 2008 at 10:29 AM, Ruslan Sivak [EMAIL PROTECTED] wrote:
Are you talking about VMware Server 1?
Yes.
Isn't there an issue with only being
able to allocate 3.4GB of ram or something to that point? I guess it
wouldn't be an issue since I only have 8GB of ram on this box,
7 matches
Mail list logo
