From xen-announce-bounces@lists.xen.org Wed Oct 01 12:04:19 2014
Return-path: <xen-announce-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 01 Oct 2014 12:04:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-announce-bounces@lists.xen.org>)
	id 1XZIcf-0000se-4C; Wed, 01 Oct 2014 12:03:09 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <iwj@xenbits.xen.org>)
	id 1XZIcd-0000sM-V6; Wed, 01 Oct 2014 12:03:08 +0000
Received: from [193.109.254.147:37528] by server-10.bemta-14.messagelabs.com
	id A3/4F-01463-B7DEB245; Wed, 01 Oct 2014 12:03:07 +0000
X-Env-Sender: iwj@xenbits.xen.org
X-Msg-Ref: server-4.tower-27.messagelabs.com!1412164985!12734774!1
X-Originating-IP: [50.57.168.107]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.12.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17692 invoked from network); 1 Oct 2014 12:03:06 -0000
Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107)
	by server-4.tower-27.messagelabs.com with AES256-SHA encrypted SMTP;
	1 Oct 2014 12:03:06 -0000
Received: from xenbits.xen.org ([50.57.170.242])
	by mail.xen.org with esmtp (Exim 4.72)
	(envelope-from <iwj@xenbits.xen.org>)
	id 1XZIcT-000229-Bw; Wed, 01 Oct 2014 12:02:57 +0000
Received: from iwj by xenbits.xen.org with local (Exim 4.72)
	(envelope-from <iwj@xenbits.xen.org>)
	id 1XZIcT-0004aF-1v; Wed, 01 Oct 2014 12:02:57 +0000
Date: Wed, 01 Oct 2014 12:02:57 +0000
Message-Id: <E1XZIcT-0004aF-1v@xenbits.xen.org>
Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.428 (Entity 5.428)
To: xen-announce@lists.xen.org, xen-devel@lists.xen.org,
	xen-users@lists.xen.org, oss-security@lists.openwall.com
From: Xen.org security team <security@xen.org>
Cc: "Xen.org security team" <security@xen.org>
Subject: [Xen-announce] Xen Security Advisory 108 (CVE-2014-7188) - Improper
 MSR range used for x2APIC emulation
X-BeenThere: xen-announce@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Xen announcements \(low volume\)" <xen-announce.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-announce@lists.xen.org>
List-Help: <mailto:xen-announce-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=subscribe>
Sender: xen-announce-bounces@lists.xen.org
Errors-To: xen-announce-bounces@lists.xen.org


--=separator
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

              Xen Security Advisory CVE-2014-7188 / XSA-108
                              version 4

              Improper MSR range used for x2APIC emulation

UPDATES IN VERSION 4
====================

Public release.

ISSUE DESCRIPTION
=================

The MSR range specified for APIC use in the x2APIC access model spans
256 MSRs. Hypervisor code emulating read and write accesses to these
MSRs erroneously covered 1024 MSRs. While the write emulation path is
written such that accesses to the extra MSRs would not have any bad
effect (they end up being no-ops), the read path would (attempt to)
access memory beyond the single page set up for APIC emulation.

IMPACT
======

A buggy or malicious HVM guest can crash the host or read data
relating to other guests or the hypervisor itself.

VULNERABLE SYSTEMS
==================

Xen 4.1 and onward are vulnerable.

Only x86 systems are vulnerable.  ARM systems are not vulnerable.

MITIGATION
==========

Running only PV guests will avoid this vulnerability.

CREDITS
=======

This issue was discovered Jan Beulich at SUSE.

RESOLUTION
==========

Applying the attached patch resolves this issue.

xsa108.patch        xen-unstable, Xen 4.4.x, Xen 4.3.x, Xen 4.2.x

$ sha256sum xsa108*.patch
cf7ecf4b4680c09e8b1f03980d8350a0e1e7eb03060031788f972e0d4d47203e  xsa108.patch
$
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJUK+1fAAoJEIP+FMlX6CvZ6cwH+wdcnTCTdyAMc8bmQv+IxrMN
ue5rBYdX0b7CnnC2uCrwPssygna2cxTcVhJsU0eZk5OVrIU5rQ3PKtmFtxMwa3WS
my/vtyftTmoxAzftUKgpDFeicmZXlot3aowfRIiIc+GFZ59zAjDL2yQ0xMR1mJio
7SXl+dkcUPj5nXaeK1gFozJ8XNF+wArNQUPv0xUBIg4NSjQyqa7CMCZ5Q3IuJ53S
hKY37/MSoOViDORDPkeVr3BoSb7atYZSPwibqEUjeL5f+eXyVkbD0MkLQgu1ERtZ
p+dc+DTaRYm77LrDM+npZ+j1uSoVqdVzXtNYe6GZmbNRVXjbhJ+gJyJBcpy/a5Q=
=m0tK
-----END PGP SIGNATURE-----

--=separator
Content-Type: application/octet-stream; name="xsa108.patch"
Content-Disposition: attachment; filename="xsa108.patch"
Content-Transfer-Encoding: base64

eDg2L0hWTTogcHJvcGVybHkgYm91bmQgeDJBUElDIE1TUiByYW5nZQoKV2hp
bGUgdGhlIHdyaXRlIHBhdGggY2hhbmdlIGFwcGVhcnMgdG8gYmUgcHVyZWx5
IGNvc21ldGljIChidXQgc3RpbGwKZ2V0cyBkb25lIGhlcmUgZm9yIGNvbnNp
c3RlbmN5KSwgdGhlIHJlYWQgc2lkZSBtaXN0YWtlIHBlcm1pdHRlZAphY2Nl
c3NlcyBiZXlvbmQgdGhlIHZpcnR1YWwgQVBJQyBwYWdlLgoKTm90ZSB0aGF0
IHdoaWxlIHRoaXMgaXNuJ3QgZnVsbHkgaW4gbGluZSB3aXRoIHRoZSBzcGVj
aWZpY2F0aW9uCihkaWdlc3RpbmcgTVNScyAweDgwMC0weEJGRiBmb3IgdGhl
IHgyQVBJQyksIHRoaXMgaXMgdGhlIG1pbmltYWwKcG9zc2libGUgZml4IGFk
ZHJlc3NpbmcgdGhlIHNlY3VyaXR5IGlzc3VlIGFuZCBnZXR0aW5nIHgyQVBJ
QyByZWxhdGVkCmNvZGUgaW50byBhIGNvbnNpc3RlbnQgc2hhcGUgKGVsc2V3
aGVyZSBhIDI1NiByYXRoZXIgdGhhbiAxMDI0IHdpZGUKd2luZG93IGlzIGJl
aW5nIHVzZWQgdG9vKS4gVGhpcyB3aWxsIGJlIGRlYWx0IHdpdGggc3Vic2Vx
dWVudGx5LgoKVGhpcyBpcyBYU0EtMTA4LgoKU2lnbmVkLW9mZi1ieTogSmFu
IEJldWxpY2ggPGpiZXVsaWNoQHN1c2UuY29tPgoKLS0tIGEveGVuL2FyY2gv
eDg2L2h2bS9odm0uYworKysgYi94ZW4vYXJjaC94ODYvaHZtL2h2bS5jCkBA
IC00MzgwLDcgKzQzODAsNyBAQCBpbnQgaHZtX21zcl9yZWFkX2ludGVyY2Vw
dCh1bnNpZ25lZCBpbnQgCiAgICAgICAgICptc3JfY29udGVudCA9IHZjcHVf
dmxhcGljKHYpLT5ody5hcGljX2Jhc2VfbXNyOwogICAgICAgICBicmVhazsK
IAotICAgIGNhc2UgTVNSX0lBMzJfQVBJQ0JBU0VfTVNSIC4uLiBNU1JfSUEz
Ml9BUElDQkFTRV9NU1IgKyAweDNmZjoKKyAgICBjYXNlIE1TUl9JQTMyX0FQ
SUNCQVNFX01TUiAuLi4gTVNSX0lBMzJfQVBJQ0JBU0VfTVNSICsgMHhmZjoK
ICAgICAgICAgaWYgKCBodm1feDJhcGljX21zcl9yZWFkKHYsIG1zciwgbXNy
X2NvbnRlbnQpICkKICAgICAgICAgICAgIGdvdG8gZ3BfZmF1bHQ7CiAgICAg
ICAgIGJyZWFrOwpAQCAtNDUwNiw3ICs0NTA2LDcgQEAgaW50IGh2bV9tc3Jf
d3JpdGVfaW50ZXJjZXB0KHVuc2lnbmVkIGludAogICAgICAgICB2bGFwaWNf
dGR0X21zcl9zZXQodmNwdV92bGFwaWModiksIG1zcl9jb250ZW50KTsKICAg
ICAgICAgYnJlYWs7CiAKLSAgICBjYXNlIE1TUl9JQTMyX0FQSUNCQVNFX01T
UiAuLi4gTVNSX0lBMzJfQVBJQ0JBU0VfTVNSICsgMHgzZmY6CisgICAgY2Fz
ZSBNU1JfSUEzMl9BUElDQkFTRV9NU1IgLi4uIE1TUl9JQTMyX0FQSUNCQVNF
X01TUiArIDB4ZmY6CiAgICAgICAgIGlmICggaHZtX3gyYXBpY19tc3Jfd3Jp
dGUodiwgbXNyLCBtc3JfY29udGVudCkgKQogICAgICAgICAgICAgZ290byBn
cF9mYXVsdDsKICAgICAgICAgYnJlYWs7Cg==

--=separator
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-announce mailing list
Xen-announce@lists.xen.org
http://lists.xen.org/xen-announce
--=separator--


From xen-announce-bounces@lists.xen.org Wed Oct 01 12:04:19 2014
Return-path: <xen-announce-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 01 Oct 2014 12:04:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-announce-bounces@lists.xen.org>)
	id 1XZIcf-0000se-4C; Wed, 01 Oct 2014 12:03:09 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <iwj@xenbits.xen.org>)
	id 1XZIcd-0000sM-V6; Wed, 01 Oct 2014 12:03:08 +0000
