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 <christophe.fonta...@enea.com> 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 <module> import libvirt File "/usr/lib/python2.7/dist-packages/libvirt.py", line 28, in <module> 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 <christophe.fonta...@enea.com<mailto:christophe.fonta...@enea.com>> 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> [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<mailto:vpp-dev@lists.fd.io> Cc: vpp-dev@lists.fd.io<mailto: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@0000:02:01.0<mailto:pci@0000:02:01.0> network Virtio network device pci@0000:03:01.0<mailto:pci@0000:03:01.0> network Virtio network device pci@0000:04:01.0<mailto:pci@0000:04:01.0> network Virtio network device pci@0000:05:01.0<mailto:pci@0000: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$<mailto:csit@dut1:~/vpp/build-root/build-vpp-native/dpdk/dpdk-17.11/usertools$> sudo ./dpdk-devbind.py --status Network devices using DPDK-compatible driver ============================================ 0000:02:01.0 'Virtio network device 1000' drv=uio_pci_generic unused= 0000:03:01.0 'Virtio network device 1000' drv=uio_pci_generic unused= 0000:04:01.0 'Virtio network device 1000' drv=uio_pci_generic unused= 0000:05:01.0 'Virtio network device 1000' drv=uio_pci_generic unused= Network devices using kernel driver =================================== <none> Other Network devices ===================== <none> Crypto devices using DPDK-compatible driver =========================================== <none> Crypto devices using kernel driver ================================== <none> Other Crypto devices ==================== <none> Eventdev devices using DPDK-compatible driver ============================================= <none> Eventdev devices using kernel driver ==================================== <none> Other Eventdev devices ====================== <none> Mempool devices using DPDK-compatible driver ============================================ <none> Mempool devices using kernel driver =================================== <none> Other Mempool devices ===================== <none> 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 /sys/bus/pci/devices/0000:04:01.0/resource0: No such file or directory Feb 16 17:47:17 dut1 vnet[19827]: EAL: Requested device 0000:04:01.0 cannot be used Feb 16 17:47:17 dut1 vnet[19827]: EAL: Invalid NUMA socket, default to 0 Feb 16 17:47:17 dut1 vpp[19827]: EAL: Cannot open /sys/bus/pci/devices/0000:05:01.0/resource0: No such file or directory Feb 16 17:47:17 dut1 vpp[19827]: EAL: Requested device 0000:05:01.0 cannot be used Feb 16 17:47:17 dut1 vnet[19827]: EAL: Cannot open /sys/bus/pci/devices/0000:05:01.0/resource0: No such file or directory Feb 16 17:47:17 dut1 vnet[19827]: EAL: Requested device 0000:05:01.0 cannot be used Feb 16 17:47:17 dut1 vnet[19827]: unix_physmem_region_iommu_register: ioctl (VFIO_IOMMU_MAP_DMA): Invalid argument Feb 16 17:47:17 dut1 vnet[19827]: dpdk_ipsec_process:1007: not enough DPDK crypto resources, default to OpenSSL Feb 16 17:47:17 dut1 vnet[19827]: dpdk_lib_init:221: DPDK drivers found no ports... csit@dut1:~$ csit@dut1:~$
