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

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

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

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

Agree!
-Xin

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

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

Prev by Date: Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
Next by Date: [Xen-devel] [PATCH] xenpm control interface
Previous by thread: Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
Next by thread: [Xen-devel] Test report for Xen-3.3.1-rc1 (#18510)
Index(es):
- Date
- Thread

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