similar to: Porting Bochs bios to Xen/hvmloader?

This patch adds an implementation of the TCG BIOS extensions to the Bochs BIOS and enables logging of boot measurements using the previously implemented support for TCPA ACPI tables. A low-level driver for a TPM TIS device and an Atmel device is provided. The implemented specification is described here:

This patch set mainly allows the user to build a seabios or rombios only version of hvmloader. In addition, when building a seabios only hvmloader, Option ROMs like vgabios and etherboot are no longer required, and therefore can be disabled from the build. Dependency on the bcc compiler can also be avoided the same way. v2: Separate patches for separate issues Introduced config option to

Hi, when I boot my windows, the bios that is used is a qemu bios. I''m searching for the bios file on my system that is used by the hvmloader. I found bios files from bochs : -rw-r--r-- 1 root root 131072 2008-06-28 03:05 /usr/share/bochs/BIOS-bochs-latest -rw-r--r-- 1 root root 65536 2008-06-28 03:05 /usr/share/bochs/BIOS-bochs-legacy -rw-r--r-- 1 root root 131072 2008-06-28 03:05

Attached simple patch modifies the rombios and hvmloader Makefiles to default to an 8-way bochs bios for the hvmloader. Is there a reason to not define the mp config table by default for >1 processors (8), in the repository? Seems like using the hvm guest config file can the methodolody to describe a UP guest regardless of the mptables. Defaulting the rombios to MP would allow users to

This patch set mainly allows the user to build a seabios or rombios only version of hvmloader. In addition, when building a seabios only hvmloader, Option ROMs like vgabios and etherboot are no longer required, and therefore can be disabled from the build. Dependency on the bcc compiler can also be avoided the same way. v2: Separate patches for separate issues Introduced config option to

When booting HVMs with SeaBIOS, the BIOS itself takes care of extracting option ROMs from the PCI devices. These ROMs are usually provided with by the device model (qemu). Thus, hvmloader should not require any longer the rombios, stdvga, cirrusvga or etherboot ROMs to be present. Also, the 32bitbios_support.c file is specific to rombios and should not be built when building hvmloader with

Some firmware, such as OVMF relies on this value to get the size of extra memory above 4GB. Seabios in Xen doesn''t need this as it gets e820 directly from Xen. Rombios doesn''t read this value. Signed-off-by: Wei Liu <wei.liu2@citrix.com> --- tools/firmware/hvmloader/hvmloader.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git

Package: xen-utils-unstable Version: 3.3-unstable+hg17192-1 Severity: important Tags: patch In tools/firmware/Makefile, INST_DIR is $(DESTDIR)/usr/$(PREFIX)/boot but $(PREFIX) is empty. hvmloader doesn't get installed. diff -ru xen-unstable-3.3-unstable+hg17192.orig/debian/patches/tools-prefix.diff xen-unstable-3.3-unstable+hg17192/debian/patches/tools-prefix.diff ---

Hi, These set of patches are affected by replacing bios_relocate hook with bios_load hook in hvmloader. The patches for code files config.h and hvmloader.c also contains part of the contents of Enabling UEFI BIOS(OVMF) support in Xen-unstable HVM. Is there any problem with these patches? Thank you very much. # HG changeset patch # User gbtju85@gmail.com # Replace bios_relocate hook with

This patch adds TCG BIOS extensions to the high memory area along with some often-used libc utility functions. The TCG extensions are described here: https://www.trustedcomputinggroup.org/specs/PCClient/TCG_PCClientImplementationforBIOS_1-20_1-00.pdf I have tried to keep the patching with rombios.c to a minimum, but some amount of code needs to be inserted at various locations. The code is

Hi, Please post any comments or questions if you get around to testing them. Your comments are very welcome! Best regards, -Gonglei > > >>> On 22.10.13 at 06:08, "Gonglei (Arei)" <arei.gonglei@huawei.com> > wrote: > > > Hi, guys. The new patch has been modified based on the principles you > > > suggested, thank you so much. > > >

Hello list, I''ve installed Xen 3.0.3-testing from source on my spiffy new socket AM2 machine and I''m eager to play with fully virtualized guests. The problem is, it seems the hvmloader wasn''t installed (or built) when I built and installed Xen. I''m getting the following error : Error: Kernel image does not exist: /usr/lib/xen/boot/hvmloader So I did a quick

Hi List, many People seem to be interested in the Graphic-Card Passthrough Feature (for more or less obvious reasons). Official Support is still under development, and i hope not to interfere with it in any (bad) way ... But i remember my own painfull and timeconsuming research when i wanted this feature to work, so i thought perhaps this spares some time for the unpatient users like me :)

The SeaBIOS ROM image may validly exceed 128k in size, it''s only our interface code that so far assumed that it wouldn''t. Remove that restriction by setting the base address depending on image size. Add a check to HVM loader so that too big images won''t result in silent guest failure anymore. Uncomment the intended build-time size check for rombios, moving it into a

This patch series adds the ability to selectively disable the S3 and S4 ACPI power states for HVM guests. Since there is a general move towards retiring the hvm_info_table structure, the first patch moves the acpi_enabled flag out of the hvm_info_table and into a xenstore key (platform/acpi). The second patch then introduces the acpi_s3 and acpi_s4 configuration parameters to the xl config file

I have a self built system using an Intel D 920 processor and a MB that supports VT. I''m able to run HVM domains fine, but have trouble getting multiple VCPUs for these domains. Here is an example of one of my configs. # -*- mode: python; -*- #============================================================================ # Python configuration setup for ''xm create''. #

This patch supports basic gfx passthrough on QEMU: - disable emulated VGA adpater if there is passthroughed gfx - register/unregister legacy VGA I/O ports and MMIOs for passthroughed gfx Signed-off-by: Ben Lin <ben.y.lin@intel.com> Signed-off-by: Weidong Han <weidong.han@intel.com> _______________________________________________ Xen-devel mailing list

A "main" function is defined in Xen-3.1.0-source/tools/firmware/hvmloader/hvmloader.c. In this main function, rombios, vgabios and vmxassist are copied to specified address, with following commands memcpy((void *)ROMBIOS_PHYSICAL_ADDRESS, rombios, rombios_sz); ... memcpy((void *)ETHERBOOT_PHYSICAL_ADDRESS, etherboot, sizeof(etherboot)); .... But after searching the whole

Windows SVVP tests requiring a HPET ACPI table is in my opinion not a valid reason to always expose that table - respective tests should be run with "hpet=1" in the guest config file. The problem here is that at least with qemu-traditional, which by default doesn''t appear to emulate a HPET, the advertising here can mislead an OS to believe that there actually is a usable HPET,

Thank you. I notice the system then jumps to F000:FFF0 to execute. But because VMX is turned on, switching to real-mode would incur problems? I don’t find any clue to turn on the vm86 mode as Readme in the tools/firmware directory puts. Best regards, Hu Jia Yi Ext: 20430 Tel: 65-67510430 -----Original Message----- From: Cui, Dexuan [mailto:dexuan.cui@intel.com] Sent: Thursday,