similar to: iommu: mapping reserved region failed - Q35 - VT-D Issue

On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller) driver is not loading correctly if vtd support in Xen is enabled. It fails at the point of initializing firmware. I wasn''t seeing this error with Xen-3.2.2-rc3 (Unstable version), though with vtd disabled in Xen-3.3.0, it is working. Looks like a degrade problem. Any clues? Thx, Venkat

Dear Users, in my case, i want to passthrough a pci-e graphiccard to a hvm guest. In the bios i have to select whether the onboard graphic is used as primary vga output or the pci-e one. If i define the onboard one then the pci-e card gets unavailable in xen, furthermore lspci did not show it anymore. if i set the pci-e card as primary, it comes up fine in xen, but if i hide that card which is

-----Urspr?ngliche Nachricht----- Von: Gene Cumm <gene.cumm at gmail.com> > 1) What version of Syslinux? I just checked the configuration again and we're not using syslinux. It's pxelinux.0 and is served via: filename "pxelinux.0"; next-server 172.16.0.2; # strings pxelinux.0 | grep PXELINUX PXELINUX 3.82 3.82 But thats the same version. Any ideas? It's part of

Hi, I want to run a HVM domU. I have a Dell Optiplex 755: model name : Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz I have enabled VT in BIOS settings under performance. However, after I boot into a linux kernel (not under Xen), grep vmx /proc/cpuinfo returns nothing. When I boot under Xen, I get (XEN) Intel VT-d has been enabled (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not

This patch maps RMRR in intel_iommu_add_device() if the device has RMRR; move domain_context_mapping() to be in front of list_move() in reassign_device_ownership(). Currently, hypervisor sets up devices and RMRR for dom0, and dom0 also adds devices for itself via hypercall. This is obviously duplicate. In order to allow old dom0 kernels to work with iommu-capable platforms, maybe it cannot be

Hello XCI developers, I have a HP6930, downloaded xenclient from the git. And by following the instruction in HOWTO, I could get xenclient boot up fine. I try then to start a guest using xenvm.readme as template and nothing shows on the screen for the guest, although xenops shows 2 doms running. Can you point me to how to start a guest. And also, is the tree downloaded from git enough to arrive

Dear Developers & Users, I'm using pxe booting on SLES11 sp3. My clients are all Lenovo/IBM E73 Workstations with latest bios. My config is: LABEL disk LOCALBOOT 0 unfortunately this is not working. I tried all 5 options to localboot 1,2,3... as well as chainloading with chain.c32 like described in the wiki: http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#LOCALBOOT

hi, I am trying the Xen unstable on X48 chipset these days but it failed due to an corrupted RMRR table in the ACPI. The following is the acpi dump of DMAR. DMAR @ 0x7fef1000 0000: 44 4d 41 52 20 01 00 00 01 d1 49 4e 54 45 4c 20 DMAR .....INTEL 0010: 44 58 34 38 42 54 32 20 12 06 00 00 4d 53 46 54 DX48BT2 ....MSFT 0020: 13 00 00 01 23 00 00 00 00 00 00 00 00 00 00 00 ....#...........

Good evening dear users and developers, I'm using samba 3.5.6 on Debian Squeeze as Domain-Controller for several Windows XP clients. Config below. One user installed a software with settings in C:\documents and settings\martin\.vkbstandalone/.metadata/.plugins/de.vkb.standalone.tomcat/work/catalina/localhost/eba_standalone_web/org/apache/jsp/jsp/composite/angebot/angebot zum

I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit) on a SUPERMICRO C7X58 board I see the following the error in my boot log. (XEN) [VT-D]dmar.c:372: RMRR is incorrect. This problem is caused by this condition in dmr.c:372. if ( rmrr->base_address >= rmrr->end_address ) { dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n"); return -EFAULT; } As an

I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit) on a SUPERMICRO C7X58 board I see the following the error in my boot log. (XEN) [VT-D]dmar.c:372: RMRR is incorrect. This problem is caused by this condition in dmr.c:372. if ( rmrr->base_address >= rmrr->end_address ) { dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n"); return -EFAULT; } As an

On Fri, Oct 30, 2020 at 07:44:43PM +0800, Jason Wang wrote: > >On 2020/10/30 ??6:54, Stefano Garzarella wrote: >>On Fri, Oct 30, 2020 at 06:02:18PM +0800, Jason Wang wrote: >>> >>>On 2020/10/30 ??1:43, Stefano Garzarella wrote: >>>>This patch enables the IOTLB API support for vhost-vsock devices, >>>>allowing the userspace to emulate an IOMMU

Hi list, I have a problem with a new laptop (reproducable on other machines too) and the xen hypervisor. When the hypervisor gets booted with VESA mode 800x600 I see some messages and then the screen contents is switched into a pattern of vertical colored lines and never comes back. In text mode all works well, but later the pattern appears when the X servers starts. I disabled VTd in the bios

This adds a boolean boot parameter to xen to allow reserved memory regions to be added to the iommu mappings for dom0. The parameter is "iommu_include_reserved" and is off by default. A warning is also traced when incorrect RMRR to system memory map values are detected. This is being added to address some incorrect BIOS''s that do not report correctly the requied reserved memory

Hi, I did a git pull on pv_ops tree this morning and now get a crash when eth0 is started, here is the full boot log: Booting ''Xen 3.4 / Linux 2.6.29-rc6-tip'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz com1=115200,8n1 console=com1,vga iommu=1 [Multiboot-elf, <0x100000:0x131748:0x8e8b8>, shtab=0x2c0078, entry=0x100000] module

Add public HVM definitions header for firmware passthrough support (including comment describing the feature''s use). In addition this header is used to collect the various xenstore string values that are used in HVMLOADER. Signed-off-by: Ross Philipson <ross.philipson@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org

I have pulled a recent (today''s) clone of staging/xen-unstable.hg and I get a failure when trying to create a domain with xend/xm. The failure I get is: Error: (''<domain GUID>'', ''VM_metrics'') I have traced the problem down to where the pci = [ ''02:00.0'' ] parameter (which is the value in my case) from my configuration

Dear Users, Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64: After i want to start the HVM i get: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072)

Hi, I have a guest enabled vIOMMU, but on the guest there are several devices in the same iommu group. Could someone help to check if I missed something? Thank you very much! 1. guest xml: # virsh edit q ... <os> <type arch='x86_64' machine='pc-q35-rhel7.5.0'>hvm</type> <loader readonly='yes' secure='yes'

Rather than requiring the scopes to be the first members of their respective structures (so that casts can be used to switch between the different views), properly use types and container_of(). Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/passthrough/vtd/dmar.c +++ b/xen/drivers/passthrough/vtd/dmar.c @@ -304,13 +304,15 @@ static int __init scope_device_count(con