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] pci passthrough error "unknown command"pci-ins"

To: Weald Wind <wealdwind@xxxxxxxxx>
Subject: Re: [Xen-devel] pci passthrough error "unknown command"pci-ins"
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 10 May 2010 11:06:02 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 10 May 2010 08:17:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <m2rfe15d4c41005071721i845eeb29s32e7f5a864bbf2f0@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: <l2lfe15d4c41005071430vae777f5pb07db845060190d1@xxxxxxxxxxxxxx> <m2rfe15d4c41005071721i845eeb29s32e7f5a864bbf2f0@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Fri, May 07, 2010 at 08:21:39PM -0400, Weald Wind wrote:
> Hi All,
> 
> Please help me.
> 
> I am now installing the XEN on my PC and trying to config the pci pass
> through.
> 
> My motherboard is intel DQ45CB which is vtd enabled.
> I downloaded the latest xen4.0 source from xen.org which is the latest
> release.
> I downloaded stable-2.6.32-x dom0 kernel source from jeremy's repository.
> 
> After compiling the xen and dom0 kernel, I could play it. I could create
> hvm. And the VM was runing very well.
> 
> But when I configured the pci pass through, it always failed with  the
> following error:
> 
> root@charles-dq45:/opt/virtualmachines# xm pci-attach 1 0000:02:00.0
> 
> Error: Failed to assign device to IOMMU (0000:02:00.0@100
> ,msitranslate=1,power_mgmt=0)
> Usage: xm pci-attach [-o|--options=<opt>] <Domain> <domain:bus:slot.func>
> [virtual slot]
> Insert a new pass-through pci device.
> 

Have you tried to have your guest file contain the pci entry instead of
doing hot-plug add? Does that work?

Here is an example:

kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 2048
maxvcpus = 4
serial='pty'
vcpus = 2
disk = [ 'file:/mnt/lab/vs08/root_image.iso,hdc:cdrom,r']
boot="dn"
vif = [ 'type=ioemu,model=e1000,mac=00:0F:4B:00:00:68, bridge=switch' ]
vfb = [ 'vnc=1, vnclisten=0.0.0.0,vncunused=1']
pci = [ '0000:01:00.0' ]
> 
> 
> root@charles-dq45:~# tail  /var/log/xen/qemu-dm-win7.log
> 
> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> Log-dirty: no command yet.
> xs_read(/local/domain/1/log-throttling): read error
> qemu: ignoring not-understood drive `/local/domain/1/log-throttling'
> medium change watch on `/local/domain/1/log-throttling' - unknown device,
> ignored
> cirrus vga map change while on lfb mode
> mapping vram to f0000000 - f0400000
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
> state.
> platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro
> state.
> dm-command: unknown command"pci-ins"

Ugh, that means you don't have CONFIG_PASSTHROUGH set.. but.
> 
> 
> when I compiled the xen-tools, it's said the pci pass has been enabled...
> 
> root@charles-dq45:/opt/xen-4.0.0/tools# make
> ....
> qemu successfuly configured for Xen qemu-dm build
> make -C ioemu-dir all
> === PCI passthrough capability has been enabled ===
> make[2]: Entering directory `/data/opt/xen-4.0.0/tools/ioemu-qemu-xen'
>   CC    audio/sdlaudio.o
>   CC    sdl.o
>   AR    libqemu_common.a
> === PCI passthrough capability has been enabled ===
> === PCI passthrough capability has been enabled ===

You got it there. So is md5sum of the i386-dm/qemu-dm the same as
/usr/<somewhere>/.../xen/qemu-dm? Maybe you haven't installed the
newer version of QEMU?


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

<Prev in Thread] Current Thread [Next in Thread>