similar to: VM creation failure using passthrough with latest unstable

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

OK, cut two of the iommu reserved memory issue patch as we discussed... This patch adds a boolean boot parameter to xen to allow inclusive mapping of all memory below 4GB to the iommu mappings for dom0. The unusable ranges and memory occupied by xen are still excluded. The parameter is "iommu_inclusive_mapping=1" and is off by default. In addition to the parameter, a warning is also

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

The series "HVM firmware passthrough" series in Jan 2013 from Ross Philipson cause two regressions for HVM guests which sadly found their way into the Xen 4.3 release. The first regression causes an incorrect count of tables to be placed in the main header, and can be seen by running dmidecode in any applicable HVM domain. The second regression found its way into the public ABI, making

ACPI table passthrough support allowing additional static tables and SSDTs (AML code) to be loaded. These additional tables are added at the end of the secondary table list in the RSDT/XSDT tables. Signed-off-by: Ross Philipson <ross.philipson@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

This patch introduces support for two new parameters in libxl: smbios_firmware=<path_to_smbios_structures_file> acpi_firmware=<path_to_acpi_tables_file> The changes are primarily in the domain building code where the firmware files are read and passed to libxc for loading into the new guest. After the domain building call to libxc, the addresses for the loaded blobs are returned and

This patch introduces support for two new parameters in libxl: smbios_firmware=<path_to_smbios_structures_file> acpi_firmware=<path_to_acpi_tables_file> The changes are primarily in the domain building code where the firmware files are read and passed to libxc for loading into the new guest. After the domain building call to libxc, the addresses for the loaded blobs are returned and

Utility routines in hvmloader for SMBIOS table validation. Signed-off-by: Ross Philipson <ross.philipson@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xensource.com/xen-devel

Hi all, I downloaded the xen 3.3.0 and now testing the pci pass-through with the NIC. Using late binding, the pci slot 0000:08:01.0 is assigned to pciback. But pci related xm commands are not working. For eg: linux-242:/home/xen-3.3.0 # xm pci-list-assignable-devices Unexpected error: <type ''exceptions.OSError''> Please report to

After changeset 18030 and 18064 were checked in, I found some issues when creating HVM domains with devices assigned: In XendDomainInfo.py, we have the call trace: the global function create() => vm.start() => _constructDomain(). In _constructDomain(), we invoke xc.test_assign_device() and when the function fails (maybe because iommu=1 is not specified in grub entry since iommu is 0 by

Hi, The new smbmount that comes with Samba 2.0.5a doesn't seem to recognize the '-P' command line option. This means that I cannot automatically mount shares from a script, as I need to manually enter the password for each mount. This used to work with the older smbmount, and also with the newer 'smbmount -c ...'. Is this (passing a password on the command line) not supported

Hi, I just had a try using the xeno-unstable. When I used the xc_dom_create.py to create a new domain I got the followings: ============================================== Traceback (most recent call last): File "/usr/bin/xc_dom_create.py", line 332, in ? (current_id, current_port) = make_domain() File "/usr/bin/xc_dom_create.py", line 238, in make_domain

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

On 05/16/2014 06:08 AM, Jan Beulich wrote: >>>> On 16.05.14 at 10:58, <ijc at hellion.org.uk> wrote: >> So it seems like dom0 is unable to (correctly) bind to some hardware >> interrupts. I wonder if these messages from Xen's dmesg are relevant. >> (XEN) Not enabling x2APIC: depends on iommu_supports_eim. >> (XEN) I/O virtualisation disabled >>

I pulled unstable yesterday and noticed xc_dom_create.py does not have a default value for cpu, so python complains Traceback (most recent call last): File "/usr/bin/xc_dom_create.py", line 408, in ? (current_id, current_port) = make_domain() File "/usr/bin/xc_dom_create.py", line 234, in make_domain id = xc.domain_create( mem_kb=mem_size*1024,

Hello everybody, i have a problem setting up a DomU with Windows XP. I get the following error: xen:/etc/xen# xm create windows.hvm Using config file "./windows.hvm". VNC= 1 Unexpected error: exceptions.OSError Please report to xen-devel@lists.xensource.com Traceback (most recent call last): File "/usr/lib/xen-3.1-1/bin/xm", line 7, in ? main.main(sys.argv) File

Xen 3.4 xen-unstable.hg from yesterday with debian etch on 64bit arch Intel/Lenovo Q35 Mainboard with VT-d enabled Bootoptions iommu=1 vtd=1 pci.backhide for a PCI-E nvidia graphiccard xm dmesg Error messages includes: [VT-D] iommu.c: 1694:d32767 iommu: mapping reserved region failed [VT-D] iommu.c: 1542:d0 intel_iommu_add_device: context mapping failed If i try to start my HVM by xm create

Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a guest because of what looks like an issue allocating memory even though xm info shows like 5x the amount of free memory needed? We are still unfortunately still using xm... it's on my list, i know.. We've had this happen on a couple hosts now. Only way to resolve seams to be rebooting the host. I'm going to

Hello, I''m trying to get a freebsd virtual machine running following : http://www.yuanjue.net/xen/howto.html But I get : # xm create freebsd_xen_INSTALL -c Using config file "./freebsd_xen_INSTALL". Error: (14, ''Bad address'') Am I missing something? I am using xen 3.0.4. Thanks and regards, Sergi .... log output from xend.log: [2007-02-27 12:46:59

Hi I have configured few VMs with RHEL5,32 bit, but some VMs after successful stop/restart few times, suddenly they start giving following error from "xm create vm1.cfg" startup. ---- Error: (''c618d493-a696-7637-333d-bd891fa41ac2'', ''VM_metrics'') ---- If i replace system.img, they starts working again. This is what i see in xend.log file. This happens