Ask Your Question

Revision history [back]

abnormally long migration time in juno

I have installed Juno on a 4 node topology (1 controller node, 1 neutron node, 2 compute nodes). All nodes have similar hardware configuration. They are Dell PowerEdge R720 machines with intel Xeon cpu (16 cores each), 4TB HDD, and 16 GB RAM. I also have Three separate physical networks in my Openstack. One for the management issues, the other one dedicated for VMs traffic and the last one is an external network which have access to the internet. You can see a schematic feature of my Openstack topology here.

I have configured my compute nodes for block live migration. I can successfully live migrate a tiny instance (Cirros-0.3.3-x86-64 image, 1 vcpu, 512 MB RAM, and 1GB disk) which is not loaded (nothing is installed or running on top of it). However, the migration takes around 90-100 seconds or even more while it should be something around 5-10 seconds at most. This is very large migration time, especially for a tiny instance like this. I checked many online resources and couldn't find any reason for that.

I just wanna ask what causes this abnormal large time and what I can do to reduce it to a reasonable time. I have included my nova.conf file along with nova compute log files for both compute nodes (they just include logs from the time migration starts to the time it finishes).

Thanks

nova.conf: http://paste.openstack.org/show/528652/

nova-compute log for compute1 (migration destination): http://paste.openstack.org/show/528653/

nova-compute log for compute2 (migration source): http://paste.openstack.org/show/528655/

abnormally long migration time in juno

I have installed Juno on a 4 node topology (1 controller node, 1 neutron node, 2 compute nodes). All nodes have similar hardware configuration. They are Dell PowerEdge R720 machines with intel Xeon cpu (16 cores each), 4TB HDD, and 16 GB RAM. I also have Three separate physical networks in my Openstack. One for the management issues, the other one dedicated for VMs traffic and the last one is an external network which have access to the internet. You can see a schematic feature of my Openstack topology here.

I have configured my compute nodes for block live migration. I can successfully live migrate a tiny instance (Cirros-0.3.3-x86-64 image, 1 vcpu, 512 MB RAM, and 1GB disk) which is not loaded (nothing is installed or running on top of it). However, the migration takes around 90-100 seconds or even more while it should be something around 5-10 seconds at most. This is very large migration time, especially for a tiny instance like this. I checked many online resources and couldn't find any reason for that. By the way, when the migration process starts, I checked the migration process with the virsh. For the first 80 seconds (out of the whole migration time which is 90 seconds) nothing happen. in the last 10 seconds, suddenly migration starts progressing and then finishes very fast. It's noteworthy that I'm using QEMU and Libvirt.

I just wanna ask what causes this abnormal large time and what I can do to reduce it to a reasonable time. Is this a hypervisor problem or it's an orchestration problem from Openstack side? I have included my nova.conf file along with nova compute log files for both compute nodes (they just include logs from the time migration starts to the time it finishes).

Thanks

nova.conf: http://paste.openstack.org/show/528652/

nova-compute log for compute1 (migration destination): http://paste.openstack.org/show/528653/

nova-compute log for compute2 (migration source): http://paste.openstack.org/show/528655/

abnormally Abnormally long VM live migration time in juno

I have installed Juno on a 4 node topology (1 controller node, 1 neutron node, 2 compute nodes). All nodes have similar hardware configuration. They are Dell PowerEdge R720 machines with intel Xeon cpu (16 cores each), 4TB HDD, and 16 GB RAM. I also have Three separate physical networks in my Openstack. One for the management issues, the other one dedicated for VMs traffic and the last one is an external network which have access to the internet. You can see a schematic feature of my Openstack topology here.

I have configured my compute nodes for block live migration. I can successfully live migrate a tiny instance (Cirros-0.3.3-x86-64 image, 1 vcpu, 512 MB RAM, and 1GB disk) which is not loaded (nothing is installed or running on top of it). However, the migration takes around 90-100 seconds or even more while it should be something around 5-10 seconds at most. This is very large migration time, especially for a tiny instance like this. I checked many online resources and couldn't find any reason for that. By the way, when the migration process starts, I checked the migration process with the virsh. For the first 80 seconds (out of the whole migration time which is 90 seconds) nothing happen. in the last 10 seconds, suddenly migration starts progressing and then finishes very fast. It's noteworthy that I'm using QEMU and Libvirt.

I just wanna ask what causes this abnormal large time and what I can do to reduce it to a reasonable time. Is this a hypervisor problem or it's an orchestration problem from Openstack side? I have included my nova.conf file along with nova compute log files for both compute nodes (they just include logs from the time migration starts to the time it finishes).

Thanks

nova.conf: http://paste.openstack.org/show/528652/

nova-compute log for compute1 (migration destination): http://paste.openstack.org/show/528653/

nova-compute log for compute2 (migration source): http://paste.openstack.org/show/528655/

Abnormally abnormally long VM live migration time in juno

