Re: [vpp-dev] Unable to add interface to VPP on ARM64.

2018-02-23 Thread via Lists.Fd.Io 
 Hi,
@Jdensico sorry this is the mail thread for latest problem.
I am using Latest Qemu 2.11 and since i am using Virsh i updated Libvirt to 
latest 3.6.0 (Ubuntu 16.04)ubuntu@ubuntu:~$  virsh -c qemu:///system version 
--daemon
setlocale: No such file or directory
Compiled against library: libvirt 3.6.0
Using library: libvirt 3.6.0
Using API: QEMU 3.6.0
Running hypervisor: QEMU 2.10.1
Running against daemon: 3.6.0

Both versions were ideally not having an official release for ubuntu 16.04.

I resolved the previous issue as per mail chain and also there solved the 
permission issue for finding path for libvirt.Grant permission for lib-virt : 
setfacl -m u:libvirt-qemu:r-x ubuntu

But when i try and do virsh-install it'll get stuck after boot.Logs :
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...


Virsh command : sudo virt-install --name dut2 --ram 4096 --disk 
path=dut2.img,size=30 --vcpus 2 --os-type linux --os-variant generic --cdrom 
'./ubuntu-16.04.3-server-arm64.iso' --network default
On Monday 19 February 2018, 7:33:50 PM IST, Christophe Fontaine 
 wrote:
 
 #yiv1514780694 #yiv1514780694 -- P 
{margin-top:0;margin-bottom:0;}#yiv1514780694 
Hi,
 
  
 
I never tried to do avirt-install on arm platform: I always use cloud images. 
(Either Centos or Fedora based).
 
One more thing: maybe you also need to update other dependencies, along qemu.
 
An apt-get update and/or apt-get upgrade may fix the issues you have.
 
  
 
Christophe
 
  
 
From: adarsh m [mailto:addi.ada...@yahoo.in] 
Sent: Monday, February 19, 2018 2:26 PM
To: vpp-dev@lists.fd.io; Christophe Fontaine 
Subject: Re: [vpp-dev] Unable to add interface to VPP on ARM64.
 
  
 
Hi,
 
  
 
Thanks for the steps we were now able to install to 2.10 version but when we 
try to start VM we are getting below error,
 
  
 
pls check and let us know if you faced the same or need any other change .
 
  
 
ubuntu@vasily:~$ sudo virt-install --name dut3 --ram 4096 --disk 
path=dut3.img,size=30 --vcpus 2 --os-type linux --os-variant generic --cdrom 
'./ubuntu-16.04.3-server-arm64.iso' --network default
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-install", line 27, in 
    import libvirt
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 28, in 
    raise lib_e
ImportError: /usr/lib/aarch64-linux-gnu/libxenlight-4.9.so: symbol 
fdt_first_subnode, version LIBFDT_1.2 not defined in file libfdt.so.1 with link 
time reference
ubuntu@vasily:~$ 


 
  
 
  
 
On Monday 19 February 2018, 6:12:48 PM IST, Christophe Fontaine 
 wrote: 
 
  
 
  
 
Hi,
 
 
 
Which version of qemu do you use ?
 
I had this kind of issue when using an old version of qemu: upgrading qemu to 
2.10 resolved my issue.
 
 
 
In qemu 2.5 (the default version with Ubuntu 16.04 in my case), the IO region 
is not mapped, which ends to this kind of error (the ressource0 is the IO 
region in the PCI bar).
 
 
 
Christophe
 
 
 
From:vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io]On Behalf Of via 
Lists.Fd.Io
Sent: Friday, February 16, 2018 3:46 PM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] Unable to add interface to VPP on ARM64.
 
 
 
Hi,
 
 
 
Pls check not able to add interface to VPP on ARM64 VM
 
 
 
 
 
csit@dut1:~$ lshw -class network -businfo
WARNING: you should run this program as super-user.
Bus info  Device  Class  Description

pci@:02:01.0  network    Virtio network device
pci@:03:01.0  network    Virtio network device
pci@:04:01.0  network    Virtio network device
pci@:05:01.0  network    Virtio network device
  eth0    network    Ethernet interface
