** Changed in: ossn Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1240554
Title: Insecure live migration with libvirt driver Status in OpenStack Compute (Nova): Confirmed Status in OpenStack Security Advisories: Won't Fix Status in OpenStack Security Notes: Fix Released Bug description: By default, libvirt on the receiving end of a live migration starts a qemu process listening on 0.0.0.0 waiting for a tcp connection from the sender. During block migration, qemu-nbd is started similarly. This is bad because compute nodes have interfaces on the guest network. As a result, guests can interfere with live migrations. There is a flag during migration to remedy this called VIR_MIGRATE_TUNNELLED, which tunnels traffic over the libvirt socket (which can be secured with TLS). This seems like a great option. Unfortunately it doesn't work with the new nbd-based block migration code, so there isn't a great option for securing the traffic. Related to this, libvirt just added: - Default migration bind()/listen() IP addr in /etc/libvirt/qemu.conf - Pass in bind()/listen() IP address to migration APIs So with libvirt >= 1.1.4, Nova will have the ability to control the interface used (Problem originally reported by Vish Ishaya) To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1240554/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp