[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] How does live relocation work in xen 3.1?

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Ying Zhang" <zhangying07@xxxxxxxxx>
  • Date: Sun, 29 Jul 2007 11:47:18 +0800
  • Delivery-date: Sat, 28 Jul 2007 20:45:02 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=kjkS5buKcIqJBEZ6GWISZ0crm2qyxmTqBHGP+a5Oaih4h7jbZX85BTnC8n16duhMCNS3xY6HyERcSn7nAVBk+YLNdHhcbIq9lbZ04qFpwI+SjkUrka38o8Rdwhh+mTHbX5mIygyKzGW7QyM7Xss5XkEwphwAn8OP3JmKlxUhxvo=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

As key features of xen 3.1,live relocation and dynamic memory control enables dynamic resource scheduling and "no-downtime maintenance" of Microsoft Windows-based virtual infrastructures.
I'm interested in how it works. I try to use the commands "xm mem-set" ,"xm list" and "xm top",but it seems of no use. The fullvirtualized windows guest still maintains the initial maximum memory.However,those commands take effect in domain 0.So I think it will also take effect in paravirtualized guests.Am I right?
Is there anyone who can tell me how the features work in fullvirtualized windows guest? Many thanks.


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.