[jira] [Commented] (CLOUDSTACK-4649) Windows Vms that were deployed in 6.0.2 Xenservers fail to start (after being stopped) after upgrading host to 6.2.

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764993#comment-13764993 ] 

ASF subversion and git services commented on CLOUDSTACK-4649:
-------------------------------------------------------------

Commit 5950d37e9f57a41a945a11724f250aaeffa9b118 in branch refs/heads/4.2-forward from [~anthonyxu]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5950d37 ]

CLOUDSTACK-4649
       use the same virtual hardware platform in XS 6.2 as that in XS 6.0.2

                
> Windows Vms that were deployed in 6.0.2 Xenservers fail to start (after being stopped) after upgrading host to 6.2.
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4649
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4649
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.1
>         Environment: Build from 4.2-forward
>            Reporter: Sangeetha Hariharan
>            Assignee: Anthony Xu
>            Priority: Critical
>             Fix For: 4.2.1
>
>         Attachments: XenUpgrade.rar
>
>
> Windows Vms that were deployed in 6.0.2 Xenservers fail to start (after being stopped) after upgrade to 6.2
> Steps to reproduce the problem:
> 1. Advanced zone with XS 6.0.2
> 2. install windows 2008 VM
> 3. install xs-tools(XS 6.0.2) in windows 2008 VM
> 4. upgrade XS 6.0.2 to XS 6.2
> As part of upgrade procedure , we are able to see all the Vms successfully live migrate from XS 6.0.2 host to an upgraded XS 6.2 host.
> 6. Now stop and start this windows VM.
> Vm start reportd success.
> Vm does not boot successfully.
> We see the following exception on the screen:
> "System Recovery Option:"

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