I have installed Juno on a 4 node topology (1 controller node, 1 neutron node, 2 compute nodes). All nodes have similar hardware configuration. They are Dell PowerEdge R720 machines with intel Xeon cpu (16 cores each), 4TB HDD, and 16 GB RAM. I also have Three separate physical networks in my Openstack. One for the management issues, the other one dedicated for VMs traffic and the last one is an external network which have access to the internet. You can see a schematic feature of my Openstack topology here.

I have configured my compute nodes for block live migration. I can successfully live migrate a tiny instance (Cirros-0.3.3-x86-64 image, 1 vcpu, 512 MB RAM, and 1GB disk) which is not loaded (nothing is installed or running on top of it). However, the migration takes around 90-100 seconds or even more while it should be something around 5-10 seconds at most. This is very large migration time, especially for a tiny instance like this. I checked many online resources and couldn't find any reason for that. By the way, when the migration process starts, I checked the migration process with the virsh. For the first 80 seconds (out of the whole migration time which is 90 seconds) nothing happen. in the last 10 seconds, suddenly migration starts progressing and then finishes very fast. It's noteworthy that I'm using QEMU and Libvirt.

I just wanna ask what causes this abnormal large time and what I can do to reduce it to a reasonable time. Is this a hypervisor problem or it's an orchestration problem from Openstack side? I have included my nova.conf file along with nova compute log files for both compute nodes (they just include logs from the time migration starts to the time it finishes).

Thanks

nova.conf: http://paste.openstack.org/show/528652/

nova-compute log for compute1 (migration destination): http://paste.openstack.org/show/528653/

nova-compute log for compute2 (migration source): http://paste.openstack.org/show/528655/

abnormally Abnormally long VM live migration time in juno

I have installed Juno on a 4 node topology (1 controller node, 1 neutron node, 2 compute nodes). All nodes have similar hardware configuration. They are Dell PowerEdge R720 machines with intel Xeon cpu (16 cores each), 4TB HDD, and 16 GB RAM. I also have Three separate physical networks in my Openstack. One for the management issues, the other one dedicated for VMs traffic and the last one is an external network which have access to the internet. You can see a schematic feature of my Openstack topology here.

I have configured my compute nodes for block live migration. I can successfully live migrate a tiny instance (Cirros-0.3.3-x86-64 image, 1 vcpu, 512 MB RAM, and 1GB disk) which is not loaded (nothing is installed or running on top of it). However, the migration takes around 90-100 seconds or even more while it should be something around 5-10 seconds at most. This is very large migration time, especially for a tiny instance like this. I checked many online resources and couldn't find any reason for that. By the way, when the migration process starts, I checked the migration process with the virsh. For the first 80 seconds (out of the whole migration time which is 90 seconds) nothing happen. in happens. In the last 10 seconds, suddenly migration starts progressing and then finishes very fast. It's noteworthy that I'm using QEMU and Libvirt.

I just wanna ask what causes this abnormal large time and what I can do to reduce it to a reasonable time. Is this a hypervisor problem or it's an orchestration problem from Openstack side? I have included my nova.conf file along with nova compute log files for both compute nodes (they just include logs from the time migration starts to the time it finishes).

Thanks

nova.conf: http://paste.openstack.org/show/528652/

nova-compute log for compute1 (migration destination): http://paste.openstack.org/show/528653/

nova-compute log for compute2 (migration source): http://paste.openstack.org/show/528655/

Abnormally abnormally long VM live migration time in juno

I have installed Juno on a 4 node topology (1 controller node, 1 neutron node, 2 compute nodes). All nodes have similar hardware configuration. They are Dell PowerEdge R720 machines with intel Xeon cpu (16 cores each), 4TB HDD, and 16 GB RAM. I also have Three separate physical networks in my Openstack. One for the management issues, the other one dedicated for VMs traffic and the last one is an external network which have access to the internet. You can see a schematic feature of my Openstack topology here.

I have configured my compute nodes for block live migration. I can successfully live migrate a tiny instance (Cirros-0.3.3-x86-64 image, 1 vcpu, 512 MB RAM, and 1GB disk) which is not loaded (nothing is installed or running on top of it). However, the migration takes around 90-100 seconds or even more while it should be something around 5-10 seconds at most. This is very large migration time, especially for a tiny instance like this. I checked many online resources and couldn't find any reason for that. By the way, when the migration process starts, I checked the migration process with the virsh. For the first 80 seconds (out of the whole migration time which is 90 seconds) nothing happens. In the last 10 seconds, suddenly migration starts progressing and then finishes very fast. It's noteworthy that I'm using QEMU and Libvirt.

I just wanna ask what causes this abnormal large time and what I can do to reduce it to a reasonable time. Is this a hypervisor problem or it's an orchestration problem from Openstack side? I have included my nova.conf file along with nova compute log files for both compute nodes (they just include logs from the time migration starts to the time it finishes).

Thanks

nova.conf: http://paste.openstack.org/show/528652/

nova-compute log for compute1 (migration destination): http://paste.openstack.org/show/528653/

nova-compute log for compute2 (migration source): http://paste.openstack.org/show/528655/