Received: from [193.109.254.147:37528] by server-10.bemta-14.messagelabs.com
	id A3/4F-01463-B7DEB245; Wed, 01 Oct 2014 12:03:07 +0000
X-Env-Sender: iwj@xenbits.xen.org
X-Msg-Ref: server-4.tower-27.messagelabs.com!1412164985!12734774!1
X-Originating-IP: [50.57.168.107]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.12.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17692 invoked from network); 1 Oct 2014 12:03:06 -0000
Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107)
	by server-4.tower-27.messagelabs.com with AES256-SHA encrypted SMTP;
	1 Oct 2014 12:03:06 -0000
Received: from xenbits.xen.org ([50.57.170.242])
	by mail.xen.org with esmtp (Exim 4.72)
	(envelope-from <iwj@xenbits.xen.org>)
	id 1XZIcT-000229-Bw; Wed, 01 Oct 2014 12:02:57 +0000
Received: from iwj by xenbits.xen.org with local (Exim 4.72)
	(envelope-from <iwj@xenbits.xen.org>)
	id 1XZIcT-0004aF-1v; Wed, 01 Oct 2014 12:02:57 +0000
Date: Wed, 01 Oct 2014 12:02:57 +0000
Message-Id: <E1XZIcT-0004aF-1v@xenbits.xen.org>
Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8"
Content-Transfer-Encoding: binary
MIME-Version: 1.0
X-Mailer: MIME-tools 5.428 (Entity 5.428)
To: xen-announce@lists.xen.org, xen-devel@lists.xen.org,
	xen-users@lists.xen.org, oss-security@lists.openwall.com
From: Xen.org security team <security@xen.org>
Cc: "Xen.org security team" <security@xen.org>
Subject: [Xen-announce] Xen Security Advisory 108 (CVE-2014-7188) - Improper
 MSR range used for x2APIC emulation
X-BeenThere: xen-announce@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Xen announcements \(low volume\)" <xen-announce.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-announce@lists.xen.org>
List-Help: <mailto:xen-announce-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=subscribe>
Sender: xen-announce-bounces@lists.xen.org
Errors-To: xen-announce-bounces@lists.xen.org


--=separator
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

              Xen Security Advisory CVE-2014-7188 / XSA-108
                              version 4

              Improper MSR range used for x2APIC emulation

UPDATES IN VERSION 4
====================

Public release.

ISSUE DESCRIPTION
=================

The MSR range specified for APIC use in the x2APIC access model spans
256 MSRs. Hypervisor code emulating read and write accesses to these
MSRs erroneously covered 1024 MSRs. While the write emulation path is
written such that accesses to the extra MSRs would not have any bad
effect (they end up being no-ops), the read path would (attempt to)
access memory beyond the single page set up for APIC emulation.

IMPACT
======

A buggy or malicious HVM guest can crash the host or read data
relating to other guests or the hypervisor itself.

VULNERABLE SYSTEMS
==================

Xen 4.1 and onward are vulnerable.

Only x86 systems are vulnerable.  ARM systems are not vulnerable.

MITIGATION
==========

Running only PV guests will avoid this vulnerability.

CREDITS
=======

This issue was discovered Jan Beulich at SUSE.

RESOLUTION
==========

Applying the attached patch resolves this issue.

xsa108.patch        xen-unstable, Xen 4.4.x, Xen 4.3.x, Xen 4.2.x

$ sha256sum xsa108*.patch
cf7ecf4b4680c09e8b1f03980d8350a0e1e7eb03060031788f972e0d4d47203e  xsa108.patch
$
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJUK+1fAAoJEIP+FMlX6CvZ6cwH+wdcnTCTdyAMc8bmQv+IxrMN
ue5rBYdX0b7CnnC2uCrwPssygna2cxTcVhJsU0eZk5OVrIU5rQ3PKtmFtxMwa3WS
my/vtyftTmoxAzftUKgpDFeicmZXlot3aowfRIiIc+GFZ59zAjDL2yQ0xMR1mJio
7SXl+dkcUPj5nXaeK1gFozJ8XNF+wArNQUPv0xUBIg4NSjQyqa7CMCZ5Q3IuJ53S
hKY37/MSoOViDORDPkeVr3BoSb7atYZSPwibqEUjeL5f+eXyVkbD0MkLQgu1ERtZ
p+dc+DTaRYm77LrDM+npZ+j1uSoVqdVzXtNYe6GZmbNRVXjbhJ+gJyJBcpy/a5Q=
=m0tK
-----END PGP SIGNATURE-----

--=separator
Content-Type: application/octet-stream; name="xsa108.patch"
Content-Disposition: attachment; filename="xsa108.patch"
Content-Transfer-Encoding: base64

