search for: memory_map

...m resource base to 100000000 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 02:0 bar 10 size 002000000: 0f0000008 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 03:0 bar 14 size 001000000: 0f2000008 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 06:0 bar 10 size 000200000: 0f3000004 (XEN) [2013-07-17 19:10:12] memory_map:add: dom17 gfn=f3000 mfn=f9a00 nr=200 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 04:0 bar 10 size 000020000: 0f3200000 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 04:0 bar 30 size 000020000: 0f3220000 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 02:0 bar 30 size 000010000: 0f3240000 (XEN) [2013-07-17...

The following dump-core patches changes its format into ELF, adds PFN-GMFN table, HVM support, and adds experimental IA64 support. - ELF format Program header and note section are adopted. - HVM domain support To know the memory area to dump, XENMEM_set_memory_map is added. XENMEM_memory_map hypercall is for current domain, so new one is created. and hvm domain builder tell xen its memory map. - IA64 support IA64 support is for only review. It doesn''t work because Xen/IA64 doesn''t support memory map hypercall. Subject: [PATCH 1/5]...

...INTA->IRQ5 (XEN) HVM4: pci dev 05:0 INTA->IRQ10 (XEN) HVM4: pci dev 02:0 bar 10 size 02000000: f0000008 (XEN) HVM4: pci dev 03:0 bar 14 size 01000000: f2000008 (XEN) HVM4: pci dev 04:0 bar 30 size 00080000: f3000000 (XEN) HVM4: pci dev 05:0 bar 30 size 00080000: f3080000 (XEN) domctl.c:985:d0 memory_map:add: gfn=f3100 mfn=df040 nr_mfns=40 (XEN) HVM4: pci dev 04:0 bar 1c size 00040000: f3100004 (XEN) domctl.c:985:d0 memory_map:add: gfn=f3140 mfn=df640 nr_mfns=40 (XEN) HVM4: pci dev 05:0 bar 1c size 00040000: f3140004 (XEN) domctl.c:985:d0 memory_map:add: gfn=f3180 mfn=df03c nr_mfns=4 (XEN) domctl.c...

I''ve been trying to pass through a GPU to a domU, so far with a lot of trouble but finally a success. PCI passthrough works, I''ve had the usb hubs work successfully. Today I tried to pass through my ATI card to an ubuntu hvm domU with no gfx_passthru and got this: [...] (XEN) memory_map:add: dom14 gfn=f3040 mfn=f7c40 nr=4 (XEN) memory_map:remove: dom14 gfn=f3040 mfn=f7c40 nr=4 (XEN) memory_map:add: dom14 gfn=f3040 mfn=f7c40 nr=4 (XEN) irq.c:270: Dom14 PCI link 0 changed 5 -> 0 (XEN) irq.c:270: Dom14 PCI link 1 changed 10 -> 0 (XEN) irq.c:270: Dom14 PCI link 2 changed 11 -&gt...

...1: pci dev 02:0 INTA->IRQ11 (XEN) HVM1: pci dev 03:0 INTC->IRQ10 (XEN) HVM1: pci dev 04:0 INTA->IRQ5 (XEN) HVM1: pci dev 02:0 bar 10 size 02000000: f0000008 (XEN) HVM1: pci dev 03:0 bar 14 size 01000000: f2000008 (XEN) HVM1: pci dev 05:0 bar 10 size 00004000: f3000004 (XEN) domctl.c:982:d0 memory_map:add: gfn=f3000 mfn=dd5a0 nr_mfns=4 (XEN) domctl.c:982:d0 memory_map:add: gfn=f3004 mfn=dd6a0 nr_mfns=4 (XEN) domctl.c:992:d0 memory_map:remove: gfn=f3004 mfn=dd6a0 nr_mfns=1 (XEN) HVM1: pci dev 05:0 bar 1c size 00004000: f3004004 (XEN) HVM1: pci dev 02:0 bar 14 size 00001000: f3008000 (XEN) HVM1: p...

*RESEND* due to exceeding the mailinglists limit for attachment size. Hi, I''m trying to get secondary vga-passthrough on a HVM guest to work with a AMD HD6570 and the native kernel radeon driver and kernel modesetting. So the guest still gets the emulated stdvga or cirrus device(used in my case here) as primary/boot vga adapter. - When i don''t passthrough the radeon card, the

(moving to xen-devel, xen-arm is for the older PV ARM port) On Tue, 2013-06-25 at 23:59 +0000, Eric Trudeau wrote: > Hi, I am trying to build the XEN tools for our port of XEN to our > Cortex A15-based platform. > > I am using the repo at git://xenbits.xenproject.org/xen.git to > cross-compile the tools into our rootfs. Which branch/changeset are you using? I've heard that

Hello, It looks like upstream linux-2.6.git contains at least the following xen related new features for Linux 2.6.36: - Xen-SWIOTLB support (required for Xen PCI passthru and dom0) - Xen PV-on-HVM drivers - Xen VBD online dynamic resize of guest disks (xvd*) Congratulations! What are the plans for 2.6.37 merge window? I believe at least: - Xen PCI frontend Others? I''m going to

These two patches were originally part of the XSM series that I have posted, and remain prerequisites for that series. However, they are independent of the XSM changes and are a useful simplification regardless of the use of XSM. The Acked-bys on these patches were provided before rebasing them over the copyback changes in 26268:1b72138bddda, which had minor conflicts that I resolved. [PATCH

...ed 0 -> 5 (XEN) HVM1: PCI-ISA link 3 routed to IRQ5 (XEN) HVM1: pci dev 01:1 bar 20 size 00000010: 0000c001 (XEN) io.c:157:d32767 hvm_dpci_eoi:: device 2 intx 0 (XEN) HVM1: pci dev 01:2 INTA->IRQ10 (XEN) HVM1: pci dev 02:0 bar 10 size 00080000: f0000000 (XEN) domctl.c:595:d0 memory_map:add: gfn=f0000 mfn=90480 nr_mfns=80 (XEN) HVM1: pci dev 02:0 bar 14 size 00000008: 0000c011 (XEN) domctl.c:646:d0 ioport_map:add f_gport=c010 f_mport=3410 np=8 (XEN) HVM1: pci dev 02:0 bar 18 size 10000000: 00000008 (XEN) domctl.c:595:d0 memory_map:add: gfn=10000 mfn=90300 nr_mfns=100...

...; into for-hpa/elflink/firmware efi, ansi: Improve console handling even further (e.g. scrolling support) module: Consolidate lots of 32/64-bit code Create derivative-specific files Merge branch 'elflink' into for-hpa/elflink/firmware efi: We don't need two memory_map() functions efi: Update the correct copy of hdr rosh: Update default make target Add per-firmware object directory support efi: Delete unused variables efi: Add support for UGA devices efi: Forward declare 'struct screen_info' Makefile: Only provide...

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

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

...; into for-hpa/elflink/firmware efi, ansi: Improve console handling even further (e.g. scrolling support) module: Consolidate lots of 32/64-bit code Create derivative-specific files Merge branch 'elflink' into for-hpa/elflink/firmware efi: We don't need two memory_map() functions efi: Update the correct copy of hdr rosh: Update default make target Add per-firmware object directory support efi: Delete unused variables efi: Add support for UGA devices efi: Forward declare 'struct screen_info' Makefile: Only provide...

I''ve put together two patches. The first introduces a new dom0_op, set_max_vcpus, which with an associated variable and a check in the VCPUOP handler fixes [1]bug 288. Also included is a new VCPUOP, VCPUOP_create, which handles all of the vcpu creation tasks and leaves initialization and unpausing to VCPUOP_initialize. The separation allows for build-time allocation of vcpus which

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -