Search results
From Xen
Page title matches
- }}|{{Trail|Architecture| * [[X86 Paravirtualised Memory Management|Memory Management]]5 members (0 subcategories, 0 files) - 11:19, 24 June 2013
Page text matches
- * [[:Category:Paravirtualised Architecture|Software Developer Manual for PV]] * [[:Category:Design Document|Design & Architecture Documents]]156 members (2 subcategories, 0 files) - 10:57, 24 June 2019
- This tutorial was done using a Fedora 13 host, installing a paravirtualised CentOS 5.5 x86 (32bit) domU. However, it should work fine for other Fedora/ * Change "Architecture" to "i686" as we're installing 32bit PAE guest VM.6 KB (887 words) - 14:25, 24 October 2014
- == Paravirtualised Network Devices == A Xen guest typically has access to one or more [[Paravirtualization_(PV)|paravirtualised (PV)]] network interfaces. These PV interfaces enable fast and efficient ne27 KB (3,376 words) - 23:47, 6 June 2018
- [[Category:Paravirtualised Architecture]]4 KB (514 words) - 14:43, 18 April 2016
- [[Category:Paravirtualised Architecture]]46 KB (6,924 words) - 10:49, 24 June 2013
- ...ent to GPFN for an auto-translated guest, and equivalent to MFN for normal paravirtualised guests. It represents what the guest ''thinks'' are MFNs. === x86 Architecture ===5 KB (667 words) - 10:57, 24 June 2013
- The Xen paravirtualised MMU model instead requires that the guest be and the architecture of the guest (each entry is four bytes27 KB (4,330 words) - 09:13, 27 May 2015
- [[Category:Paravirtualised Architecture]]3 KB (451 words) - 16:10, 8 September 2023
- }}|{{Trail|Architecture| * [[X86 Paravirtualised Memory Management|Memory Management]]5 members (0 subcategories, 0 files) - 11:19, 24 June 2013