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

[Xen-API] Squeezed + slow domain = broken dynamic memory

  • To: xen-api@xxxxxxxxxxxxxxxxxxx
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
  • Date: Fri, 14 Jan 2011 19:00:46 +0300
  • Delivery-date: Fri, 14 Jan 2011 08:01:07 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=nnF7GerEtZTQXCuh2eNpn2X3kSHWIpYpivmHcIqEgmTc1qcv4HL7CxhQFfuPzSJvUe iZrNJsUDF/b6rMk1skz0uZ+0ek63mgJRIrRfWIPbGTpVjNdTvrrO06ZZzBKayaRm4pgD 1AGoXMtgQV/XqhNjx2/oaL3IoC3YTKPy2/W9k=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

Good day.

I found strange limitation in squeezed code: if domain's balloon does
not reply to memory change request it marked as 'uncooperative'.

This cause stops to react to vm-memory-dynamic-set commands and stay
until xe toolstak restarted.

As I understand this was done for fast memory regulation. Is any way to
disable this behavior? (And if some domain's balloon will not reply
ever, will it stops to work squeezed with other domains?)

Other question: can I restart squeezed without restarting xapi? Will it
break something?


wBR, George Shuklin

xen-api mailing list



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