[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
New dtc-xen bugfix 0.5.13 release
- To: dtcdev@xxxxxxxxxx, dtcannounce <dtcannounce@xxxxxxxxxx>, 598387@xxxxxxxxxxxxxxx
- Subject: New dtc-xen bugfix 0.5.13 release
- From: Thomas Goirand <thomas@xxxxxxxxxx>
- Date: Fri, 01 Oct 2010 15:31:33 +0800
- Delivered-to: gplhost.sg_dtcannounce@xxxxxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; s=postfix; bh=H4gnbsdMIiMhPVHs/whJrO xDU84=; b=cg8Uh7kMfBNy17kESNRSV32tOuQjLPyjsGcLrmodsJ9kcC9aapllBh jMpyRM3SjUHtblW7/UfV8ph6wbyj2WTIzyxEa4ELwga0EWNWuhZ3FYNRcvnD6/5o ggIQ3SgpdgmWfVvVKG2KE4070CVqCNIsmV7xuyRJdzl2uozd34+pk=
- Domainkey-signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; q=dns; s=postfix; b=Z/caWm/eAOIftFvu au2hBtRPq3aFBi8/3NPJb87kWhyOPN1qS8FIV++uYYz0i20HEI0whtnQsZy8DwSI WJWxaM0B1kNRLbJgKv8T/AbiALJDMXbnuKqbAaf8MrNV1410hgTIRQyYCMCjrLl0 Y0OCCylFwhKu3c0YmDUdxavLj8g=
- Openpgp: id=98EF9A49
- Organization: GPLHost
- Reply-to: dtcdev@xxxxxxxxxx
- User-agent: Mozilla-Thunderbird 126.96.36.199 (X11/20100329)
This is an announcement of a bugfix release for DTC-Xen.
I have released few days ago a new version 0.5.13, that corrects a quite
bad issue, related to standard output and error redirections when
starting or stopping a VM. The corresponding patches are here:
What happened is that when doing xm start/stop/shutdown, dtc-xen was
trying to redirect stderr/stdout so that it could catch an eventual
error message. The issue is that it didn't release it, so that later,
the dataCollector that does "xm list" didn't work. Worse, the output of
"xm list", after a xm stop/start/shutdown (any of them), was going in an
internal variable of dtc-xen (localsysout / localsyserr). The result was
something that appeared as a memory leak, with these 2 variable getting
the content of the output of "xm list" every minutes.
In short, dtc-xen could fill-up the memory of your dom0, refuse to stop,
and has its statistic reporting feature broken, as soon as you are
trying to start, stop or shutdown a VM through DTC-Xen's soap server.
The version 0.5.12 was an attempt to solve this, it did, but then xm
start/stop/shutdown didn't work anymore, which is why the same day,
DTC-Xen 0.5.13 has been released.
If you are running DTC-Xen 0.5.x, you should upgrade immediately.
P.S: As we are now adding new features in DTC-Xen for supporting VZ, and
I hope also KVM and Virtualbox soon, our Git has now an up-to-date
stable-0.5 branch, while we will be working on the master branch as of
today. New features will *not* get into the 0.5.x branch anymore, and
new features in DTC-Xen will not be released until we have support for
other virtualization technologies working.
Do not reply to this mail, subscribe to dtcdev@xxxxxxxxxx instead
To unsubscribe send a mail to dtcannounce-unsubscribe@xxxxxxxxxx