WARNING: output may be incomplete or inaccurate, you should run this program as 
super-user.
csit@dut1:~$ 

 cd vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools/
csit@dut1:~/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools$ sudo 
./dpdk-devbind.py --status

Network devices using DPDK-compatible driver

:02:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=
:03:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=
:04:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=
:05:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=

Network devices using kernel driver
===


Other Network devices
=


Crypto devices using DPDK-compatible driver
===


Crypto devices using kernel driver
==


Other Crypto devices



Eventdev devices using DPDK-compatible driver

Re: [vpp-dev] Unable to add interface to VPP on ARM64.

2018-02-19 Thread Christophe Fontaine 
Hi,



I never tried to do a virt-install on arm platform: I always use cloud images. 
(Either Centos or Fedora based).

One more thing: maybe you also need to update other dependencies, along qemu.

An apt-get update and/or apt-get upgrade may fix the issues you have.



Christophe



From: adarsh m [mailto:addi.ada...@yahoo.in]
Sent: Monday, February 19, 2018 2:26 PM
To: vpp-dev@lists.fd.io; Christophe Fontaine 
Subject: Re: [vpp-dev] Unable to add interface to VPP on ARM64.



Hi,



Thanks for the steps we were now able to install to 2.10 version but when we 
try to start VM we are getting below error,



pls check and let us know if you faced the same or need any other change .



ubuntu@vasily:~$ sudo virt-install --name dut3 --ram 4096 --disk 
path=dut3.img,size=30 --vcpus 2 --os-type linux --os-variant generic --cdrom 
'./ubuntu-16.04.3-server-arm64.iso' --network default
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-install", line 27, in 
import libvirt
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 28, in 
raise lib_e
ImportError: /usr/lib/aarch64-linux-gnu/libxenlight-4.9.so: symbol 
fdt_first_subnode, version LIBFDT_1.2 not defined in file libfdt.so.1 with link 
time reference
ubuntu@vasily:~$






On Monday 19 February 2018, 6:12:48 PM IST, Christophe Fontaine 
> wrote:





Hi,



Which version of qemu do you use ?

I had this kind of issue when using an old version of qemu: upgrading qemu to 
2.10 resolved my issue.



In qemu 2.5 (the default version with Ubuntu 16.04 in my case), the IO region 
is not mapped, which ends to this kind of error (the ressource0 is the IO 
region in the PCI bar).



Christophe



From: vpp-dev@lists.fd.io 
[mailto:vpp-dev@lists.fd.io] On Behalf Of via Lists.Fd.Io
Sent: Friday, February 16, 2018 3:46 PM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] Unable to add interface to VPP on ARM64.



Hi,



Pls check not able to add interface to VPP on ARM64 VM





csit@dut1:~$ lshw -class network -businfo
WARNING: you should run this program as super-user.
Bus info  Device  Class  Description

pci@:02:01.0  networkVirtio 
network device
pci@:03:01.0  networkVirtio 
network device
pci@:04:01.0  networkVirtio 
network device
pci@:05:01.0  networkVirtio 
network device
  eth0networkEthernet interface
WARNING: output may be incomplete or inaccurate, you should run this program as 
super-user.
csit@dut1:~$

 cd vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools/
csit@dut1:~/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools$
 sudo ./dpdk-devbind.py --status

Network devices using DPDK-compatible driver

:02:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=
:03:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=
:04:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=
:05:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=

Network devices using kernel driver
===


Other Network devices
=


Crypto devices using DPDK-compatible driver
===


Crypto devices using kernel driver
==


Other Crypto devices



Eventdev devices using DPDK-compatible driver
=


Eventdev devices using kernel driver



Other Eventdev devices
==


Mempool devices using DPDK-compatible driver



Mempool devices using kernel driver
===


Other Mempool devices
=

csit@dut1:~/vpp/build-root/build-vpp-nativ

● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Fri 2018-02-16 17:47:17 CST; 4h 45min ago
  Process: 19822 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 19818 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 19827 (vpp_main)
Tasks: 4
   Memory: 73.1M
  CPU: 59.726s
   CGroup: /system.slice/vpp.service
   └─19827 /usr/bin/vpp -c /etc/vpp/startup.conf

