search for: msitransl

...;'domain'': ''0x0000'', ''key'': ''00:02.0'', ''bus'': ''0x00'', ''vdevfn'': ''0x10'', ''func'': ''0x0'', ''opts'': [[''msitranslate'', ''1''], [''power_mgmt'', ''0'']], ''uuid'': ''16d91793-5fe2-e409-9a8c-1bae56a4ff48''}, {''slot'': ''0x1a'', ''domain'': ''0x0000'', ''...

...machine with: - Hypervisor: xen-unstable - Dom0: xen/next-2.6.32.17 commit c3f5aba942c7516a5c76c47345ff0a473daf2542 Hardware: -MSI 890FXA-GD70 with AMD IOMMU -Phenom X6 I''m trying to do PCI passthrough to a HVM, this fails with: Error: Failed to assign device to IOMMU (0000:04:00.0@100,msitranslate=1,power_mgmt=0) Error: pci: to avoid potential security issue, 0000:08:00.0 is not allowed to be assigned to guest since it is behind PCIe switch that does not support or enable ACS. I have found this thread https://bugzilla.redhat.com/show_bug.cgi?id=526713 regarding the ACS problem, which sa...

...00 0x1d 0x0 0x100 ()) (0x0000 0x01 0x00 0x0 0x100 ()) (0x0000 0x01 0x00 0x1 0x100 ()) (0x0000 0x04 0x04 0x0 0x100 ()) ) ) (hap 1) (localtime 1) (timer_mode 1) (pci_msitranslate 1) (oos 1) (apic 1) (usbdevice tablet) (display :0) (vpt_align 1) (vncunused 1) (boot c) (pae 1) (viridian 1) (acpi 1) (vnc 1) (nographic 0)...

...m0 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. 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-...

...m0 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. 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-...

...t; ### > > After running the create command the "failed to assign to IOMMU" error > is seen: > > ### > SunBlade2:/etc/xen/vm # xm create node1.conf > Using config file "./node1.conf". > Error: Failed to assign device to IOMMU > (0000:0e:00.0@100,msitranslate=1,power_mgmt=0) > ### > > We have enabled the debug traces (iommu=verbose loglvl=all > guest_loglvl=all) which show the following at the point of failure > (Please ignore the time stamps): > > /var/log/messages > -------------------------- > > Mar 10 02:57:0...

...until igbvf tries to initialize the PCI device. I have the same error with XEN 4.3, 4.3.1 and the current 4.4-unstable, linux kernel 3.12.0, 3.12.1, 3.9. DomU config: kernel = "/boot/gentoo-DomU" memory = 2048 name = "domU" nic = 2 vcpus = 1 #pci = [''02:10.0,msitranslate=1,permissive=1''] <= same crash #pci = [''02:10.0,permissive=1''] <= same crash pci = [''02:10.0'', ''02:10.1''] vif = [''bridge=xenbr1'',''bridge=xenbr2''] disk = [''phy:/dev/loop4,x...

Hello, I''m hoping someone may be able to push us in the right direction. I''m trying to get one of our products to work with the current branch of Xen (4.0/4.0.0) but I''m hitting a problem. We are currently using Xen 3.3.2 on a Sun Blade 600 chassis (with x6270 blades) this works great. But when we upgrade to Xen 4.0/4.0.1 we get the following message when

...enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as assignable. When I attempt to start the VM I get the error: Error: Failed to assign device to IOMMU (0000:02:00.0@100,msitranslate=1,power_mgmt=0) Below is all the information I can think of that would be useful to help debug it: BIOS VT-d Enabled: http://i43.tinypic.com/nl3a5e.jpg http://i42.tinypic.com/nqvlu1.jpg grub entry: title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 root (hd0,0) kernel...

...enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as assignable. When I attempt to start the VM I get the error: Error: Failed to assign device to IOMMU (0000:02:00.0@100,msitranslate=1,power_mgmt=0) Below is all the information I can think of that would be useful to help debug it: BIOS VT-d Enabled: http://i43.tinypic.com/nl3a5e.jpg http://i42.tinypic.com/nqvlu1.jpg grub entry: title Xen 4.0.0 / Debian GNU/Linux, kernel 2.6.31.13 root (hd0,0) kernel...

