Ask Your Question

Live block migration from Liberty compute nodes to Mitaka compute nodes gives "Permission denied" error.

asked 2017-06-17 11:22:29 -0500

Hi. I'm trying to live block migrate from compute nodes running Liberty, backing instance images with NFS, to Mitaka nodes using local disk to back the instances.

I am however running into the following error: 2017-06-17 18:13:17.894 143531 ERROR nova.virt.libvirt.driver [req-d0314c6e-e082-4741-892a-324363d1a799 aa476eb154b9400a91f2a72550359079 bc4b33b79c2741888cfc2cc0da7dede3 - - -] [instance: 24c8dbd4-5120-486e-abe4-edfa34f434cd] Live Migration failure: internal error: process exited while connecting to monitor: 2017-06-17T16:13:17.572056Z qemu-system-x86_64: -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-instance-0000023f/monitor.sock,server,nowait: Failed to unlink socket /var/lib/libvirt/qemu/domain-instance-0000023f/monitor.sock: Permission denied

The file /var/lib/libvirt/qemu/domain-instance-0000023f/monitor.sock does not exist, the running process is showing /var/lib/libvirt/qemu/instance-0000023f.monitor as the monitor path.

The process is running as user nova and /var/lib/libvirt/qemu is owned by nova.

I'm really stumped as to what the possible issue is, so I'd love some help and / or suggestions as to further troubleshooting steps.

Thanks, Martin

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2017-06-20 10:28:38 -0500

Thanks for the help! I tried to migrate to another compute-node which was commissioned using the same Salt state and it worked just my compute-node was borked for some reason.

Re-provisioned it and now it works as it should...

edit flag offensive delete link more

answered 2017-06-19 19:04:48 -0500

luowei gravatar image

updated 2017-06-19 19:11:10 -0500

Did you configure for live migration? It requires, among other things, password-less ssh between compute nodes. See:

One way I've found to non-live migrate on Mitaka without setting up migrations is:

a) disable the compute nodes I dont wish to migrate to (hypervisor->compute host->disable service)
b) shelve the instance (wait for the shelving copy to complete)
c) unshelve the instance (it will be rebooted on one of the enabled compute nodes)
edit flag offensive delete link more


On second thought, the document says "block migration" requires no additional configuration.

luowei gravatar imageluowei ( 2017-06-19 20:19:04 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-06-17 11:21:29 -0500

Seen: 68 times

Last updated: Jun 20 '17