eDg2L0hWTTogcHJvcGVybHkgYm91bmQgeDJBUElDIE1TUiByYW5nZQoKV2hp
bGUgdGhlIHdyaXRlIHBhdGggY2hhbmdlIGFwcGVhcnMgdG8gYmUgcHVyZWx5
IGNvc21ldGljIChidXQgc3RpbGwKZ2V0cyBkb25lIGhlcmUgZm9yIGNvbnNp
c3RlbmN5KSwgdGhlIHJlYWQgc2lkZSBtaXN0YWtlIHBlcm1pdHRlZAphY2Nl
c3NlcyBiZXlvbmQgdGhlIHZpcnR1YWwgQVBJQyBwYWdlLgoKTm90ZSB0aGF0
IHdoaWxlIHRoaXMgaXNuJ3QgZnVsbHkgaW4gbGluZSB3aXRoIHRoZSBzcGVj
aWZpY2F0aW9uCihkaWdlc3RpbmcgTVNScyAweDgwMC0weEJGRiBmb3IgdGhl
IHgyQVBJQyksIHRoaXMgaXMgdGhlIG1pbmltYWwKcG9zc2libGUgZml4IGFk
ZHJlc3NpbmcgdGhlIHNlY3VyaXR5IGlzc3VlIGFuZCBnZXR0aW5nIHgyQVBJ
QyByZWxhdGVkCmNvZGUgaW50byBhIGNvbnNpc3RlbnQgc2hhcGUgKGVsc2V3
aGVyZSBhIDI1NiByYXRoZXIgdGhhbiAxMDI0IHdpZGUKd2luZG93IGlzIGJl
aW5nIHVzZWQgdG9vKS4gVGhpcyB3aWxsIGJlIGRlYWx0IHdpdGggc3Vic2Vx
dWVudGx5LgoKVGhpcyBpcyBYU0EtMTA4LgoKU2lnbmVkLW9mZi1ieTogSmFu
IEJldWxpY2ggPGpiZXVsaWNoQHN1c2UuY29tPgoKLS0tIGEveGVuL2FyY2gv
eDg2L2h2bS9odm0uYworKysgYi94ZW4vYXJjaC94ODYvaHZtL2h2bS5jCkBA
IC00MzgwLDcgKzQzODAsNyBAQCBpbnQgaHZtX21zcl9yZWFkX2ludGVyY2Vw
dCh1bnNpZ25lZCBpbnQgCiAgICAgICAgICptc3JfY29udGVudCA9IHZjcHVf
dmxhcGljKHYpLT5ody5hcGljX2Jhc2VfbXNyOwogICAgICAgICBicmVhazsK
IAotICAgIGNhc2UgTVNSX0lBMzJfQVBJQ0JBU0VfTVNSIC4uLiBNU1JfSUEz
Ml9BUElDQkFTRV9NU1IgKyAweDNmZjoKKyAgICBjYXNlIE1TUl9JQTMyX0FQ
SUNCQVNFX01TUiAuLi4gTVNSX0lBMzJfQVBJQ0JBU0VfTVNSICsgMHhmZjoK
ICAgICAgICAgaWYgKCBodm1feDJhcGljX21zcl9yZWFkKHYsIG1zciwgbXNy
X2NvbnRlbnQpICkKICAgICAgICAgICAgIGdvdG8gZ3BfZmF1bHQ7CiAgICAg
ICAgIGJyZWFrOwpAQCAtNDUwNiw3ICs0NTA2LDcgQEAgaW50IGh2bV9tc3Jf
d3JpdGVfaW50ZXJjZXB0KHVuc2lnbmVkIGludAogICAgICAgICB2bGFwaWNf
dGR0X21zcl9zZXQodmNwdV92bGFwaWModiksIG1zcl9jb250ZW50KTsKICAg
ICAgICAgYnJlYWs7CiAKLSAgICBjYXNlIE1TUl9JQTMyX0FQSUNCQVNFX01T
UiAuLi4gTVNSX0lBMzJfQVBJQ0JBU0VfTVNSICsgMHgzZmY6CisgICAgY2Fz
ZSBNU1JfSUEzMl9BUElDQkFTRV9NU1IgLi4uIE1TUl9JQTMyX0FQSUNCQVNF
X01TUiArIDB4ZmY6CiAgICAgICAgIGlmICggaHZtX3gyYXBpY19tc3Jfd3Jp
dGUodiwgbXNyLCBtc3JfY29udGVudCkgKQogICAgICAgICAgICAgZ290byBn
cF9mYXVsdDsKICAgICAgICAgYnJlYWs7Cg==

--=separator
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-announce mailing list
Xen-announce@lists.xen.org
http://lists.xen.org/xen-announce
--=separator--


From xen-announce-bounces@lists.xen.org Wed Oct 22 11:28:05 2014
Return-path: <xen-announce-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 22 Oct 2014 11:28:05 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-announce-bounces@lists.xen.org>)
	id 1Xgu3r-00064f-Ea; Wed, 22 Oct 2014 11:26:39 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>) id 1XgtxW-0005Q4-CZ
	for xen-announce@lists.xenproject.org; Wed, 22 Oct 2014 11:20:06 +0000
Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id
	FA/6D-02699-5E297445; Wed, 22 Oct 2014 11:20:05 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-16.tower-21.messagelabs.com!1413976136!8466305!1
X-Originating-IP: [209.85.212.174]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.12.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22569 invoked from network); 22 Oct 2014 11:08:56 -0000
Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com)
	(209.85.212.174)
	by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	22 Oct 2014 11:08:56 -0000
Received: by mail-wi0-f174.google.com with SMTP id r20so1021738wiv.7
	for <xen-announce@lists.xenproject.org>;
	Wed, 22 Oct 2014 04:08:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:content-type:content-transfer-encoding:subject:message-id:date
	:to:mime-version;
	bh=6LNp7zrr7cX15LnnvYf4JQL9ieBGc0J9ln4qmOEN9l4=;
	b=ZOnUc+RWlUMNRc3ZmYRLhUjL7mg8huwtU8UT6aUaFf+VQAK/ojMPIGoXeSDjTOGSUi
	+J7LNZ2+FyqvMqLo8S/1buOGYBzFD5lrPbJ8vlPBDi8Oo+S+YH6E3GMuooB5NCs61fI4
	VWk45t9GYc2dRhDydrG88I1h8RaVZlUXqPzT6C48gH9sVsoWIfIf9897w+9gcAi29xmO
	DH0LJfIwWNdJnx59/ZUqlmqViXSep2wcMERzrqDyODPpVH+Pqvb4jvkEOsNnaiQ0pU/S
	3C+HRG999A6S4zN89qdOzPYvUlqkE3lEGbMXuzwvEMEXuRDnYpUnejGyGSUAwL1772ti
	VH7A==
X-Received: by 10.180.85.68 with SMTP id f4mr28126807wiz.10.1413976136376;
	Wed, 22 Oct 2014 04:08:56 -0700 (PDT)
Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206])
	by mx.google.com with ESMTPSA id
	ma8sm18475015wjb.46.2014.10.22.04.08.54
	for <xen-announce@lists.xenproject.org>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 22 Oct 2014 04:08:55 -0700 (PDT)
From: Lars Kurth <lars.kurth.xen@gmail.com>
Message-Id: <3839E1D1-8FF9-4827-86D2-4826E7EF1812@gmail.com>
Date: Wed, 22 Oct 2014 12:08:53 +0100
To: xen-announce@lists.xenproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
X-Mailman-Approved-At: Wed, 22 Oct 2014 11:26:38 +0000
Subject: [Xen-announce] Xen Project Security Policy Improvements: Get
	Involved
X-BeenThere: xen-announce@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Xen announcements \(low volume\)" <xen-announce.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-announce@lists.xen.org>
List-Help: <mailto:xen-announce-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: xen-announce-bounces@lists.xen.org
Errors-To: xen-announce-bounces@lists.xen.org

Dear Community Members,

The recent XSA-108 vulnerability resulted in a lot of media coverage, which=
 ended up stress-testing some of our policy and security related processes.=
 During the embargo period of XSA-108, the Xen Project Security Team was fa=
ced with some difficult questions of policy interpretation, as well as prac=
tical issues related to pre-disclosure list membership applications.

To ensure more clarity moving forward, the Xen Project Security Team starte=
d a community consultation (http://lists.xenproject.org/archives/html/xen-d=
evel/2014-10/msg00976.html) to improve and better define the project=92s Se=
curity Vulnerability Response Process (http://xenproject.org/security-polic=
y.html). =


In particular we are seeking to clarify the following elements of the polic=
y, which surfaced during the embargo period of XSA-108:
* Sharing of information amongst pre-disclosure list members during an emba=
rgo period
* Deployment of patches on public systems of fixed versions of the Xen Proj=
ect Hypervisor during the embargo period
* Service announcements to non-list-member users during an embargo period
* Clarifying criteria related to pre-disclosure list membership and making =
it easier to verify them
* Processing applications of pre-disclosure list membership during an embar=
go period

For more background and information read the e-mail thread on xen-devel@ ca=
lled Security policy ambiguities =96 XSA-108 process post-mortem (http://li=
sts.xenproject.org/archives/html/xen-devel/2014-10/msg00976.html & http://b=
ugs.xenproject.org/xen/bug/44 to see the entire conversation thread in one =
place).

If you use Xen Project Software in any way, we encourage you to voice your =
thoughts to help formulate and update our security policy to ensure it meet=
s the needs of our entire community. To take part in the discussion please =
send mail to xen-devel@lists.xenproject.org. If you are a member of the lis=
t just reply to the relevant thread. If you are not a member of the mailing=
 list and plan to respond to an e-mail that has already been sent you have =
two easy options:

 * You can reply to the message via our issue tracker (http://bugs.xenproje=
ct.org/xen/bug/44) using the Reply to this message link at the top of the m=
essage; or
 * You can retrieve the mbox from the issue issue tracker, load the thread =
into your mail client and just reply.

Even if you chose not to subscribe to xen-devel@ =96 which you don=92t have=
 to participate =96 you may want to occasionally check the discussion threa=
d activity on this thread, to ensure you are not missing any activity.

Going forward, we will collate community input and propose a revised versio=
n of the policy, which will be formally approved in line with Xen Project G=
overnance. We have not set a specific deadline for the discussion, but aim =
to issue a revised policy within 4 weeks.

Best Regards
Lars
_______________________________________________
Xen-announce mailing list
Xen-announce@lists.xen.org
http://lists.xen.org/xen-announce

