[
https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738435#comment-13738435
]
Abhinav Roy edited comment on CLOUDSTACK-4300 at 8/13/13 4:26 PM:
------------------------------------------------------------------
Wei,
I ran that command but i am not able to login to the systemvm, the state is
shown as running on the host (not on CS) but when i try to login to the console
though virt-manager, i am not
Thanks,
Abhinav
was (Author: abhinavr):
Wei,
I ran that command but i am not able to login to the systemvm, the state is
shown as running but when i try to login to the console though virt-manager, i
am not
Thanks,
Abhinav
> [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4300
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4300
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, SystemVM, Upgrade
> Affects Versions: 4.2.0
> Environment: Host : KVM [CentOS 6.1]
> MS : CentOS 6.1
> upgrade from 2.2.14 to 4.2
> Reporter: Abhinav Roy
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CS-4300.zip
>
>
> Steps :
> ================
> 1. Deploy a CS 2.2.14 advanced zone setup with KVM host.
> 2. do some operations like create vm, snapshots, templates, domain, accounts
> etc
> 3. upgrade to 4.2
> Expected behaviour :
> ===============
> Upgrade should go fine and new system vms should come up
> Observed behaviour :
> ==============
> Upgrade went fine but system vms don't come up, they stay in the starting
> state.
> Attaching management server logs, catalina logs, agent logs and DB dumps
--
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
