Please see my response below.
> On Dec 7, 2015, at 6:43 AM, Ali Volkan Atli <volkan.a...@argela.com.tr> wrote: > > Hi > > First, thanks for the reply. vHost-user(s) can bind to the related socket > right now, but I have another problem. I followed the link > (https://software.intel.com/en-us/articles/using-open-vswitch-with-dpdk-for-inter-vm-nfv-applications) > and while booting a VM with Fedora-Cloud-Base-23-20151030.x86_64.qcow2 image > by qemu, it gives me the following error, even so I can login the VM but and > I cannot connect the VM via ssh or cannot connect to the Internet from the > VM. Therefore I cannot transfer anything into the VM. By the way, I don't > know it is related to the OvS DPDK or not? > > <snip> > ... > Starting Initial cloud-init job (metadata service crawler)... > [ 66.669708] cloud-init[681]: Cloud-init v. 0.7.7 running 'init' at Mon, 07 > Dec 2015 13:33:13 +0000. Up 65.97 seconds. > [ 66.670147] cloud-init[681]: ci-info: +++++++++++++++++++++++++++Net > device info++++++++++++++++++++++++++++ > [ 66.671295] cloud-init[681]: ci-info: > +--------+-------+-----------+-----------+-------+-------------------+ > [ 66.671479] cloud-init[681]: ci-info: | Device | Up | Address | > Mask | Scope | Hw-Address | > [ 66.671656] cloud-init[681]: ci-info: > +--------+-------+-----------+-----------+-------+-------------------+ > [ 66.671835] cloud-init[681]: ci-info: | lo: | True | 127.0.0.1 | > 255.0.0.0 | . | . | > [ 66.672133] cloud-init[681]: ci-info: | lo: | True | . | . > | d | . | > [ 66.672409] cloud-init[681]: ci-info: | eth0: | True | . | . > | . | 00:00:00:00:00:01 | > [ 66.672703] cloud-init[681]: ci-info: | eth0: | True | . | . > | d | 00:00:00:00:00:01 | > [ 66.672968] cloud-init[681]: ci-info: | eth1: | False | . | . > | . | 52:54:00:12:34:56 | > [ 66.673271] cloud-init[681]: ci-info: > +--------+-------+-----------+-----------+-------+-------------------+ > [ 66.673535] cloud-init[681]: 2015-12-07 13:33:14,286 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: > request error [('Connection aborted.', OSError(101, 'Network is > unreachable'))] > [ 67.675085] cloud-init[681]: 2015-12-07 13:33:15,290 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: > request error [('Connection aborted.', OSError(101, 'Network is > unreachable'))] > ... > ... > [ 185.978295] cloud-init[681]: 2015-12-07 13:35:13,593 - > url_helper.py[WARNING]: Calling > 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: > request error [('Connection aborted.', OSError(101, 'Network is > unreachable'))] > [ 192.985262] cloud-init[681]: 2015-12-07 13:35:20,601 - > DataSourceEc2.py[CRITICAL]: Giving up on md from > ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 126 seconds > [ 192.996385] cloud-init[681]: 2015-12-07 13:35:20,608 - > DataSourceCloudSigma.py[WARNING]: failed to get hypervisor product name via > dmi data > ... > ... > Fedora 23 (Cloud Edition) > Kernel 4.2.3-300.fc23.x86_64 on an x86_64 (ttyS0) > > localhost login: I certainly could be mistaken, but I think this is not related to OVS or DPDK. Most "cloud" images expect the presence of a metadata service in order to perform instance customization. In this case, you're booting a cloud image via QEMU, so there is no metadata service, and therefore no customization (password setting, SSH key injection, etc.) can occur. The warnings you're seeing are all related to cloud-init, as it is unable to connect to a metadata source. Hope this helps! -- Scott _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
