similar to: [PATCH][1/5] Add files to support IA64 VT-d

Now if VT-d is enabled, when Dom0 does S3, Xen doesn''t suspend/resume the IOMMU states. The patch adds the missing invocations of iommu_suspend()/iommu_resume() and makes some nesessary fixes: 1) In iommu_set_root_entry(), we should not re-allocate the root-entry when Xen returns from S3; 2) Define the array iommu_state correctly (u8 -> u32); 3) Only save/restore the necessary IOMMU

Thanks for your advice. I will re-organize the patch. Thanks -- Dexuan -----Original Message----- From: Li, Xin B Sent: 2006年10月24日 18:08 To: Petersson, Mats; Cui, Dexuan; Betak, Travis Cc: xen-devel@lists.xensource.com Subject: RE: [Xen-devel] [Patch] Add hardware CR8 acceleration for TPRaccessing >> From: xen-devel-bounces@lists.xensource.com >>

@@ -491,16 +512,15 @@ int pirq_guest_bind(struct vcpu *v, int int rc = 0; cpumask_t cpumask = CPU_MASK_NONE; + WARN_ON(!spin_is_locked(&v->domain->evtchn_lock)); I find this WARN_ON() is triggered harmlessly when I assign device to HVM guest. The call trace is XEN_DOMCTL_bind_pt_irq -> pt_irq_create_bind_vtd() -> pirq_guest_bind(). Should we

After building Xen-3.2.1 I could successfully boot into it if I avoid giving vtd=1 as the boot parameter. If I pass vtd=1 as the boot parameter to xen, the system hangs while booting. The system hangs after the following messages ============================ Boot messages [XEN]..... [Xen] Brought up 2 CPUs... ========================= My chipset DQ35 series is having VT-d support and is enabled in

Currently, Xen does not support injecting an NMI to HVM guest OS. Adding this feature is necessary for those softwares which depend on NMI to function correctly, such as KDB and oprofile. The attached patch allows NMI to be injected to guest OS in NMIP capable platforms. It also enables to queue an NMI and then inject it as soon as possible. Signed-off-by: Haitao Shan

The attached patch adds the HPET description table to ACPI. -- Dexuan Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

In x64 SMP Vista HVM guest (vcpus=2 in the configuration file), the wall clock time is 50% slower than that in the real world. The attached patch fixes the issue. -- Dexuan Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

HVM balloon driver or something, that''s under development, may decrease or increase the machine memory that is taken by HVM guest; in IA32/IA32e host, now Qemu maps the physical memory of HVM guest based on little blocks of memory (the block size is 64K in IA32 host or 1M in IA32E host). When HVM balloon driver decreases the reserved machine memory of HVM guest, Qemu should unmap the

Trying to set up PCI pass through with xen 3.2.1 on Debian Lenny, with xen Kernel 2.6.26... having no luck. I have the following configured... i) Virtualization and vt-d are both enabled in the bios, I have power cycled after making these changes. ii) I have these option in grub menu; iommu=1 pciback.permissive pciback.hide=(07:01.0)(01:00.0) vtd=1 iii) I have this in my cfg file

hi, I just tried the tip of the xen-unstable branch. It looks that the Xen supports 64bit BARs now? Thanks, Neo -- I would remember that if researchers were not ambitious probably today we haven''t the technology we are using! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Changeset 15046:e527b4ff1948 breaks 32-bit HVM guest: when req->size is 4, "1UL << 32" returns 1 in IA32 system, so the mask becomes 0 wrongly. The attached patch fixes this by using 64-bit left-shift. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

The patch moves the struct IO_APIC_route_entry to a common place. This allows us to share the struct with iosapic. Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

At present IA64 Xen doesn''t support MSI for passthrough, so let''s not expose MSI/MSI-X capabilities to IA64 HVM guest for now. Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I really need help. I spent 2 days already on this pci passthrough thing. I''m using Xen 3.2.1 with Centos 5.2 64 bits on intel VT. I''d like to use PCI passthrough and I don''t think I need VT-D functionality. I''m trying to pass PCI 12:01.0 to my domU guest. I got this error when I use "xm create /etc/xen/hvm_centos_2.cfg" Using config file

Hello, I''m also seeing this exact same problem. I''ve posted on xen-users, but did not get an answer. Venkat seems to be experiencing the same problem as me. I have the latest BIOS for my motherboard DQ35JO. (BIOS ver 933) I''m running a Q6600 as well. It hangs at "Brought up 4 CPUs." I''ve tried all sorts of combinations of Xen versions and kernels to

Hi all, I recently upgraded my Xen 3.2.1 to 3.3.1 on Centos 5.2. Everything seems to have gone pretty smoothly except I have a few issues. My system specs are: 4GB RAM Q6600 quad core Intel CPU P5E-VM DO Q35 Intel mobo (VT-d enabled) Skystar2 DVB PCI card passed through to HVM DomU HVM Windows XP SP3 DomU 1. When I restart my DomU, it shuts down and turns into Domain-Unnamed but

Hi everyone, after following in the footsteps of the following discussion (http://lists.xenproject.org/archives/html/xen-users/2013-09/msg00106.html) I had been able to turn my GTX 480 into a Quadro 6000. When I VT-d passthrough it to a Debian jessie VM it shows up fine and CUDA 5.5 seems to function properly up to a point: lspci -v: 00:04.0 VGA compatible controller: NVIDIA Corporation GF100GL

Hi folks, currently I try to setup a new xen host v3.4.1 on top of a Asus P5E-VM DO (latest BIOS, Vt-d capable and enabled in BIOS) to migrate my extisting HVMs (Win2k3 server) running on Xen v3.3.0 to a new home. I want to switch over to 3.4.1 to (hopefully!) passthrough my ISDN board to a HVM domU. Unfortunate there seem some issue with the VT-d DMAR tables which is beyond my knowledge and

Any advice about the patch cr8-acceleration-3.patch? Hi Keir, could you give some comments? Thanks! -- Dexuan -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Cui, Dexuan Sent: 2006年10月25日 11:12 To: Keir.Fraser@cl.cam.ac.uk Cc: xen-devel@lists.xensource.com Subject: [Xen-devel] [Patch][RESEND] Add hardware CR8

I have a system whose cpu can run a hvm. I have some PCI devices that I would like to be able to pass through straight to the domU Specifically, I want to pass through a device to a Windows VM. No, I explicitly do _not_ have a system with Intel''s VT-d technology. In an ideal world, I would be able to pass the graphics and some arbitrary non-graphics PCI cards direct to the DomU.