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

xen-devel

[Top] [All Lists]

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

To: Jun Koi <junkoi2004@xxxxxxxxx>
Subject: RE: [Xen-devel] Fail to passthru PCI device to HVM
From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Date: Fri, 4 Sep 2009 15:13:02 +0800
Accept-language: zh-CN, en-US
Acceptlanguage: zh-CN, en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: 2009年9月04日 00:14:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <fdaac4d50909032359pc8e8d42sda61f6ab2e18c7fc@xxxxxxxxxxxxxx>
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> <fdaac4d50909032346u4988c04cy8a0b93413f0c26de@xxxxxxxxxxxxxx> <EADF0A36011179459010BDF5142A457501CD85C52F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <fdaac4d50909032359pc8e8d42sda61f6ab2e18c7fc@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcotLVFiuwi4898/T6GPrK4TBqh/5gAAEEDg
Thread-topic: [Xen-devel] Fail to passthru PCI device to HVM
To assign device to HVM guest, you should need an IOMMU-capable system like a 
VT-d capable machine.
What device is 01:00.0? Is it a special device like SR/IOV VF?
I guess you have to figure out why the device 01:00.0 is not discovered in 
scan_pci_devices().
Thanks,
-- Dexuan
-----Original Message-----
From: Jun Koi [mailto:junkoi2004@xxxxxxxxx] 
Sent: 2009?9?4? 15:00
To: Cui, Dexuan
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Fail to passthru PCI device to HVM
On Fri, Sep 4, 2009 at 3:55 PM, Cui, Dexuan<dexuan.cui@xxxxxxxxx> wrote:
> Are you sure "xm list" only shows Domain-0 and there is not any other domain?
Yes, I can confirm that.
> Looks it's really weird.
> Can you reboot the the host and re-try to create your hvm domain with 01:00.0 
> assigned?
That didnt help.
BTW: is that true that PCI passthru is only available with VT-d machine??
Thanks,
J
>
> -----Original Message-----
> From: Jun Koi [mailto:junkoi2004@xxxxxxxxx]
> Sent: 2009?9?4? 14:46
> To: Cui, Dexuan
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Fail to passthru PCI device to HVM
>
> 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
>> .&checktime(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
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] Fail to passthru PCI device to HVM , Jun Koi
Next by Date: Re: [Xen-devel] RE: rdtsc: correctness vs performance on Xen (and KVM?) , Jan Beulich
Previous by Thread: Re: [Xen-devel] Fail to passthru PCI device to HVM , Jun Koi
Next by Thread: [Xen-devel] Xenmon execution count problem , Marco Tizzoni
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /