From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) by dpdk.org (Postfix) with ESMTP id 4CA732C1A for ; Wed, 12 Jul 2017 15:30:10 +0200 (CEST) Received: by mail-lf0-f52.google.com with SMTP id t72so16645971lff.1 for ; Wed, 12 Jul 2017 06:30:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+pM87h08rplnI4Vg1r/23n6EH7yi21D+WwfRJTAz170=; b=eyr/J1ADWkaGItpWVkHKJ4NcHDYBT1rTHqbj1815AMesbpTKVGXHjmmG62qJn8SJuB elQoib2Bb2a20FnPTvKFFclEXlE9vgonfGsEbtPoBwXnKdC8gC7wYHKiB8VY/Eq1d/1f yGiAdHX8OHZrIb/fSBlo+ga0g1w65wAkzd2vcZD0SsXRCp7yw+D+KDpybC7UDuHWSNmd HF1FPjXBnZlheo2AKMNnsUmMlrZqN4MGSl7NXN/MziFaSG3rY8GhpQNUly2IeInJspAV 1UeufE4bA6DgC0K03GoZ6XYNWd83bmrNoXEHd2vflKh/ESC3v7dPPESNn/3Amtl+5+aG NamA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+pM87h08rplnI4Vg1r/23n6EH7yi21D+WwfRJTAz170=; b=MC48CzdZC8/CPR5fpCUb06M0bG/VcKWSU8glMoS1SnroyVetKKuZPl8NMCe0s37RXU fUSHJLQ8gXh25DvyWgWLDt34ZL8mGKm6R7jR/JNVw8d+dagHKBl7gnjAIUgW+jGt2N0q 5L2oZpgYcvn0GnxVTI+vfJlCfQoaeo7s5isGjQb8+R76LIC3aitMiIrYSnMboByrQ0bJ SmFRk0+cMWuU1AXGdQ9VX1H2qm3bEDzOzfog/89GrKOb2F/FOx/0o1L+v+tjPb9ZqCPc M7TbYiqUb2GIyBpkOObpiU1oqjMu6N5ANH4hCZpFMcaa5U/xm8HS7nlnEBZWTtWzyN7z 1utg== X-Gm-Message-State: AIVw110bFAZHfm7ma31OLhdRfETZ4FOFppG+F9ECWzmUHZpPukwv/aAP M+Xb4jczLE3N78rz5GVDehK+63nNqw== X-Received: by 10.46.70.26 with SMTP id t26mr1799848lja.7.1499866209623; Wed, 12 Jul 2017 06:30:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.195.10 with HTTP; Wed, 12 Jul 2017 06:30:08 -0700 (PDT) In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F93DA45094@HASMSX110.ger.corp.intel.com> References: <9B0331B6EBBD0E4684FBFAEDA55776F93DA45021@HASMSX110.ger.corp.intel.com> <9B0331B6EBBD0E4684FBFAEDA55776F93DA45094@HASMSX110.ger.corp.intel.com> From: ran lifshitz Date: Wed, 12 Jul 2017 16:30:08 +0300 Message-ID: To: "Rosen, Rami" Cc: "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Using PF bound to IGB_UIO, together with sr-iov VFs passed to guests X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2017 13:30:10 -0000 Yeah I assume something is going wrong with libvirt logic, direct qemu command is probably working. >>From the logs it might be related to udev interface which does not detect properly the vf when libvirt tries to discover the interface . Can you repeat your scenario, but with libvirt ? No specific kernel logs from kernel. here is libvirt debug info: 2000-01-18 00:10:51.573+0000: 2055: info : virEventPollRunOnce:641 : EVENT_POLL_RUN: nhandles=3D8 timeout=3D4979 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollRunOnce:651 : Poll got 1 event(s) 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollDispatchTimeouts:433 : Dispatch 2 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollDispatchHandles:479 : Dispatch 8 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollDispatchHandles:493 : i=3D0 w=3D1 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollDispatchHandles:493 : i=3D1 w=3D2 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollDispatchHandles:493 : i=3D2 w=3D3 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollDispatchHandles:493 : i=3D3 w=3D4 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollDispatchHandles:493 : i=3D4 w=3D5 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollDispatchHandles:493 : i=3D5 w=3D6 2000-01-18 00:10:51.574+0000: 2055: debug : virEventPollDispatchHandles:493 : i=3D6 w=3D7 2000-01-18 00:10:51.574+0000: 2055: info : virEventPollDispatchHandles:507 : EVENT_POLL_DISPATCH_HANDLE: watch=3D7 events=3D1 2000-01-18 00:10:51.574+0000: 2055: debug : udevEventHandleCallback:1543 : udev action: 'add' 2000-01-18 00:10:51.574+0000: 2055: debug : udevGetDeviceProperty:124 : udev reports device '35' does not have property 'DRIVER' 2000-01-18 00:10:51.574+0000: 2055: debug : udevGetDeviceProperty:139 : Found property key 'SUBSYSTEM' value 'vfio' for device with sysname '35' 2000-01-18 00:10:51.574+0000: 2055: debug : udevGetDeviceType:1245 : Could not determine device type for device with sysfs name '35' 2000-01-18 00:10:51.574+0000: 2055: debug : udevAddOneDevice:1413 : Discarding device -1 0x5641bbfd2570 /sys/devices/virtual/vfio/35 and later i see: 2000-01-18 00:10:51.575+0000: 2055: info : virEventPollDispatchHandles:507 : EVENT_POLL_DISPATCH_HANDLE: watch=3D7 events=3D1 2000-01-18 00:10:51.575+0000: 2055: debug : udevEventHandleCallback:1543 : udev action: 'remove' 2000-01-18 00:10:51.575+0000: 2055: debug : udevRemoveOneDevice:1314 : Failed to find device to remove that has udev name '/sys/devices/virtual/vfio/35' 2000-01-18 00:10:51.575+0000: 2055: debug : virEventPollDispatchHandles:493 : i=3D7 w=3D31 which causes the vm bootup to fail: 2000-01-18 00:10:51.576+0000: 2057: debug : virNetServerProgramSendError:153 : prog=3D536903814 ver=3D1 proc=3D10 type= =3D1 serial=3D5 msg=3D0x5641bbfd3b90 rerr=3D0x7f49bc0b7db0 2000-01-18 00:10:51.576+0000: 2057: debug : virNetMessageEncodePayload:376 : Encode length as 120 2000-01-18 00:10:51.576+0000: 2057: debug : virNetServerClientSendMessageLocked:1397 : msg=3D0x5641bbfd3b90 proc=3D10 len=3D120 offset=3D0 2000-01-18 00:10:51.576+0000: 2057: info : virNetServerClientSendMessageLocked:1405 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: client=3D0x5641bbfd59b0 len=3D120 prog=3D536903814 vers=3D1 proc=3D10 type= =3D1 status=3D1 serial=3D5 2000-01-18 00:10:51.576+0000: 2057: debug : virNetServerClientCalculateHandleMode:157 : tls=3D(nil) hs=3D-1, rx=3D0x5641bbfddc30 tx=3D0x5641bbfd3b90 2000-01-18 00:10:51.576+0000: 2057: debug : virNetServerClientCalculateHandleMode:192 : mode=3D3 the xml file: WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml configuration should be made using: virsh edit vm64efi or other application using the libvirt API. --> VoidVNF-SRIOV 05ed74d9-e31f-80c2-fb69-6cb052abdb6b 3072 3072 2 hvm /mnt/vm_snapshot/OVMF.fd 2 destroy restart