Shulou(Shulou.com)06/02 Report--

The openstack platform is created on a server using a KVM virtual machine. 7 virtual machines, 1 deployment node, 3 control nodes, 3 compute nodes. After the deployment completes the creation of the instance, I log in to the instance to see if the IP address has been obtained, and find that it has not. All right, I'll see if there's anything wrong with the Internet. I saw that the network card of each server is connected to each network segment, and there is no problem. Then I looked at the ovs and found that there was an error in one dpdk0, as follows:

Bridge br-prv

Fail_mode: secure

Port "dpdk0"

Interface "dpdk0"

Type: dpdk

Options: {dpdk-devargs= "0000 06.0", naughrxq = "2"}

Error: "Error attaching device '0000 to DPDK 06.0'"

Port br-prv

Interface br-prv

Type: internal

Port phy-br-prv

Interface phy-br-prv

Type: patch

Options: {peer=int-br-prv}

Then open the log file / var/log/openvswitch/ovs-vswitchd.log and find that there is an error. Driver cannot attach the device (0000DPDK 06.0) knows that there may be something wrong with the driver of the network card and does not support DPDK.

Later, the drivers of the network card are changed to virtio re-deployment platform to create a virtual machine, and then it will be fine.

Attached: a brief description of several ovirt network cards (e1000, rtl8139,virtio)

Http://www.cnovirt.com/archives/382

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.