[openstack-dev] [Nova][Neutron] Nova-network to Neutron migration: issues with libvirt

Oleg Bondarev obondarev at mirantis.com
Mon Apr 21 09:10:32 UTC 2014


On Fri, Apr 18, 2014 at 9:10 PM, Kyle Mestery <mestery at noironetworks.com>wrote:

> On Fri, Apr 18, 2014 at 8:52 AM, Oleg Bondarev <obondarev at mirantis.com>
> wrote:
> > Hi all,
> >
> > While investigating possible options for Nova-network to Neutron
> migration
> > I faced a couple of issues with libvirt.
> > One of the key requirements for the migration is that instances should
> stay
> > running and don't need restarting. In order to meet this requirement we
> need
> > to either attach new nic to the instance or update existing one to plug
> it
> > to the Neutron network.
> >
> Thanks for looking into this Oleg! I just wanted to mention that if
> we're trying to plug a new NIC into the VM, this will likely require
> modifications in the guest. The new NIC will likely have a new PCI ID,
> MAC, etc., and thus the guest would have to switch to this. Therefor,
> I think it may be better to try and move the existing NIC from a nova
> network onto a neutron network.
>

Yeah, I agree that modifying the existing NIC is the preferred way.


> > So what I've discovered is that attaching a new network device is only
> > applied
> > on the instance after reboot although VIR_DOMAIN_AFFECT_LIVE flag is
> passed
> > to
> > the libvirt call attachDeviceFlags():
> >
> https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L1412
> > Is that expected? Are there any other options to apply new nic without
> > reboot?
> >
> > I also tried to update existing nic of an instance by using libvirt
> > updateDeviceFlags() call,
> > but it fails with the following:
> > 'this function is not supported by the connection driver: cannot modify
> > network device configuration'
> > libvirt API spec (http://libvirt.org/hvsupport.html) shows that 0.8.0 as
> > minimal
> > qemu version for the virDomainUpdateDeviceFlags call, kvm --version on my
> > setup shows
> > 'QEMU emulator version 1.0 (qemu-kvm-1.0)'
> > Could someone please point what am I missing here?
> >
> What does "libvirtd -V" show for the libvirt version? On my Fedora 20
> setup, I see the following:
>
> [kmestery at fedora-mac neutron]$ libvirtd -V
> libvirtd (libvirt) 1.1.3.4
> [kmestery at fedora-mac neutron]$
>

On my Ubuntu 12.04 it shows:
 $ libvirtd --version
 libvirtd (libvirt) 0.9.8


> Thanks,
> Kyle
>
> > Any help on the above is much appreciated!
> >
> > Thanks,
> > Oleg
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140421/42122c3a/attachment-0001.html>


More information about the OpenStack-dev mailing list