similar to: [PATCH][RESEND] qemu-xen: Intel GPU passthrough, fix OpRegion mapping (v3)

The OpRegion shouldn''t be mapped 1:1 because the address in the host can''t be used in the guest directly. This patch traps read and write access to the opregion of the Intel GPU config space (offset 0xfc). To work correctly this patch needs a change in hvmloader. HVMloader will allocate 2 pages for the OpRegion and write this address on the config space of the Intel GPU. Qemu

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

Expose more host bridge config space value to make the driver happy for all the different revisions of the device. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> --- hw/pt-graphics.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi,all I have tried to passthrough GPU card(Nvidia quadro 4000) on the latest Xen unstable version (QEMU is using Qemu-upsteam-unstable, not traditional Qemu). This issue as below: Windows7 64-bit guest will blue screen when GPU passthrough configure 4g memory,blue screen code is 50, and SUSE 11 64-bit guest will always stay at the grub screen. I noticed that it will relocate RAM that

Platform : Nehalem, official Intel x58 with Core i7 920 (dx58so) Main (Console): Nvidia 9500 GT PCI Express Secondary: Nvidia 8800 GTS PCI Express Yes, I binned the ASUS P6T due to bad VT-d support in the BIOS. With the latest BIOS from Intel, the dx58so has enable/disable for VT-d, ICH FLR and Interrupt Mapping! Helped a lot with getting this working ... Dom0: 2.6.18-xen0 (built from

2011/7/19 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > CC''ing Tim and xen-devel > > On Mon, 18 Jul 2011, Jiageng Yu wrote: >> 2011/7/16 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: >> > On Fri, 15 Jul 2011, Jiageng Yu wrote: >> >> 2011/7/15 Jiageng Yu <yujiageng734@gmail.com>: >> >> > 2011/7/15

Currently it is assumed PCI device BAR access < 4G memory. If there is such a device whose BAR size is larger than 4G, it must access > 4G memory address. This patch enable the 64bits big BAR support on hvmloader. v3 changes from v2: - Remain original print information v2 changes from v1 as comments by Jan. 1) Set Dynamic MMIO high memory address instead of a fixed number 640G 2) Mask

Hi all, this is the tenth version of the patch series to introduce upstream qemu and seabios in the xen-unstable build system. Changes to v9: - rename QEMU_UPSTREAM_TAG to QEMU_UPSTREAM_REVISION: we are going to use it with a branch name by default; - set QEMU_UPSTREAM_REVISION to "master" by default; - set SEABIOS_UPSTREAM_URL to git://xenbits.xen.org/seabios.git by default; - add

The GGC field have moved from 0x52 to 0x50 on Sandy Bridge. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

root@boris-P5Q-E:/mnt/usr/tmp# losetup -f ubuntu11.04.iso root@boris-P5Q-E:/mnt/usr/tmp# losetup -a /dev/loop0: [0809]:406494 (/mnt/usr/tmp/ubuntu11.04.iso) root@boris-P5Q-E:~/vms/natty# cat natty.hvm name = "NattyHVM" builder = "hvm" memory = "2048" disk = [''phy:/dev/sda5,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r''] vif = [

root@boris-P5Q-E:/mnt/usr/tmp# losetup -f ubuntu11.04.iso root@boris-P5Q-E:/mnt/usr/tmp# losetup -a /dev/loop0: [0809]:406494 (/mnt/usr/tmp/ubuntu11.04.iso) root@boris-P5Q-E:~/vms/natty# cat natty.hvm name = "NattyHVM" builder = "hvm" memory = "2048" disk = [''phy:/dev/sda5,hda,w'', ''phy:/dev/loop0,hdc:cdrom,r''] vif = [

Before I get to entrenched in the ACPI code - I thought I''d ping the community to make sure nobody else has investigated this already - Can we present cores vs sockets for guest VCPUs? Right now, the number of total processors can be specified, but can we specify cores per socket? I see this potentially being an hvmloader function, as part of its acpi build code. Could this be

Hi, When Ubuntu12.04 64bit domU boot up, Intel VGA-passthrough doesn''t work. I used the command "xm create" to boot up Dom-U. Windows7-64bit-SP1 works quite well with same configuration. Boot log is as follows. Dom-U dmesg: [ 1.421858] initcall rfcomm_init+0x0/0xf1 [rfcomm] returned 0 after 2192 usecs [ 1.423021] calling i915_init+0x0/0x8d [i915] @ 387 [ 1.423023]

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

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1331924173 -3600 # Node ID bf1d5778ffd10858b402068b9473e410791ebd07 # Parent 72e6530b29463f0913af365f5d085d94ff75627c tools: specify datadir for qemu-xen build to fix firmware loading qemu-xen does currently not find the firmware files, such as vgabios-cirrus.bin. The reason is that qemu-xen uses the default prefix /usr/local.

CC''ing Tim and xen-devel On Mon, 18 Jul 2011, Jiageng Yu wrote: > 2011/7/16 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > > On Fri, 15 Jul 2011, Jiageng Yu wrote: > >> 2011/7/15 Jiageng Yu <yujiageng734@gmail.com>: > >> > 2011/7/15 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > >> >> On Fri, 15 Jul 2011,

I know these are mostly gamers but they have a lot of experience doing PCI pass though: https://discord.gg/du9ecG I have found them extremely helpful in the past doing libvirt PCI passthough. *Paul O'Rorke* On 2020-02-05 10:13 a.m., Jim Fehlig wrote: > On 2/4/20 1:04 AM, Christoph wrote: >> this config does not work... why? > > Without more details, I don't know why

Hi all, I''ve been trying to understand the pci_setup function in hvmloader.c in Xen unstable. I''m kinda lost at Line 328. base = (resource->base + bar_sz - 1) & ~(bar_sz - 1) I''d appreciate if someone could explain to me why base is calculated this way. Specifically, I don''t understand the bitwise AND with the one''s complements of