[
https://issues.apache.org/jira/browse/CLOUDSTACK-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704494#comment-13704494
]
ASF subversion and git services commented on CLOUDSTACK-3443:
-------------------------------------------------------------
Commit 033d05fa2076b5cf72f3942b4e8a9a1ff685842f in branch refs/heads/master
from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=033d05f ]
CLOUDSTACK-3443: Timeoffset on windows guest not persisted between VM stop and
start on XenServer.
The problem was because in cloudstack when a vm is stopped it gets destroyed on
the host. For a
windows vm the timeoffset (which can be set by changing the timezone from
within the vm) is stored
in the platform:timeoffset attribute of vm record. The information is lost when
the vm is destroted.
Made change to read and persist the platform:timeoffset vm attribute when an
instance is stopped.
The value is persisted in the user_vm_details table. When the vm is started
again the attribute is
set for the vm instance that gets created.
> 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