From xen-announce-bounces@lists.xen.org Wed Oct 22 11:28:05 2014
Return-path: <xen-announce-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 22 Oct 2014 11:28:05 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-announce-bounces@lists.xen.org>)
	id 1Xgu3r-00064f-Ea; Wed, 22 Oct 2014 11:26:39 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>) id 1XgtxW-0005Q4-CZ
	for xen-announce@lists.xenproject.org; Wed, 22 Oct 2014 11:20:06 +0000
Received: from [85.158.143.35] by server-3.bemta-4.messagelabs.com id
	FA/6D-02699-5E297445; Wed, 22 Oct 2014 11:20:05 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-16.tower-21.messagelabs.com!1413976136!8466305!1
X-Originating-IP: [209.85.212.174]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.12.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22569 invoked from network); 22 Oct 2014 11:08:56 -0000
Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com)
	(209.85.212.174)
	by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	22 Oct 2014 11:08:56 -0000
Received: by mail-wi0-f174.google.com with SMTP id r20so1021738wiv.7
	for <xen-announce@lists.xenproject.org>;
	Wed, 22 Oct 2014 04:08:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:content-type:content-transfer-encoding:subject:message-id:date
	:to:mime-version;
	bh=6LNp7zrr7cX15LnnvYf4JQL9ieBGc0J9ln4qmOEN9l4=;
	b=ZOnUc+RWlUMNRc3ZmYRLhUjL7mg8huwtU8UT6aUaFf+VQAK/ojMPIGoXeSDjTOGSUi
	+J7LNZ2+FyqvMqLo8S/1buOGYBzFD5lrPbJ8vlPBDi8Oo+S+YH6E3GMuooB5NCs61fI4
	VWk45t9GYc2dRhDydrG88I1h8RaVZlUXqPzT6C48gH9sVsoWIfIf9897w+9gcAi29xmO
	DH0LJfIwWNdJnx59/ZUqlmqViXSep2wcMERzrqDyODPpVH+Pqvb4jvkEOsNnaiQ0pU/S
	3C+HRG999A6S4zN89qdOzPYvUlqkE3lEGbMXuzwvEMEXuRDnYpUnejGyGSUAwL1772ti
	VH7A==
X-Received: by 10.180.85.68 with SMTP id f4mr28126807wiz.10.1413976136376;
	Wed, 22 Oct 2014 04:08:56 -0700 (PDT)
Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206])
	by mx.google.com with ESMTPSA id
	ma8sm18475015wjb.46.2014.10.22.04.08.54
	for <xen-announce@lists.xenproject.org>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 22 Oct 2014 04:08:55 -0700 (PDT)
From: Lars Kurth <lars.kurth.xen@gmail.com>
Message-Id: <3839E1D1-8FF9-4827-86D2-4826E7EF1812@gmail.com>
Date: Wed, 22 Oct 2014 12:08:53 +0100
To: xen-announce@lists.xenproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
X-Mailman-Approved-At: Wed, 22 Oct 2014 11:26:38 +0000
Subject: [Xen-announce] Xen Project Security Policy Improvements: Get
	Involved
X-BeenThere: xen-announce@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Xen announcements \(low volume\)" <xen-announce.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-announce@lists.xen.org>
List-Help: <mailto:xen-announce-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: xen-announce-bounces@lists.xen.org
Errors-To: xen-announce-bounces@lists.xen.org

Dear Community Members,

The recent XSA-108 vulnerability resulted in a lot of media coverage, which=
 ended up stress-testing some of our policy and security related processes.=
 During the embargo period of XSA-108, the Xen Project Security Team was fa=
ced with some difficult questions of policy interpretation, as well as prac=
tical issues related to pre-disclosure list membership applications.

To ensure more clarity moving forward, the Xen Project Security Team starte=
d a community consultation (http://lists.xenproject.org/archives/html/xen-d=
evel/2014-10/msg00976.html) to improve and better define the project=92s Se=
curity Vulnerability Response Process (http://xenproject.org/security-polic=
y.html). =


In particular we are seeking to clarify the following elements of the polic=
y, which surfaced during the embargo period of XSA-108:
* Sharing of information amongst pre-disclosure list members during an emba=
rgo period
* Deployment of patches on public systems of fixed versions of the Xen Proj=
ect Hypervisor during the embargo period
* Service announcements to non-list-member users during an embargo period
* Clarifying criteria related to pre-disclosure list membership and making =
it easier to verify them
* Processing applications of pre-disclosure list membership during an embar=
go period

For more background and information read the e-mail thread on xen-devel@ ca=
lled Security policy ambiguities =96 XSA-108 process post-mortem (http://li=
sts.xenproject.org/archives/html/xen-devel/2014-10/msg00976.html & http://b=
ugs.xenproject.org/xen/bug/44 to see the entire conversation thread in one =
place).

If you use Xen Project Software in any way, we encourage you to voice your =
thoughts to help formulate and update our security policy to ensure it meet=
s the needs of our entire community. To take part in the discussion please =
send mail to xen-devel@lists.xenproject.org. If you are a member of the lis=
t just reply to the relevant thread. If you are not a member of the mailing=
 list and plan to respond to an e-mail that has already been sent you have =
