Return-Path: 
 <issues-return-13494-apmail-cloudstack-issues-archive=cloudstack.apache.org@cloudstack.apache.org>
X-Original-To: apmail-cloudstack-issues-archive@www.apache.org
Delivered-To: apmail-cloudstack-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B88B510AAA
	for <apmail-cloudstack-issues-archive@www.apache.org>;
 Wed, 10 Jul 2013 11:33:49 +0000 (UTC)
Received: (qmail 30711 invoked by uid 500); 10 Jul 2013 11:33:49 -0000
Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org
Received: (qmail 30526 invoked by uid 500); 10 Jul 2013 11:33:48 -0000
Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:issues@cloudstack.apache.org>
List-Id: <issues.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list issues@cloudstack.apache.org
Received: (qmail 30513 invoked by uid 500); 10 Jul 2013 11:33:48 -0000
Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org
Received: (qmail 30506 invoked by uid 99); 10 Jul 2013 11:33:48 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 11:33:48 +0000
Date: Wed, 10 Jul 2013 11:33:48 +0000 (UTC)
From: "Devdeep Singh (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12657052.1373455898168.25013.1373456028611@arcas>
In-Reply-To: <JIRA.12657052.1373455898168@arcas>
References: <JIRA.12657052.1373455898168@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-3443) Timeoffset on Windows guests not
 persisted between VM stop/start from Cloudstack
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devdeep Singh updated CLOUDSTACK-3443:
--------------------------------------

    Fix Version/s: 4.2.0
    
> Timeoffset on Windows guests not persisted between VM stop/start from Cloudstack
> --------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3443
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3443
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.1.0
>            Reporter: Devdeep Singh
>            Assignee: Devdeep Singh
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> For Windows guests, time is initially driven from the control domain clock. However, XenServer also stores for each Windows VM a time offset. This represents the difference between the control domain time and the guest, and is persisted for each VM. if you manually set a VM to be 2 hours ahead of the control domain (e.g. via a time-zone offset within the guest), then it will remember that.
> This information is stored by Xenserver in the parameter "platform" in a key/value pair where the key is "timeoffset". You can check this using "xe vm-param-list uuid=<vmuuid>".
> This information is persisted with Xenserver until the VM exists. The problem is that Cloudstack stop VM operation is really a destroy on Xenserver. When you start the VM again a new VM is launched (of course using the same disk). In this process the above information is lost as Cloudstack doesn't store it and pass it on to the hypervisor when launching the VM.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira