You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Anthony Xu (JIRA)" <ji...@apache.org> on 2013/09/12 02:19:52 UTC
[jira] [Resolved] (CLOUDSTACK-4649) Windows Vms that were deployed
in 6.0.2 Xenservers fail to start (after being stopped) after upgrading
host to 6.2.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Xu resolved CLOUDSTACK-4649.
------------------------------------
Resolution: Fixed
commit 5950d37e9f57a41a945a11724f250aaeffa9b118
Author: Anthony Xu <an...@citrix.com>
Date: Wed Sep 11 17:16:25 2013 -0700
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