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-api

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

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Squeezed + slow domain = broken dynamic memory
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; bh=lxFp9Tuwd+KlSPOtT8oAh8BczXrHWS3J5mFqkTYGNLQ=; b=p1x+Q+L7otqzOMo8APEJVVFdqotlFV8ReAI3z9je2MgLYeDhBq73kJk7y5ALyGWSFD XLrlarAaK7AzRmxBWB+g57f7B4iNu6BgxoK5iCZ2+kcLi8SzYLj5k1yJSeBtYC97zOY/ r/HYUvG6cvBSCxKC12oaVK8qOx9lI4Xe5R51g=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
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?

Thanks.

---
wBR, George Shuklin
 


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>