(arm64) unable to suspend vm

Bug #1731066 reported by Sean Feole
This bug report is a duplicate of:  Bug #1731051: (arm64) VM fails to properly reboot. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

In Openstack Pike upon attempting to suspend an instance on an ARM64 host, the following error occurs

2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] Traceback (most recent call last):
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6815, in _error_out_instance_on_exception
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] yield
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 4238, in suspend_instance
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] self.driver.suspend(context, instance)
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2658, in suspend
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] guest.save_memory_state()
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/guest.py", line 505, in save_memory_state
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] self._domain.managedSave(0)
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 186, in doit
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] result = proxy_call(self._autowrap, f, *args, **kwargs)
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 144, in proxy_call
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] rv = execute(f, *args, **kwargs)
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 125, in execute
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] six.reraise(c, e, tb)
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 83, in tworker
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] rv = meth(*args, **kwargs)
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1427, in managedSave
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] if ret == -1: raise libvirtError ('virDomainManagedSave() failed', dom=self)
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352] libvirtError: Unable to read from monitor: Connection reset by peer
2017-11-08 21:37:35.345 241677 ERROR nova.compute.manager [instance: 8036044b-067b-4be3-916e-29d34b1c3352]

libvirt-bin:
  Installed: 3.6.0-1ubuntu5~cloud0
  Candidate: 3.6.0-1ubuntu5~cloud0

In the libvirt logs, I see:

2017-11-08 22:14:32.528+0000: Domain id=1 is tainted: host-cpu
KVM_SET_DEVICE_ATTR failed: Group 4 attr 0x0000000000000001: No such device or address
2017-11-08 22:17:52.733+0000: shutting down, reason=crashed

I've attached the full output of my commands to the bug.

Tags: arm64
Revision history for this message
Sean Feole (sfeole) wrote :
Revision history for this message
Sean Feole (sfeole) wrote :
tags: added: arm64
description: updated
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Can we make this a dup of 1731051?

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

incomplete waiting for Sean to ack a dup

Changed in libvirt (Ubuntu):
status: New → Incomplete
Revision history for this message
Sean Feole (sfeole) wrote :

after reading Christians update in bug 1731051, marking this one a dup.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.