similar to: Mapping pci resources for graphics passthrough

Hi, In changeset 19130:c8962b24fb50, when using iommu=1, it goes into the hypervisor debugger. Why is this so? Thanks. -Alex _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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, I'm a new user to LLVM. Not really sure if this is the correct place to post, since there isn't really any other forums around. Anyway, the issue I'm encountering is that, I was trying out the first tutorial (http://llvm.org/docs/tutorial/JITTutorial1.html). I attempted to do this in another folder that was copied from llvm/projects/sample. I created a new folder called

Keir, Here''s a first patch to address the issue with rolling over to guest-physical address 0x00000000 when assigning address regions to PCI BARs during HVM boot. For now, this: - Makes the hole bigger: 0xC0000000-0xF5000000. This might be overkill...but it should only matter for 32-bit guest OSes assigned more than 3GB of RAM. - Prevents addresses from above 0xF50000000 from

I have a chipset which supports VT-d (Intel X58) and, according to my motherboard manufacturers, VT-d is enabled in the BIOS and listed as "Intel VT." The problem is that xm dmesg shows "I/O virtualisation disabled" and I get this error message when I try to create a domU with a pci device assigned: ''Error: failed to assign device: maybe the platform doesn''t

We created a 64bit SLES11 SP1 guest, and then used a script to change memory (using mem-set command) periodically (in 1 second): set 1G, set 2G, set 1G, set 2G, and so on. After a few minutes, we encountered QEMU exit due to SIGBUS error. Below is the call trace captured by gdb: The call trace: Program received signal SIGBUS, Bus error. 0x00007f94f74773d7 in memcpy () from /lib64/libc.so.6 (gdb)

On Sun, Sep 20, 2009 at 11:05 PM, Alexia Benington <alexbenington at gmail.com> wrote: > Hi all, > > I can get it to compile with the following command. But I want to make > sure I understand how the Makefiles integrate together. > g++ tut1.cpp `llvm-config --cxxflags --ldflags --libs core engine` > > Really appreciate your help. Thank you. I've been sitting on a

Hello everyone, As one of the steps of improving my ZFS home fileserver (snv_134) I wanted to replace a 1TB disk with a newer one of the same vendor/model/size because this new one has 64MB cache vs. 16MB in the previous one. The removed disk will be use for backups, so I thought it''s better off to have a 64MB cache disk in the on-line pool than in the backup set sitting off-line all

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

Hello, We are looking to use Xen as our hypervisor. However, after doing some research it''s still not clear as to the amount of memory Xen 64bit can support? The highest I''ve found is 4TB of physical memory. For the host VM''s, I''ve found several statements that indicated that the max per VM was 32GB. Are these numbers accurate? And can these limits be removed

Is *.text 1 *the same as *.section*??? .text 1 occurs in entry.S Please tell me what it means? Furquan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

On 9/8/15, 9:35 AM, "Philip Reames" <listmail at philipreames.com> wrote: >On 09/04/2015 11:36 AM, Brett Simmers via llvm-dev wrote: >> On 9/4/15 1:12 AM, Sanjoy Das via llvm-dev wrote: >>> Specifically on "Location records" -- >>> >>> Is it legal for the optimizer to drop the `!locrec` metadata that you >>> attach to

Keir: Not sure from when, at least now hvm_do_resume is double invoked in both 1: arch_vmx_do_resume from schedule_tail, and 2) vmx_asm_do_vmentry of ASM code for both x86 32 & 64 bits. I am wondering if the #1 is a redundant, can u have a double check? thx,eddie _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi I am tring to build the testcode for xenstored # cd xen-3.1-src/tools/xenstore/ # make testcode but it generating error due to conflict of function in fake_libxc with libxc. Error: gcc -Werror -Wp,-MD,.fake_libxc.o.d -I../../tools/libxc -I. -DTESTING -c -o fake_libxc.o fake_libxc.c fake_libxc.c:41: error: conflicting types for ‘xc_evtchn_notify’ ../../tools/libxc/xenctrl.h:692: error:

Hi I am tring to build the testcode for xenstored # cd xen-3.1-src/tools/xenstore/ # make testcode but it generating error due to conflict of function in fake_libxc with libxc. Error: gcc -Werror -Wp,-MD,.fake_libxc.o.d -I../../tools/libxc -I. -DTESTING -c -o fake_libxc.o fake_libxc.c fake_libxc.c:41: error: conflicting types for ‘xc_evtchn_notify’ ../../tools/libxc/xenctrl.h:692: error:

I do recieve this error when building xen-unstable tree. gcc -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -DVMXASSIST -nostdinc -fno-builtin -fno-common -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/xen-unstable.hg/xen/include

Hi, any one help? I have puzzled by the question of device''s MMIO areas. I know a MMIO operation of guest os handled by VMM as follow steps: 1: Qemu-dm does its initialization and presents virtual devices for guest os. 2: virtual bios executes PCI_setup, it will scan the pci bus and get configure space of all devices,then virtual bios allocation system resources(like port I/O range,MMIO

Hello! I am encountering a problem with one of the machines I am using and the timer going backwards. It looks like the problem is due to to a bad PM-Timer entry being found. Though when debugging further, the real source of the problem stems from an ACPI table of type DSDT being parsed as an FADT during boot and certainly a bogus PM-Timer is found there. Here''s the output from

This change has the effect of adding some complexity to the callback routines. The original callback passed an opaque argument which was a private item for the use of the controlling mechanism and its callback function. This change removes this and specifies only an fd. While it''s possible for the controlling mechanism to use the fd as an index to find internal data structures, this is

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