Ask Your Question
0

Block format 'qcow' used by device '' does not support feature 'live migration'

asked 2013-07-09 02:46:36 -0500

hcotuk gravatar image

updated 2013-07-09 05:05:46 -0500

Jobin gravatar image

I am using Openstack Grizzly on ubuntu (version 1:2013.1.1-0ubuntu2~cloud0). All compute nodes use /var/lib/nova/instances directory on a shared storage. I confirmed all the steps specified on migration configuration page.

df -kh (on computes)

Filesystem Size Used Avail Use% Mounted on

/dev/sda1 332G 6.4G 309G 3% /

udev 63G 4.0K 63G 1% /dev

tmpfs 26G 548K 26G 1% /run

none 5.0M 0 5.0M 0% /run/lock

none 63G 0 63G 0% /run/shm

none 100M 0 100M 0% /run/user

cgroup 63G 0 63G 0% /sys/fs/cgroup

10.0.20.1:/export/fatih-openstack-shared 229T 537G 229T 1% /var/lib/nova/instances

10.0.20.1:/export/fatih-openstack-volume 229T 526G 229T 1% /var/lib/nova/mnt/7340a4cfb943b72a10821ea4b9732b60

nova.conf (migration related section)

live_migration_bandwidth=0

live_migration_flag= VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE

live_migration_retry_count=30

live_migration_uri=qemu+tcp://%s/system

ps -ef |grep libvirtd

root 1962 49944 0 10:24 pts/0 00:00:00 grep --color=auto libvirtd

root 55682 1 0 Jun24 ? 01:53:42 /usr/sbin/libvirtd -d -l

/etc/libvirt/libvirtd.conf:

listen_tls = 0

listen_tcp = 1

auth_tcp = "none"

When i use the following command, i get a strange error.

nova live-migration 739bf0cd-9aac-4919-b9c4-1de5d092c8a9 dest_host

Error message in nova-compute.log

2013-07-09 08:55:58.054 26690 ERROR nova.virt.libvirt.driver [-] [instance: 739bf0cd-9aac-4919-b9c4-1de5d092c8a9] Live Migration failure: internal error unable to execute QEMU command 'migrate': Block format 'qcow' used by device '' does not support feature 'live migration'

Error in libvirtd.log

2013-07-09 08:55:56.669+0000: 2206: error : qemuMonitorJSONCheckError:345 : internal error unable to execute QEMU command 'migrate': Block format 'qcow' used by device '' does not support feature 'live migration'

2013-07-09 08:55:58.044+0000: 2206: error : virNetClientProgramDispatchError:174 : An error occurred, but the cause is unknown

Following packages are installed in the compute nodes:

ii nova-common 1:2013.1.1-0ubuntu2~cloud0 all OpenStack Compute - common files

ii nova-compute 1:2013.1.1-0ubuntu2~cloud0 all OpenStack Compute - compute node

ii nova-compute-kvm 1:2013.1.1-0ubuntu2~cloud0 all OpenStack Compute - compute node (KVM)

ii nova-conductor 1:2013.1.1-0ubuntu2~cloud0 all OpenStack Compute - conductor service

ii python-nova 1:2013.1.1-0ubuntu2~cloud0 all OpenStack Compute Python libraries

ii python-novaclient 1:2.13.0-0ubuntu1~cloud0 all client library for OpenStack Compute API

ii libvirt-bin 0.9.13-0ubuntu12.2 amd64 programs for the libvirt library

ii libvirt0 0.9.13-0ubuntu12.2 amd64 library for interfacing with different virtualization systems

ii python-libvirt 0.9.13-0ubuntu12.2 amd64 libvirt Python bindings

ii kvm 1:84+dfsg-0ubuntu16+1.2.0+noroms+0ubuntu2.12.10.4 amd64 dummy transitional package from kvm to qemu-kvm

ii qemu-common 1.2.0+noroms-0ubuntu2.12.10.4 all qemu common functionality (bios, documentation, etc)

ii qemu-kvm 1.2.0+noroms-0ubuntu2.12.10.4 amd64 Full virtualization on supported hardware

ii qemu-utils 1.2.0+noroms-0ubuntu2.12.10.4 amd64 qemu utilities

ii kvm-ipxe 1.0.0+git-3.55f6c88-0ubuntu5 all PXE ROM's for KVM

Any suggestions?

edit retag flag offensive close merge delete

Comments

Is your image a qcow? Have you tried a qcow2?

darragh-oreilly gravatar imagedarragh-oreilly ( 2013-10-29 12:55:34 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2014-05-29 12:03:19 -0500

updated 2014-05-29 12:04:32 -0500

What command are you using ?

OK I see now

Try adding --block-migrate
I just tried this with the following command and a qcow2 image, worked fine.

Our stack is mostly G based, with some H features and fixes brought in

$ nova live-migration --block-migrate baa7ed84-fccd-4533-a647-a8a0dbeefb43 mhv1.demo1.mc.metacloud.in
bills-mbp:Demo_Scripts Harper$ nova show baa7ed84-fccd-4533-a647-a8a0dbeefb43
image description

edit flag offensive delete link more
0

answered 2015-04-28 12:29:56 -0500

mriedem gravatar image

QEMU just doesn't support live migration for some disk formats, you can see that from the block device code in qemu:

mriedem@ubuntu:~/git/qemu$ grep -R QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED ./block ./block/vvfat.c: QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED, ./block/snapshot.c: error_set(errp, QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED, ./block/snapshot.c: error_set(errp, QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED, ./block/vpc.c: QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED, ./block/vdi.c: QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED, ./block/qcow.c: QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED, ./block/vmdk.c: QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED, ./block/vhdx.c: QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED,

Should really be using raw or qcow2.

edit flag offensive delete link more

Comments

Note that this also applies to the suspend operation:

http://paste.openstack.org/show/210442/

mriedem gravatar imagemriedem ( 2015-04-28 12:30:49 -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

Stats

Asked: 2013-07-09 02:46:36 -0500

Seen: 1,074 times

Last updated: Apr 28 '15