...he board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0) root@vm:~# lspci -s 05:00 05:00.0 USB Controller: NEC Corporation USB (rev 43) 05:00.1 USB Controller: NEC Corporation USB (rev 43) 05:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) root@vm:~# cat /etc/xen/vm-nine.cfg kernel = ''/usr/lib/xen/boot/hvmloader'...

...he board/cpu/bios all support vt-d and I think maybe I''m just missing something? Any feedback would be much appreciated :) Output below: root@vm:~# xm create /etc/xen/vm-nine.cfg Using config file "/etc/xen/vm-nine.cfg". Error: Failed to assign device to IOMMU (0000:05:00.0@100,msitranslate=1,power_mgmt=0) root@vm:~# lspci -s 05:00 05:00.0 USB Controller: NEC Corporation USB (rev 43) 05:00.1 USB Controller: NEC Corporation USB (rev 43) 05:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04) root@vm:~# cat /etc/xen/vm-nine.cfg kernel = ''/usr/lib/xen/boot/hvmloader'...

...h [-o|--options=<opt>] <Domain> <domain:bus:slot.func> [virtual slot] Insert a new pass-through pci device. And get different error message when repeating the command: [root@localhost ~]# xm pci-attach VM2 07:10.0 Error: Failed to assign device to IOMMU (0000:07:10.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. And I notice the ''xm dmesg'' contains the following lines: (XEN) Intel VT-d Snoop Control enabled. (XEN) In...

...xen-docs-4.1 4.1.3-3 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121204/605ee5d1/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: qemu-msitranslate-disable.diff Type: application/octet-stream Size: 2461 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20121204/605ee5d1/attachment.obj>

Hi, I tried to attach passrough io device to domU, the command (ended successfully in dom0), but when I entered the domU and typed the "lspci" command I didn''t see the new device, although the dom0 removed it from the "pci-list-assignable-devices". When I tried to detach it from the domU, the detach command returned with timeout error. What did I miss? perhaps I

Hello, I hope that I am posting the correct list with this question. I have been trying to get VGA passthrough working on my system for some time now without success. I do not have the system with me right now, so I will not be able to provide any logs or error messages right now. I will be able to to do so in a couple of hours. I have a VT-d enabled system (Motherboard and CPU) on which I wish

Hello, I hope that I am posting the correct list with this question. I have been trying to get VGA passthrough working on my system for some time now without success. I do not have the system with me right now, so I will not be able to provide any logs or error messages right now. I will be able to to do so in a couple of hours. I have a VT-d enabled system (Motherboard and CPU) on which I wish

...: bool; + vnclisten : string; + vncpasswd : string; + vncdisplay : int; + vncunused : bool; + keymap : string; + sdl : bool; + opengl : bool; + display : string; + xauthority : string; +} + +type pci_info = +{ + v : int; (* domain * bus * dev * func multiplexed *) + domain : int; + vdevfn : int; + msitranslate : bool; + power_mgmt : bool; +} + +type physinfo = +{ + threads_per_core: int; + cores_per_socket: int; + max_cpu_id: int; + nr_cpus: int; + cpu_khz: int; + total_pages: int64; + free_pages: int64; + scrub_pages: int64; + nr_nodes: int; + hwcap: int32 array; + physcap: int32; +} + +type sched_cr...

...sprintf(gc, "vdevfn-%d", i)); + flexarray_set(back, boffset++, libxl_sprintf(gc, "%x", pcidev->vdevfn)); } - flexarray_set(back, boffset++, libxl_sprintf(ctx, "opts-%d", i)); - flexarray_set(back, boffset++, libxl_sprintf(ctx, "msitranslate=%d,power_mgmt=%d", pcidev->msitranslate, pcidev->power_mgmt)); - flexarray_set(back, boffset++, libxl_sprintf(ctx, "state-%d", i)); - flexarray_set(back, boffset++, libxl_sprintf(ctx, "%d", 1)); + flexarray_set(back, boffset++, libxl_sprintf(gc...

The series introduces auto-generation of the type definitions used in the libxl interface followed by auto-generation of a destructor function for each type. In the future it may be possible to use the related data structures for other purposes, for example auto-generation of the functions to marshal between C and language binding data types. tools/_libxl_types.h should be identical both before