similar to: PCI pass through issue

Hi, I migrate Xen4.0 to XEN4.1, and found XEN4.1 performance is not as good as 4.0.2. xm shutdown takes longer time, control thru libvirt take longer time, and since I''m testing PCI/VGA passthru, the "createdevice: pci" also take around 5~8 seconds comparing to 1 second in XEN4.0.2. below is my configuration, do you have any suggestions to make the performance better?

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,

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

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

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

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)

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(-)

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is 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

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is 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

On 3/22/23 04:23, nospam at godawa.de wrote: > Jim Fehlig schrieb: >> >> What is the libvirt version? > > It's the "latest and greatest" I get from this source: > > [root at xen1 ~]# virsh --version > 6.6.0 > > [root at xen1 ~]# libvirtd --version > libvirtd (libvirt) 6.6.0 > > [root at xengfs1f ~]# yum list | grep libvirt >

Dear all, I have a question about merge two character vectors of the same length into one. For example: X= c('A', 'B', 'C', 'A', 'D', .......) # 26 possible alphabet values with length 1000 Y=c('B', 'A', 'C', 'A', 'C', ........) # 26 possible aphabet values with length 1000

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

Hello, I am looking into building a workstation using Xen to host several operating systems. Looking at the pci passthrough requirements of Xen4.1 on the VTdHowTo<http://wiki.xensource.com/xenwiki/VTdHowTo>page, I am a little puzzled with the fact that only Intel Core2Duo (with VT-x), Core2Quad, i7 and Core i5 (vPro Brand) CPU''s are supported while motherboards with the i55x0

Hi! I''ve got a motherboard (Gigabyte GA-G33-DS3R) where the Ethernet port has been broken. I''ll buy a new motherboard, but wants to keep all my other equipment (CPU, Memory, TV-cards etc). The requirements/wishes on the new motherboard are 2 Ethernet ports and 2 PCI slots. It would also be good if it would support VT-d. I''ve found two boards that would fulfill my

Hi, I am working of Intel 82576 device to test the SRIOV functionality. I want to assign VFs to a VMs(domU) and verify the control and data path. I installed Xen-unstable with 2.6.30-rc3(dom0). But the SRIOV functionality isn''t working, because MSI is not supported. Please let me know, what version of Xen and dom0 supports above functionality? Is there any tool available to manage SRIOV

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

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

On Wed, Jun 06, 2018 at 08:11:54PM +0800, Tiwei Bie wrote: > On Tue, Jun 05, 2018 at 03:23:11PM +0300, Michael S. Tsirkin wrote: > > On Tue, Jun 05, 2018 at 09:36:53AM +0800, Tiwei Bie wrote: > > > On Mon, Jun 04, 2018 at 07:32:25PM +0300, Michael S. Tsirkin wrote: > > > > On Fri, Jun 01, 2018 at 12:02:39PM +0800, Tiwei Bie wrote: > > > > > There is a