similar to: XCI: can we get to the demo state?

Hi Peter Anvin I tried to use open file and read file SYSLINUX API. But it always make my PC104 freeze. My snip code : ================================================ int __start(void) { int ax,cx,dx,es,si,di,t; com32sys_t inreg,outreg; memset(&inreg, 0, sizeof inreg); memset(&outreg, 0, sizeof outreg); strcopy(__com32.cs_bounce, "test.txt"); inreg.eax.w[0] = 0x0006; //

Hi all, I used syslinux to load linux on DiskOnChip in PC104 for one embbeded project suceefully for several months. But due to power lost sometime the image is corrupted. I want to develop a COM32 util to check CRC for the images and load the good ones. I read in the comboot.doc that com32 can use read file SYSLINUX API call to read a file, and the file must below 64K limit. But the image files

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 Peter, I don't want to waste your time. I only want to say that you do great softwares. I use SYSLINUX to build my embedded system with PC104 board and DiskOnChip flash disk, and thanks for your work it run very well. Now I want to boot it via ethernet and I think that I must use your PXELINUX. Pls keep this softwares live. Thanks for your great works Phung Chi Kien Automation

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

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

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

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

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

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

The following is a revised patch series to add support for a VM generation ID virtual device for HVM guests. The basic requirements of this device are as follows: - It must be exposed somewhere in ACPI namespace with a _CID of "VM_Gen_Counter". - It must also include a _DDN of "VM_Gen_Counter". - It must contain a _HID object but no particular value is required. - It must

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 is hvmloader part of the change that gets rid of the resource conflict warning in the guest kernel. The OpRegion may not always be page aligned. As a result one extra page is required to fully accommodate the OpRegion in that case. Just reserve one more page here. Signed-off-by: Timothy Guo <firemeteor@users.sourceforge.net> diff -r 11b4bc743b1f tools/firmware/hvmloader/e820.c ---

This series contains all the fixes required to produce a working IGD passthrough box. All the changes are previously seen in the dev list but not yet accepted. Some of them are out-dated and need some reshape. Detailed description can be found later in each patch. . [PATCH 1/3] qemu-xen-trad/pt_msi_disable: do not clear all MSI flags . [PATCH 2/3] qemu-xen-trad: Correctly expose PCH ISA bridge

After all the bug fixes over the last few weeks I thought it was high time to release 2.07. It certainly doesn't fix everything, but it fixes several important problems people have reported. Changes in 2.07: * MEMDISK: Workaround for BIOSes which go into a snit when they get a RESET command for the floppy system when there is no floppy in the system.

Hi everybody, I want to ask your help to explain what is going on with my following code: > mydata <- data.frame(y=rbinom(100, 1, 0.5), x1=rnorm(100), x2=rnorm(100)) > glm.fit.method <- function(model,data,...){glm(formula=model,data=data,family="binomial",. ..)} > fit1 <- glm(y ~ x1 + x2, data=mydata, family=binomial()) > update(fit1, .~1) Call: glm(formula =

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, 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

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