# \[Live Migration\] Instance shutdown by itself.

**URL:** https://forums.suse.com/t/live-migration-instance-shutdown-by-itself/29788
**Category:** SUSE OpenStack Cloud
**Created:** [May 15, 2017, 5:36pm UTC](https://forums.suse.com/t/live-migration-instance-shutdown-by-itself/29788 "2017-05-15T17:36:06Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![jurrien](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@jurrien](https://forums.suse.com/u/jurrien)
#### Post date: [May 15, 2017, 5:36pm UTC](https://forums.suse.com/t/live-migration-instance-shutdown-by-itself/29788/1 "2017-05-15T17:36:06Z")

</div>

Hi all,

I have Suse Cloud 6 installed with shared storage so I can test Live Migration. When I test Live Migration the instance status is changed to Shutoff and the power state is Shut Down.

I checked the logs of the nova computes nodes and the controller and the online message that is a not an INFO is:

[FONT=Courier New]2017-05-15 16:21:02.463 1588 WARNING nova.compute.manager [req-ac5fd5e2-db24-459f-b045-fad4bfbccc2a - - - - -] [instance: e4932875-c71d-4f5d-b561-a5c61ce1f1c8] Instance shutdown by itself. Calling the stop API. Current vm\_state: active, current task\_state: None, original DB power\_state: 4, current VM power\_state: 4[/FONT]

This is not really what I expected. I would assume that the instance is running on the other node. It is migrated to the other host but it is shutdown.

Any idea what’s going on?

---

<div class="post-metadata">

### Author: ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)
#### Post date: [May 15, 2017, 7:29pm UTC](https://forums.suse.com/t/live-migration-instance-shutdown-by-itself/29788/2 "2017-05-15T19:29:20Z")

</div>

On 15/05/17 15:44, jurrien wrote:  
[color=blue]

> I have Suse Cloud 6 installed with shared storage so I can test Live  
> Migration. When I test Live Migration the instance status is changed to  
> Shutoff and the power state is Shut Down.
> 
> I checked the logs of the nova computes nodes and the controller and the  
> online message that is a not an INFO is:
> 
> 2017-05-15 16:21:02.463 1588 WARNING nova.compute.manager  
> [req-ac5fd5e2-db24-459f-b045-fad4bfbccc2a - - - - -] [instance:  
> e4932875-c71d-4f5d-b561-a5c61ce1f1c8] Instance shutdown by itself.  
> Calling the stop API. Current vm\_state: active, current task\_state:  
> None, original DB power\_state: 4, current VM power\_state: 4
> 
> This is not really what I expected. I would assume that the instance is  
> running on the other node. It is migrated to the other host but it is  
> shutdown.
> 
> Any idea what’s going on?[/color]

Which hypervisor are your Compute Nodes running? KVM or Xen?

Is ‘Live Migration Support: Enable Libvirt Migration’ enabled in the  
Dashboard for Nova?

If your Compute Nodes are Xen have you enabled ‘Live Migration Support:  
Setup Shared Storage’ in the Dashboard for Nova?

## HTH.

Simon  
SUSE Knowledge Partner

* * *

## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks.

---

<div class="post-metadata">

### Author: ![jurrien](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@jurrien](https://forums.suse.com/u/jurrien)
#### Post date: [May 15, 2017, 8:26pm UTC](https://forums.suse.com/t/live-migration-instance-shutdown-by-itself/29788/3 "2017-05-15T20:26:42Z")

</div>

Hi Simon,

It is KVM.

Yes, Live Migration is enabled.

By Dashboard you mean Crowbar (Admin server) right? Ifso: Yes 🙂

It’s KVM so I have mounted a NFS share under /var/lib/nova/instances on both compute hosts.

---

<div class="post-metadata">

### Author: ![jurrien](https://avatars.discourse-cdn.com/v4/letter/j/2bfe46/32.png) [@jurrien](https://forums.suse.com/u/jurrien)
#### Post date: [May 16, 2017, 10:35am UTC](https://forums.suse.com/t/live-migration-instance-shutdown-by-itself/29788/4 "2017-05-16T10:35:27Z")

</div>

Oke this is weird…

Start reading some other posts from 2016: [http://lists.openstack.org/pipermail/openstack-operators/2016-September/011669.html](http://lists.openstack.org/pipermail/openstack-operators/2016-September/011669.html)

I didn’t had anything so lose so I tested mem\_stats\_period\_seconds = 0 in nova.conf.

And now the Live Migration works!