Feb 16 17:47:17 dut1 vnet[19827]: EAL: Cannot open

Re: [vpp-dev] Unable to add interface to VPP on ARM64.

2018-02-19 Thread via Lists.Fd.Io 
Hi,
Thanks for the steps we were now able to install to 2.10 version but when we 
try to start VM we are getting below error,
pls check and let us know if you faced the same or need any other change .

ubuntu@vasily:~$ sudo virt-install --name dut3 --ram 4096 --disk 
path=dut3.img,size=30 --vcpus 2 --os-type linux --os-variant generic --cdrom 
'./ubuntu-16.04.3-server-arm64.iso' --network default
Traceback (most recent call last):
  File "/usr/share/virt-manager/virt-install", line 27, in 
    import libvirt
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 28, in 
    raise lib_e
ImportError: /usr/lib/aarch64-linux-gnu/libxenlight-4.9.so: symbol 
fdt_first_subnode, version LIBFDT_1.2 not defined in file libfdt.so.1 with link 
time reference
ubuntu@vasily:~$ 


 

On Monday 19 February 2018, 6:12:48 PM IST, Christophe Fontaine 
 wrote:
 
 #yiv7431552402 #yiv7431552402 -- _filtered #yiv7431552402 
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv7431552402 
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv7431552402 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv7431552402 
#yiv7431552402 p.yiv7431552402MsoNormal, #yiv7431552402 
li.yiv7431552402MsoNormal, #yiv7431552402 div.yiv7431552402MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv7431552402 a:link, 
#yiv7431552402 span.yiv7431552402MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv7431552402 a:visited, #yiv7431552402 
span.yiv7431552402MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv7431552402 p 
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv7431552402 
p.yiv7431552402msonormal0, #yiv7431552402 li.yiv7431552402msonormal0, 
#yiv7431552402 div.yiv7431552402msonormal0 
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv7431552402 
span.yiv7431552402EmailStyle19 {color:#1F497D;}#yiv7431552402 
.yiv7431552402MsoChpDefault {font-size:10.0pt;} _filtered #yiv7431552402 
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv7431552402 div.yiv7431552402WordSection1 
{}#yiv7431552402 
Hi,
 
  
 
Which version of qemu do you use ?
 
I had this kind of issue when using an old version of qemu: upgrading qemu to 
2.10 resolved my issue.
 
  
 
In qemu 2.5 (the default version with Ubuntu 16.04 in my case), the IO region 
is not mapped, which ends to this kind of error (the ressource0 is the IO 
region in the PCI bar).
 
  
 
Christophe
 
  
 
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io]On Behalf Of via 
Lists.Fd.Io
Sent: Friday, February 16, 2018 3:46 PM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] Unable to add interface to VPP on ARM64.
 
  
 
Hi,
 
  
 
Pls check not able to add interface to VPP on ARM64 VM
 
  
 
  
 
csit@dut1:~$ lshw -class network -businfo
WARNING: you should run this program as super-user.
Bus info  Device  Class  Description

pci@:02:01.0  network    Virtio network device
pci@:03:01.0  network    Virtio network device
pci@:04:01.0  network    Virtio network device
pci@:05:01.0  network    Virtio network device
  eth0    network    Ethernet interface
WARNING: output may be incomplete or inaccurate, you should run this program as 
super-user.
csit@dut1:~$ 

 cd vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools/
csit@dut1:~/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools$ sudo 
./dpdk-devbind.py --status

Network devices using DPDK-compatible driver

:02:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=
:03:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=
:04:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=
:05:01.0 'Virtio network device 1000' drv=uio_pci_generic unused=

Network devices using kernel driver
===


Other Network devices
=


Crypto devices using DPDK-compatible driver
===


Crypto devices using kernel driver
==


Other Crypto devices



Eventdev devices using DPDK-compatible driver
=


Eventdev devices using kernel driver



Other Eventdev devices
==


Mempool devices using DPDK-compatible driver



Mempool devices using kernel driver
===


Other Mempool devices
=

csit@dut1:~/vpp/build-root/build-vpp-nativ
 
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Fri 2018-02-16 17:47:17 CST; 4h 45min ago
  Process: 19822 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited,