similar to: XEN 4.1 performance issue

Sorry to duplicate my issues onto the list - I thought I had looked through this thread before and seen a different error, but apparently Adam and I are running into much the same thing. I'm seeing exactly the same "Failed to assign device to IOMMU" along with the "Device not owned by PCI Back End or pci-stub" in these scenarios. I have not gone back to previous versions,

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

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

Package: xen-utils-common Version: 4.4.0-5 Severity: important Tags: patch Hello, xen-init-list fails to parse output of xen list -l when using XM toolstack. Therefore, /etc/init.d/xendomains stop fails to shutdown any guests still running on shutdown. xen-init-list fails with the following message: /usr/lib/xen-common/bin/xen-init-list Traceback (most recent call last): File

Changes since v1: - Fix a double-free bug introduced by v1, pointed out by Stefano where internal pointer was being passed back to caller from libxl_create_stubdom() 8<---------------------------------------------------------------------- Currently scratch variables allocated by libxl have the same lifetime as the context. While this is suitable for one off invocations of xl. It is not

Signed-off-by: Vincent Hanquez <vincent.hanquez@eu.citrix.com> --- tools/ocaml/Makefile | 2 +- tools/ocaml/common.make | 2 +- tools/ocaml/libs/xl/xl.ml | 209 ++++++++++++ tools/ocaml/libs/xl/xl.mli | 209 ++++++++++++ tools/ocaml/libs/xl/xl_stubs.c | 706 ++++++++++++++++++++++++++++++++++++++++ 5 files changed, 1126 insertions(+), 2 deletions(-)

Hi, I''m running a 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

Hi, all I''m trying SRIOV with Xen but failed to pass through virtual function of SRIOV to dom-U. My platform: Xen-unstable 4.2 Pvops Dom-0 kernel 2.6.32.35 CentOS 5.4 Dom-0 CentOS 5.4 HVM Dom-U And follow VtdHowto wiki page, my steps are: First, bind the virtual function to pci-stub. After that, check the assignable virtual function devices: [root@localhost ~]# xm

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

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''m running 6.26-2-xen-amd64 with xen-hypervisor-3.2-1-amd64. Now I try to pass through a controller card to WHS, at the moment without success because the card isn''t present in DomU. At the first moment I guess it''s a windows problem ;) so I''d tried to boot a Knoppix .iso but same problem there, the passed through device isn''t present in DomU.

# HG changeset patch # User Jim Fehlig <jfehlig@novell.com> # Date 1288301229 21600 # Branch xend-pci # Node ID 461b9d3a643a2c67c961d9fc468a804891f3770d # Parent 28a16074681582f1209c9077f870ccf44927133e Fix pci passthru in xend interface used by libvirt Attempting to define or create a domain whose XML config contains a passthru PCI device fails with libvirt xen84: # cat win2k8r2.xml ...

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

Hello, I''m having problems with VTD on this board. The 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)

Hello, I''m having problems with VTD on this board. The 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)

I saw the pci dev''s config is different from vbd/vnif with following comments: # Parsing the device SXP''s. In most cases, the SXP looks # like this: # # [device, [vif, [mac, xx:xx:xx:xx:xx:xx], [ip 1.3.4.5]]] # # However, for PCI devices it looks like this: # # [device, [pci, [dev, [domain, 0], [bus, 0], [slot, 1]]]] # # It seems the reasoning for this difference is

Hi, once again, Problems with pciback and pci passthrough the system -------------------------------------------------------------------------------- DOMAIN0:~# lspci -tv -[0000:00]-+-00.0 nVidia Corporation nForce3 250Gb Host Bridge +-01.0 nVidia Corporation nForce3 250Gb LPC Bridge +-01.1 nVidia Corporation nForce 250Gb PCI System Management +-02.0

Hi all, I''m trying to get a pci card working on a guest os (ast01) on dum0 I hided the pci card w/: # modprobe pciback hide=''(0b:08.0)'' then added this line to the guest os config file (/etc/xen/ast01) pci = [ "0000:08:0e.0" ] Whenever I try to start it fails w/: # xm create ast01 Using config file "/etc/xen/ast01". Error: function takes exactly 4

Changes since last time: - split auto-generated code in to c and h files - un-break the build system - fix ocaml binding due to libxl API change - lot''s of tidy-ups too numerous to mention Please consider and apply :) -----8<--------------------------------------------------------------- Introduce python binding for libxl. The binding is not yet complete but list_domains,

Hi, I downloaded XEN 3.1 source code on a fedora 6 machine. I did # make world # make install It did not give me an error then when I restarted the machine the Grub did not have 2 options. It had only one option that was the kernel. On loading the OS, when i gave # xend it gives the following errors: [root@localhost sbin]# xend ERROR Internal error: Could not obtain handle on privileged command