cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francois Gaudreault <>
Subject Re: [VOTE] Move forward with 4.1 without a Xen-specific fix for CLOUDSTACK-2492?
Date Tue, 21 May 2013 21:13:47 GMT
I am not sure if I am allowed to vote here but...

I guess the SSVM has been built using HVM instead of PV?  If the SSVM is 
PV, it should sync domU -> dom0. It might also require some hotfixes on 
the XenServer side if you are using XS 6.0.2 (hotfix 18) that addresses 
some clock drift issues. Because of the potential impact on other APIs 
(swift?), I would say: -1.

On 2013-05-21 4:20 PM, Chip Childers wrote:
> On Mon, May 20, 2013 at 04:15:14PM -0400, Chip Childers wrote:
>> All,
>> As discussed on another thread [1], we identified a bug
>> (CLOUDSTACK-2492) in the current 3.x system VMs, where the System VMs
>> are not configured to sync their time with either the host HV or an NTP
>> service.  That bug affects the system VMs for all three primary HVs (KVM,
>> Xen and vSphere).  Patches have been committed addressing vSphere and
>> KVM.  It appears that a correction for Xen would require the re-build of
>> a system VM image and a full round of regression testing that image.
>> Given that the discussion thread has not resulted in a consensus on this
>> issue, I unfortunately believe that the only path forward is to call for
>> a formal VOTE.
>> Please respond with one of the following:
>> +1: proceed with 4.1 without the Xen portion of CLOUDSTACK-2492 being resolved
>> +0: don't care one way or the other
>> -1: do *not* proceed with any further 4.1 release candidates until CLOUDSTACK-2492
has been fully resolved
>> -chip
>> [1]
> We need more people to voice their opinions here please.

Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
- - -
420 rue Guy
Montréal QC  H3J 1S6

View raw message