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

Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749

To: "Li, Xin" <xin.li@xxxxxxxxx>, "Li, Haicheng" <haicheng.li@xxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, Gianluca Guida <gianluca.guida@xxxxxxxxxxxxx>
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 16 Dec 2008 12:29:53 +0000
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 16 Dec 2008 04:30:14 -0800
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: AcldK/fZZNTFfVr6k0WK9hRQshPOTwAAZfOQAALnZR0ADcmHgABRQwZvACMnlFAAAwoSIAAJvz8LAACJN+AAAK3GJw==
Thread-topic: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749

On 16/12/2008 12:18, "Li, Xin" <xin.li@xxxxxxxxx> wrote:

>> Applied to Xen-unstable as c/s 18922.
>> 
>> Do we need this for 3.3 as well? And what about 3.2?
>> 
> 
> 3.3 needs it, but 3.2 may not, as this crash is introduced by 17781. But an
> evil guest may crash a Xen 3.2 hypervisor...

Yes, I think it is probably needed really.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Follow-Ups:
- RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
  - From: Li, Xin

Prev by Date: Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
Next by Date: RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
Previous by thread: Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
Next by thread: RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
Index(es):
- Date
- Thread

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