similar to: Intel HD4000 IGD pass through appears to work, but monitor complains about 'no signal'

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this

I was running benchmark on IO performance using iozone3. In my build, the dom0 resides on a small usb stick and all the storage comes from a NFS mount. I test NFS performance on both dom0 && domU, mounting from the same server. The dom0 test works just well, but the domU run suffers from unstable NFS mount. Since this is a NFS root, the domU just appear to be freezed. The log from both

I was running benchmark on IO performance using iozone3. In my build, the dom0 resides on a small usb stick and all the storage comes from a NFS mount. I test NFS performance on both dom0 && domU, mounting from the same server. The dom0 test works just well, but the domU run suffers from unstable NFS mount. Since this is a NFS root, the domU just appear to be freezed. The log from both

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

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

The i915 driver probes chip version through PCH ISA bridge device / vendor ID. Previously, the PCH ISA bridge is exposed as PCI-PCI bridge in qemu-xen-trad, which breaks the assumption of the driver. This change fixes the issue by correctly exposing the ISA bridge to domU. Signed-off-by: Rui Guo <firemeteor@users.sourceforge.net> Tested-by: Rui Guo <firemeteor@users.sourceforge.net>

Hi all I can''t seem to find any information on vga-passthrough when booting through xen.efi, so I assume it should work. But I encounter a problem on a windows 7 HVM that boots fine when dom0 is booted through MBR but fails when dom0 is booted through UEFI. My system is: DQ77KB motherboard with bios version 44 Core i7-3779T with VT-d Intel HD graphics 4000 In the qemu log it

Hi, I''m trying to get Windows Server 2008 R2 installation booting on Xen 4.0.4. Using the following config: kernel = "/usr/lib/xen/boot/hvmloader" builder = "hvm" shadow_memory = "8" memory = "4096" name = "ts" vcpus = "8" cpus = ["0", "1", "2", "3", "4", "5",

I'm building R-3.1.1 (64 bit) from source on AIX 7.1. It was going well until I hit this: xlc_r -q64 -Wl,-brtl -Wl,-G -Wl,-bexpall -Wl,-bnoentry -lc -L/opt/freeware/lib64 -L/opt/freeware/lib -Wl,-blibpath:/opt/freeware/lib64:/opt/freeware/lib:/usr/lib:/lib -Wl,-bmaxdata:0x80000000 -o tools.so text.o init.o Rmd5.o md5.o signals.o install.o getfmts.o http.o gramLatex.o gramRd.o -lm make[6]:

patch revision history ---------------------- v1: Initial patch to handle this issue involving changing the hypercall interface v2:Totally handled inside hypervisor. v3:Change some logics of handling msi-x pending unmask operations. v4:Some changes related to coding style according to Andrew Cooper''s comments From 51c5b7f1f9c8f319da8adf021b39e18fbd3bf314 Mon Sep 17 00:00:00 2001 From:

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

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

Hi, Can anyone provide the steps to build rpm from source for Xen 4.1.2? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hi, Can anyone provide the steps to build rpm from source for Xen 4.1.2? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hi- I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device model. On boot I see the following error: MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h) A list search yielded (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172), however there was no solution for an HVM VM. I''ve

From: Yang Zhang <yang.z.zhang@Intel.com> The follwoing patches are adding the Posted Interrupt supporting to Xen: Posted Interrupt allows vAPIC interrupts to inject into guest directly without any vmexit. - When delivering a interrupt to guest, if target vcpu is running, update Posted-interrupt requests bitmap and send a notification event to the vcpu. Then the vcpu will handle this

patch revision history ---------------------- v1: Initial patch to handle this issue involving changing the hypercall interface v2:Totally handled inside hypervisor. v3:Change some logics of handling msi-x pending unmask operations. v4:Some changes related to coding style according to Andrew Cooper''s comments v5:Some changes according to Jan''s comments, including a) remove

LLVM_DEFINITIONS used to be defined as set(LLVM_DEFINITIONS "-D__STDC_LIMIT_MACROS" "-D__STDC_CONSTANT_MACROS") Now it is defined as set(LLVM_DEFINITIONS " -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS") (note that it is no longer a cmake list but a string, and the string contains a leading space!) This causes CMake 3.1 to emit g++ -D

Hello everyone, I'm unable to read temperature Gigabyte H77-DH3H motherboard. Is that motherboard supported or am I doing it incorrectly? When trying to access hw.acpi.thermal everything appears to be ok, but it is not, the system always returns 27,8C and 29,8C which fooled me initially - the values never change. Here is output: [chinatsu]:/root# sysctl hw.acpi.thermal

Hi, I have just applied IGD VGA Passthrough patches to Xen 4.4-unstable changeset 27238. Please refer to the 2 attached patches. 1. [Xen-devel] [PATCH 2/3] V4 qemu-xen-trad: Correctly expose PCH ISA bridge for IGD passthrough Link: http://lists.xenproject.org/archives/html/xen-devel/2013-06/msg01720.html 2. [Xen-devel] [PATCH 3/3] qemu-xen-trad: IGD passthrough: Expose vendor specific pci