WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] VMX and resizing memory

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] VMX and resizing memory
From: "James Miller" <jimm@xxxxxxxxxxxxxxx>
Date: Fri, 14 Jul 2006 14:23:07 -0500
Delivery-date: Fri, 14 Jul 2006 12:23:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: jimm@xxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Has anyone had any success with using mem-set and mem-max in a VMX based
domU (windows 2003 in this case)?  I'm running Xen 3.0-unstable w/2GB RAM

Initial Win2003_base xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      512     1 r----- 49838.0
Win2003_base                      21      512     1 -b----    18.3


xm mem-set 21 768
 xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      512     1 r----- 49844.3
Win2003_base                      21      768     1 -b----    19.1

But the Win2003 domU doesn't see the additional RAM

The same is true if I run 'xm mem-set 21 384' to lower the amount of ram.
The domU doesn't see the smaller amount of RAM.
 xm list
Name                              ID Mem(MiB) VCPUs State  Time(s)
Domain-0                           0      512     1 r----- 49850.5
Win2003_base                      21      384     1 -b----    22.0


Also, I've noticed setting 'extra="mem-max=1024"' in the config file doesn't
seem to have the desired effect:
xentop - 13:56:54   Xen 3.0-unstable
Mem: 3397720k total, 1222484k used, 2175236k free    CPUs: 2 @ 3000MHz
NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%)
Win2003_base --b---  15    0.0     528384   15.6     541904      15.9

However if I run from the cli 'xm mem-max dom# 1024' I DO get the desired
effect:
NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%)
Win2003_base --b---         17    0.5     528384   15.6    1048576

Here's my config:
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 512
extra="mem-max=1024"
name = "Win2003_base"
vcpus=1
pae=0
acpi=0
apic=1
cpus = ""
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'file:/xen/xenimages/Win2003_base.img,ioemu:hda,w' ]
on_poweroff = 'destroy'
on_reboot   = 'destroy'
on_crash    = 'destroy'
device_model = '/usr/lib/xen/bin/qemu-dm'
cdrom='/data/en_windows_server_2003_standardsp1_enterprisesp1.iso'
boot='c'
sdl=0
vnc=1
vncviewer=0
stdvga=0
serial='pty'
ne2000=0



Thanks,
Jim


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] VMX and resizing memory, James Miller <=