search for: power_mgmt

...39;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'', ''key'': ''00:1a.0'', ''bus...

...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 says the pci bridg...

...boot c) (pae 1) (viridian 1) (acpi 1) (vnc 1) (nographic 0) (nomigrate 0) (usb 0) (tsc_mode 0) (guest_os_type default) (device_model /usr/lib/xen-4.1/bin/qemu-dm) (pci_power_mgmt 0) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL 1)) ) ) (status 2) (state r-----) (store_mfn 1044476) (device (vif (mac 02:16:3e:c8:29:36) (script /etc/xen/scripts/vif-bridge)...

...uld 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-dirty: no comman...

...uld 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-dirty: no comman...

...gt; 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:05 SunBlade2 kern...

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

..., 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 /boot/x...

..., 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 /boot/x...

...os 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'' builder = ...

...os 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'' builder = ...

...=<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) Intel VT-d Dom0 DM...

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

...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_credit = +{ + weight: int;...

...t;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, "opts-%d&q...

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

The following series implements libxl_domain_config_init as per the libxl API requirement that each type has an init function. The first function does this in an open coded manner and is proposed for Xen 4.2. The second function is RFC only since it moves the definition of this type into the IDL and makes the required infrastructure updates to enable this. I think this is more 4.3 material at

Hi, All the reviews for the AMD 890fx chipset reported that it supports IOMMU v1.2. But I cannot find any mention of that on AMD site. Does 890fx support IOMMU? Do 890fx motherboards with IOMMU exist? Does Xen support 890fx? Regards, Leonardo _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel