# Missing qbr, qvb and qvo devices on compute node with ovs agent

Hi. I'm using neutron (with a dedicated network node) with openvswitch agent and gre. My initial configuration was 1 node for controller, 1 for network and 1 for compute. Next I added a new compute node. When i launch a new instance on the first compute node, i can see on this node 4 new interfaces: tap, qbr, qvb and qvo. Moreover, i have a new qvo port (with a vlan tag) in the integration bridge (with ovs-vsctl show). On the second compute node i have a different behavior: when i launch an instance, i only see a new tap interface and a new port (with a tap interface) in the integration bridge. Vlan tags are the same (beacuse the instances are in the same network). But... is this correct? Should i have 4 new interfaces on the second compute node? If this is correct.... Why it is? Thanks

edit retag close merge delete

Sort by » oldest newest most voted

Yes, if you want security groups to work. Your nova.conf on the 2nd compute node needs to have:

libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver

more

1

Ok. Thank You, i see right interfaces now. But in this way i have a message on the compute node: "Deprecated: The LibvirtHybridOVSBridgeDriver VIF driver is now deprecated and will be removed in the next release. Please use the LibvirtGenericVIFDriver VIF driver, together with a network plugin that reports the 'vif_type' attribute" I don't want to use deprecated flags. Moreover, in this way live-migration doesn't works, but probably this is not related to the precedent flag. I have this error message on the compute node: "qemu-kvm: -drive file=/nova/instances/217a5f53-f2c2-4ec0-bd8b-bfa4837957e4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image /nova/instances/217a5f53-f2c2-4ec0-bd8b-bfa4837957e4/disk: No such file or directory" But file exists! I'm using a shared storage area where compute nodes save the instances and disks (with nova:nova owner). Is this a permission mistake?? Thank You.

( 2013-11-29 05:20:57 -0600 )edit

In Havana, I don't think the OVS (or ml2) plugin reports a vif_type that will cause the LibvirtHybridOVSBridgeDriver to be used. I think the inclusion of the deprecation message was premature. Sorry, I have no idea about your live migration problem.

( 2013-11-29 07:13:21 -0600 )edit