[
https://issues.apache.org/jira/browse/CLOUDSTACK-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470679#comment-13470679
]
Marcus Sorensen commented on CLOUDSTACK-267:
--------------------------------------------
My hunch hasn't immediately panned out, but I'm still looking at it. Does it
only happen when you use maintenance mode to migrate (does a manual live
migration of a router back and forth work fine for you)? I thought it might be
due to deleting the patch disk during StopCommand (to avoid the building up of
patch disks as has previously occurred), but I don't see that being triggered
at all during a migration, and migrating back and forth seems to work here. It
would also help if you could check to see if the patchdisk is actually missing
and exactly when it goes missing. For example, does it exist just up until the
first maintenance mode is triggered?
> Migration of VM in KVM host is not happening becausec" Unable to migrate due
> to unable to set user and group to '0:0' on
> '/mnt/6e8264c6-4591-399b-b4b0-123f61342208/v-2-VM-patchdisk': No such file or
> directory"
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-267
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-267
> Project: CloudStack
> Issue Type: Bug
> Components: KVM
> Affects Versions: pre-4.0.0
> Environment: MS Rhl 6.3
> Hyp KVM (Rhl6.3)
> build:
> Git Revision: de7a4afaf1aaa3b4fc00fd6f2b4cd58dc3330d43
> Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
> Reporter: prashant kumar mishra
> Priority: Critical
> Attachments: access_log.2012-10-05.txt, api-server.log,
> catalina.2012-10-05.log, catalina.out, cloud.backup.sql, management-server.log
>
>
> In KVM migration of Vms are not happening
> Step to reproduce
> -------------------------
> -------------------------
> 1-Create advance zone->pod->cluster->add 2 KVM host
> 2-Deploy a VM
> 3-put 1st host in maintenance
> 4-Disable maintenance of 1st host
> 5-put 2nd host in maintenance
> Expected Result
> -------------------
> -------------------
> 1-host 1 will go in maintenance and all vms will migrate to host 2(after 3rd
> step)
> 2-host 2 will go in maintenance and all vms will migrate to host 1(after 5th
> step)
> Actual result
> -------------------
> -------------------
> 1-host 1 will go in maintenance and all vms will migrate to host 2(after 3rd
> step)->went successful
> 2-host 2 will go in maintenance and all vms will migrate to host 1(after 5th
> step)->Failed
> 3-host 2 went in ErrorInMaintenace
> My observation
> ----------------------
> ----------------------
> 1-No VMs on host ->it successfully goes in maintenance mode
> 2-User vms migrated successfully but system vms are not getting migrated
> 3-manual migration is happening (1 by 1 you can migrate vms)
--
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
