WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Fail to passthru PCI device to HVM

To: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Subject: Re: [Xen-devel] Fail to passthru PCI device to HVM
From: Jun Koi <junkoi2004@xxxxxxxxx>
Date: Fri, 4 Sep 2009 15:46:09 +0900
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 03 Sep 2009 23:47:40 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=Mq3wlvlRfzFkHo4SWTg6nBUceKCqGf4GxVc+HX1w/c0=; b=ktT3otzwe9RSjEfpQU7WL8DPC2f+MMGinOru+j8XrXmo+TcasLi7FEub3xTKCrf+dv VupGms4JsPGNorVc9pzqS5tY4AiXsCFdxkiqp5v37nhBPaj/qvO8TrgtBOqGV9ewjiaH 8+jAG8B3x+vKgPdIHjsk/fkpnWY+CFyzKrbsg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=OyHaDWL6BpqlcIvAekoD+35apqrT6lYzaPJuHu9/Z+/vYR0dLgDIVK1uj84pSs/zSu S1Njvj1MQ6Frsb601SmY3sCEgFJRIaRb9vIRw42e00rvyQdTzmgBop5fwGywNtxlgNaV g5/H2FfB1juZCmV4vOSZTVxtv871u5vH+0b/I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EADF0A36011179459010BDF5142A457501CD85C503@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <fdaac4d50909032309l64d3a61ah69871af9126274aa@xxxxxxxxxxxxxx> <EADF0A36011179459010BDF5142A457501CD85C503@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Sep 4, 2009 at 3:41 PM, Cui, Dexuan<dexuan.cui@xxxxxxxxx> wrote:
> Looks the hypercall XEN_DOMCTL_test_assign_device returns a mistake somehow?
>
> Can you please have a look at xen/arch/x86/domctrl.c: arch_do_domctl() and 
> find out in "case XEN_DOMCTL_test_assign_device" what the return value is?
>
> When you see the "Error: failed to assign device...", in "xm dmesg", did you 
> notice a message like
> "XEN_DOMCTL_test_assign_device:  ... already assigned, or non-existent"?

A quick answer, yes. I have this in xm dmesg:

"(XEN) domctl.c:672:d0 XEN_DOMCTL_test_assign_device: 1:0:0 already
assigned, or non-existent"

So what should I do to track this bug? Looking at
xen/arch/x86/domctrl.c like you said above?


Thanks,
J




> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jun Koi
> Sent: 2009?9?4? 14:09
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Fail to passthru PCI device to HVM
>
> Hi,
>
> I am trying to passthru a PCI device to HVM. I think that I already
> successfully unbind the device in Dom0, by verifying like below:
>
> #xm pci-list-assignable-devices
> 0000:01:00.0
>
> Then I put a line like below into HVM config file:
>
> pci = ['0000:01:00.0']
>
> But creating the HVM failed, with below error:
>
> "Error: failed to assign device 01:00.0: maybe it has already been
> assigned to other domain, or maybe it doesn't exist."
>
> The error message seems misleading, as there is no other VM is running
> (only Dom0). So how can I fix this problem?
>
> (I am using -unstable, CS 20145:8fc927798476)
>
> Thanks,
> J
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel