Hi,
I am trying to upgrade from 2.5.0 and it is showing this as the latest version
We are using Ubuntu 16-04 version, can you pls let us know how you updated the
version.
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$ qemu-system-aarch64 --version
QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.21), Copyright (c)
2003-2008 Fabrice Bellard
ubuntu@ubuntu:~$ sudo apt-get update qemu-system-aarch64
[sudo] password for ubuntu:
E: The update command takes no arguments
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$ sudo apt-get upgrade qemu-system-aarch64
Reading package lists... Done
Building dependency tree
Reading state information... Done
qemu-system-aarch64 is already the newest version (1:2.5+dfsg-5ubuntu10.21).
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
python-cffi python-pycparser
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
ubuntu@ubuntu:~$
On Monday 19 February 2018, 12:21:37 AM IST, Christophe Fontaine
<christophe.fonta...@enea.com> wrote:
#yiv7745810692 #yiv7745810692 -- _filtered #yiv7745810692
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv7745810692
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv7745810692
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv7745810692
#yiv7745810692 p.yiv7745810692MsoNormal, #yiv7745810692
li.yiv7745810692MsoNormal, #yiv7745810692 div.yiv7745810692MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv7745810692 a:link,
#yiv7745810692 span.yiv7745810692MsoHyperlink
{color:blue;text-decoration:underline;}#yiv7745810692 a:visited, #yiv7745810692
span.yiv7745810692MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv7745810692 p
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv7745810692
p.yiv7745810692msonormal0, #yiv7745810692 li.yiv7745810692msonormal0,
#yiv7745810692 div.yiv7745810692msonormal0
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv7745810692
span.yiv7745810692EmailStyle19 {color:#1F497D;}#yiv7745810692
.yiv7745810692MsoChpDefault {font-size:10.0pt;} _filtered #yiv7745810692
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv7745810692 div.yiv7745810692WordSection1
{}#yiv7745810692
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@0000:02:01.0 network Virtio network device
pci@0000:03:01.0 network Virtio network device
pci@0000:04:01.0 network Virtio network device
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$ 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:~$