two easy options:

 * You can reply to the message via our issue tracker (http://bugs.xenproje=
ct.org/xen/bug/44) using the Reply to this message link at the top of the m=
essage; or
 * You can retrieve the mbox from the issue issue tracker, load the thread =
into your mail client and just reply.

Even if you chose not to subscribe to xen-devel@ =96 which you don=92t have=
 to participate =96 you may want to occasionally check the discussion threa=
d activity on this thread, to ensure you are not missing any activity.

Going forward, we will collate community input and propose a revised versio=
n of the policy, which will be formally approved in line with Xen Project G=
overnance. We have not set a specific deadline for the discussion, but aim =
to issue a revised policy within 4 weeks.

Best Regards
Lars
_______________________________________________
Xen-announce mailing list
Xen-announce@lists.xen.org
http://lists.xen.org/xen-announce

From xen-announce-bounces@lists.xen.org Thu Oct 23 13:33:21 2014
Return-path: <xen-announce-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 23 Oct 2014 13:33:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-announce-bounces@lists.xen.org>)
	id 1XhIUR-0007Cq-Ax; Thu, 23 Oct 2014 13:31:43 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <russell.pavlicek.xen@gmail.com>)
	id 1Xh4Hj-0001QD-RD; Wed, 22 Oct 2014 22:21:40 +0000
Received: from [85.158.137.68] by server-7.bemta-3.messagelabs.com id
	26/AF-03135-2FD28445; Wed, 22 Oct 2014 22:21:38 +0000
X-Env-Sender: russell.pavlicek.xen@gmail.com
X-Msg-Ref: server-7.tower-31.messagelabs.com!1414016497!10972525!1
X-Originating-IP: [209.85.217.178]
X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP,
  SUSPICIOUS_RECIPS
X-StarScan-Received: 
X-StarScan-Version: 6.12.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27971 invoked from network); 22 Oct 2014 22:21:38 -0000
Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com)
	(209.85.217.178)
	by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	22 Oct 2014 22:21:38 -0000
Received: by mail-lb0-f178.google.com with SMTP id w7so3642350lbi.23
	for <multiple recipients>; Wed, 22 Oct 2014 15:21:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:date:message-id:subject:from:to:content-type;
	bh=xN3fWcBjNleuLudCT3zZP1qbffvey+6zdeVR/ZLeSCE=;
	b=iwxo96DYfvsedCgcNKx52/RcsV8qIpcjaeqIerxZF46l+4Tih3Bc3nnR8rNkZQS2rm
	a49vDu8NLM+lkVAPZnJIAXksxaPXiwIUGOZtM8bLDI4wN+Q8oIBtg85vZnMRNydsF2gZ
	6GdzwMAPKWs+70rR9PO44Mjr0l3VI+qdU1TycxT8/dcUXxnKsqDCJMOucGI68gCUSBbN
	HHPjuqzFmW1xv9O4qceyf7hjsrEqJHhkFErwNu3ZVlty7Vo0WET3hzkuRNjnEV0ru/+u
	AxbOC0rcN9YobgQV1iy9VWENiHHqCQq+Yk9MVZVzBNnbNtFaSRqfLmFDa7obm6vi6goe
	LTrA==
MIME-Version: 1.0
X-Received: by 10.112.173.199 with SMTP id bm7mr939453lbc.54.1414016497119;
	Wed, 22 Oct 2014 15:21:37 -0700 (PDT)
Received: by 10.112.67.35 with HTTP; Wed, 22 Oct 2014 15:21:37 -0700 (PDT)
Date: Wed, 22 Oct 2014 18:21:37 -0400
X-Google-Sender-Auth: e__CbQ7RehGR8VTQnUnZH91oLz0
Message-ID: <CAHehzX3YOT1AyWPhdJUZFT2_dG7DGUyM9TEK7FkQVm4qVGzwsw@mail.gmail.com>
From: Russ Pavlicek <russell.pavlicek@xenproject.org>
To: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	xen-devel@lists.xen.org, xen-api@lists.xen.org, 
	xen-announce@lists.xenproject.org, mirageos-devel@lists.xenproject.org, 
	xs-devel@lists.xenserver.org
X-Mailman-Approved-At: Thu, 23 Oct 2014 13:31:42 +0000
Subject: [Xen-announce] Announcing Xen Project Test Day for 4.5 RC1 on Oct 29
X-BeenThere: xen-announce@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Xen announcements \(low volume\)" <xen-announce.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-announce@lists.xen.org>
List-Help: <mailto:xen-announce-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-announce-bounces@lists.xen.org
Errors-To: xen-announce-bounces@lists.xen.org

Folks,

Next Wednesday, October 29, is our first Test Day for the 4.5 release
cycle. Release Candidate 1 will be available for assessment.  Now is
the time to see if the upcoming release of the Xen Project Hypervisor
will work in your environment.

Information about testing this release can be found here:
http://wiki.xenproject.org/wiki/Xen_4.5_RC1_test_instructions

To learn more about Test Days, check out:
http://wiki.xenproject.org/wiki/Xen_Project_Test_Days

Also, to facilitate this Test Day, the Document Day originally
scheduled for this date will be postponed one week until November 5.
Join us on that day to help document how Xen Project can be integrated
into other solutions.

See you in #xentest on IRC next Wednesday for Test Day.

Russ

_______________________________________________
Xen-announce mailing list
Xen-announce@lists.xen.org
http://lists.xen.org/xen-announce

From xen-announce-bounces@lists.xen.org Thu Oct 23 13:33:21 2014
Return-path: <xen-announce-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 23 Oct 2014 13:33:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-announce-bounces@lists.xen.org>)
	id 1XhIUR-0007Cq-Ax; Thu, 23 Oct 2014 13:31:43 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <russell.pavlicek.xen@gmail.com>)
	id 1Xh4Hj-0001QD-RD; Wed, 22 Oct 2014 22:21:40 +0000
Received: from [85.158.137.68] by server-7.bemta-3.messagelabs.com id
	26/AF-03135-2FD28445; Wed, 22 Oct 2014 22:21:38 +0000
X-Env-Sender: russell.pavlicek.xen@gmail.com
X-Msg-Ref: server-7.tower-31.messagelabs.com!1414016497!10972525!1
X-Originating-IP: [209.85.217.178]
X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP,
  SUSPICIOUS_RECIPS
X-StarScan-Received: 
X-StarScan-Version: 6.12.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27971 invoked from network); 22 Oct 2014 22:21:38 -0000
Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com)
	(209.85.217.178)
	by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	22 Oct 2014 22:21:38 -0000
Received: by mail-lb0-f178.google.com with SMTP id w7so3642350lbi.23
	for <multiple recipients>; Wed, 22 Oct 2014 15:21:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:date:message-id:subject:from:to:content-type;
	bh=xN3fWcBjNleuLudCT3zZP1qbffvey+6zdeVR/ZLeSCE=;
	b=iwxo96DYfvsedCgcNKx52/RcsV8qIpcjaeqIerxZF46l+4Tih3Bc3nnR8rNkZQS2rm
	a49vDu8NLM+lkVAPZnJIAXksxaPXiwIUGOZtM8bLDI4wN+Q8oIBtg85vZnMRNydsF2gZ
	6GdzwMAPKWs+70rR9PO44Mjr0l3VI+qdU1TycxT8/dcUXxnKsqDCJMOucGI68gCUSBbN
	HHPjuqzFmW1xv9O4qceyf7hjsrEqJHhkFErwNu3ZVlty7Vo0WET3hzkuRNjnEV0ru/+u
	AxbOC0rcN9YobgQV1iy9VWENiHHqCQq+Yk9MVZVzBNnbNtFaSRqfLmFDa7obm6vi6goe
	LTrA==
MIME-Version: 1.0
X-Received: by 10.112.173.199 with SMTP id bm7mr939453lbc.54.1414016497119;
	Wed, 22 Oct 2014 15:21:37 -0700 (PDT)
Received: by 10.112.67.35 with HTTP; Wed, 22 Oct 2014 15:21:37 -0700 (PDT)
Date: Wed, 22 Oct 2014 18:21:37 -0400
X-Google-Sender-Auth: e__CbQ7RehGR8VTQnUnZH91oLz0
Message-ID: <CAHehzX3YOT1AyWPhdJUZFT2_dG7DGUyM9TEK7FkQVm4qVGzwsw@mail.gmail.com>
From: Russ Pavlicek <russell.pavlicek@xenproject.org>
To: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	xen-devel@lists.xen.org, xen-api@lists.xen.org, 
	xen-announce@lists.xenproject.org, mirageos-devel@lists.xenproject.org, 
	xs-devel@lists.xenserver.org
X-Mailman-Approved-At: Thu, 23 Oct 2014 13:31:42 +0000
Subject: [Xen-announce] Announcing Xen Project Test Day for 4.5 RC1 on Oct 29
X-BeenThere: xen-announce@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Xen announcements \(low volume\)" <xen-announce.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-announce@lists.xen.org>
List-Help: <mailto:xen-announce-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-announce>, 
	<mailto:xen-announce-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-announce-bounces@lists.xen.org
Errors-To: xen-announce-bounces@lists.xen.org

Folks,

Next Wednesday, October 29, is our first Test Day for the 4.5 release
cycle. Release Candidate 1 will be available for assessment.  Now is
the time to see if the upcoming release of the Xen Project Hypervisor
will work in your environment.

Information about testing this release can be found here:
http://wiki.xenproject.org/wiki/Xen_4.5_RC1_test_instructions

To learn more about Test Days, check out:
http://wiki.xenproject.org/wiki/Xen_Project_Test_Days

Also, to facilitate this Test Day, the Document Day originally
scheduled for this date will be postponed one week until November 5.
Join us on that day to help document how Xen Project can be integrated
into other solutions.

See you in #xentest on IRC next Wednesday for Test Day.

Russ

_______________________________________________
Xen-announce mailing list
Xen-announce@lists.xen.org
http://lists.xen.org/xen-announce

