From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sander Eikelenboom Subject: xen-unstable pci passthrough: bug in accounting assigned pci devices when assignment has failed Date: Fri, 21 Feb 2014 15:34:00 +0100 Message-ID: <974010162.20140221153400@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WGrAx-00022c-KL for xen-devel@lists.xenproject.org; Fri, 21 Feb 2014 14:34:03 +0000 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Hi Ian, It was decided that the bug that domain creation does not fail on non assignable pci devices was deferred to 4.5. (and it wouldn't prevent this bug anyhow when doing pci hotplug with xl pci-attach) But there seems to be a bug in the error path: root@creanuc:~# xl pci-assignable-list 0000:02:00.0 Now when i boot a VM with pci=['00:19.0'] in it's config file ... which is not assignable: root@creanuc:~# xl create /etc/xen/domU/router.hvm Parsing config from /etc/xen/domU/router.hvm libxl: error: libxl_pci.c:1060:libxl__device_pci_add: PCI device 0:0:19.0 is not assignable That looks ok ... and the pci device is not visible / accessible in the guest ... but it seems the entry is still in xenstore nevertheless: root@creanuc:~# xl pci-list router Vdev Device 00.0 0000:00:19.0 -- Sander