search for: m2p

Hi, Sometimes when I mount a disk image, unmount it, and then try to create a domU using the disk image I get the following error: Error: Device 2049 (vbd) could not be connected. Backend device not found. Im using a FC4 image. Here is the config file: kernel = "/boot/vmlinuz-2.6.16-rc3-xenU" memory=256 name=Domain1 vif = [''bridge=xenbr0''] disk = [

build p2m mapping according to m2p mapping. Signed-off-by: Xin Li <xin.b.li@intel.com> Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...mum page frame number that the RDWR_COMPAT_MPT table can map. Signed-off-by: Malcolm Crossley <malcolm.crossley@citrix.com> diff -r 274e5accd62d -r 8b1e0a2ccd7f xen/arch/x86/x86_64/mm.c --- a/xen/arch/x86/x86_64/mm.c +++ b/xen/arch/x86/x86_64/mm.c @@ -454,7 +454,7 @@ static int setup_compat_m2p_table(struct if ((smap > ((RDWR_COMPAT_MPT_VIRT_END - RDWR_COMPAT_MPT_VIRT_START) >> 2)) ) return 0; - if (epfn > (RDWR_COMPAT_MPT_VIRT_END - RDWR_COMPAT_MPT_VIRT_START)) + if ( epfn > ((RDWR_COMPAT_MPT_VIRT_END - RDWR_COMPAT_MPT_VIRT_START) >> 2) )...

Hello, how can a gfn become 0x555555 as checked in p2m.c:guest_physmap_add_entry() and p2m_alloc_table()? Looking further in p2m.c, audit_p2m() checks only for a 32bit value. So where is that magic number set, and why is it not a define to simplify grepping for users of that value? Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

From: Matt Wilson <msw@amazon.com> Commit f62805f1 introduced a bug where lazy MMU mode isn''t exited if a m2p_add/remove_override call fails. Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com> Cc: David Vrabel <david.vrabel@citrix.com> Cc: Anthony Liguori <aliguori@amazon.c...

I am trying to write a C function to create a vector of integers that can be used by the R calling function. I do not know the size of the vector in the R calling function. (Well, actually, I have an upper limit on the size, but that is so large that R cannot allocate it. What I'm doing in the function is to do a sieving procedure, and the result will be small enough to fit into my

In order to be meaningful and usable together with other measuring methods, their use in my opinion should impose as little overhead as possible. With that, I wonder why per-cpu counters use atomic operations. Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...mation about MFN to PFN mappings, MFN/PFN mappings in a guest''s PTEs, etc. This is what it can do as of now: $ /usr/sbin/xen-mfndump Usage: xen-mfndump <command> [args] Commands: help show this help dump-m2p show M2P dump-p2m <domid> show P2M of <domid> dump-ptes <domid> <mfn> show the PTEs in <mfn> lookup-pte <domid> <mfn> find the PTE mapping <mfn> memcmp-mfns <domid1> <mfn1> <d...

v6 changes: - Check compiler before using [0] or []. v5 changes: - Fix prototypes in v4v.h for do_v4v_op - Add padding to make sure all the structures are 64 bits aligned - Replace [0] with [] v4 changes: - Stop using ssize_t, use long instead - Return -MSGSIZE for message bigger than 2GB - Fixup size handling - Rename

Hi, I looked at the sources and figured out all about the P2M, M2P tables and mappings, Now I''m trying to figure out how dom0 virtual memory is implemented, and I have some questions. The platform I''m working on is x86 with Intel VT enabled. 1. Is dom0 virtual memory managed differently than the other domains? what about hvms? and domUs? 2. Wha...

hi,all I am reading xen address space layout 4M M2P translation table(RO) 24M Page-Frame Information 4M M2P translation table(R/W) 4M Linear Page Table 4M Shadow Linear Page Table 4M Per Domain Mapping 4M Map Cache 12M Direct Map 4M IO Remap I found that all of they are multiple of 2MB. Does xen use 2MB page? under the mode of PAE...

...Checkpoint:227) Reloading memory pages: 0% [2006-04-19 20:42:19 xend] ERROR (XendCheckpoint:227) Received all pages (0 races) [2006-04-19 20:42:19 xend] ERROR (XendCheckpoint:227) ERROR: Failure when submitting mmu updates [2006-04-19 20:42:19 xend] ERROR (XendCheckpoint:227) Couldn''t m2p on PAE root pgdir: 22 [2006-04-19 20:42:19 xend] ERROR (XendCheckpoint:227) Restore exit with rc=1 [2006-04-19 20:42:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:1330) XendDomainInfo.destroy: domid=42 [2006-04-19 20:42:19 xend.XendDomainInfo] DEBUG (XendDomainInfo:1338) XendDomainInfo.destroyDo...

Hell all, I am doing some research work on protecting Xen''s data structures. I know there is a direct-map area(about 12M), in which we can get the physical address of the data structure from its virtual address. My question is : are the stack and the heap of Xen both located in this direct-map area? Since I need protect stack and heap data, so it is easy to identify their physical

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were

...ggested by dvrabel in http://marc.info/?l=centos-virt&m=139289353315469 - 0001-x86-xen-rename-early_p2m_alloc-and-early_p2m_alloc_m.patch - 0008-x86-remove-the-Xen-specific-_PAGE_IOMAP-PTE-flag.patch - 0160676bba69523e8b0ac83f306cce7d342ed7c8 (xen/p2m: check MFN is in range before using the m2p table) - 7cde9b27e7b3a2e09d647bb4f6d94e842698d2d5 (xen: Fix possible user space selector corruption) * Xen 4.4 (Xen + qemu) * libvirt: 1.2.2 - Possibly with migration / pci pass-through back-ported? * dom0 / xen serial console * Ballooning bug? > http://bugs.centos.org/view.php?id=6893 * UEFI...

...e to find a good English name for >the header >file. Another concern is, in the future, we may have more such >definitions. >BTW, Qemu-dm allocates PCI devices MMIO from 0xf0000000. > This patch is to support HVM guests with more than 3.75G memory, and pls comment. Changes are: 1) M2P table and e820 table are changed to skip address space from HVM_RAM_LIMIT_BELOW_4G to 4G 2) shared io page location, when less than HVM_RAM_LIMIT_BELOW_4G memory, it''s the last page of RAM as today, or it''s the last page of HVM_RAM_LIMIT_BELOW_4G RAM. 3) in qemu-dm address space f...

In order to (longer term) constrain 32-bit pv domains running on 64-bit hv to physical memory addresses it can actually control (namely use the m2p map on) without also limiting the amount (and range) of memory accessible to 64-bit domains, the following four patches will change the allocator so that a per-domain address size restriction can be established. A positive side effect of this is that there no longer is a need to constrain DMA addr...

(This is a continuation of "[PATCH v9] xen/grant-table: Avoid m2p_override during mapping") The grant mapping API does m2p_override unnecessarily: only gntdev needs it, for blkback and future netback patches it just cause a lock contention, as those pages never go to userspace. Therefore this series does the following: - the bulk of the original function (e...

(This is a continuation of "[PATCH v9] xen/grant-table: Avoid m2p_override during mapping") The grant mapping API does m2p_override unnecessarily: only gntdev needs it, for blkback and future netback patches it just cause a lock contention, as those pages never go to userspace. Therefore this series does the following: - the bulk of the original function (e...