similar to: performance counters

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

Hi, I have a question about memory page tables in Xen. As far as I understood, every modification to page table will go through Xen(hypervisor). Is it so that all page tables are actually allocated in Xen(hypervisor) instead of guest OS(domain)? Also, is it the case that Xen(hypervisor) needs to maintain a page table for each process running in every domain? Thanks Haifeng

Hi All I want to use software counters available via "xenperf". However I get this error "Error getting number of perf counters: 38 (Function not implemented)". Am I missing something? Some configuration or option which needs to be turned on before I can use these counters. Any help would be much appreciated. I am using Xen 3.1.0 x86_64 -- Jyotirmaya Tripathi Virginia Tech

I''ve recently noticed that my windows crash dumps fail at around 40-50% under GPLPV. ''xm dmesg'' shows the following: (XEN) grant_table.c:350:d0 Iomem mapping not permitted ffffffffffffffff (domain 865) At first I thought that the cause was just a bug in my grant ref code but it just occurred to me that this could be happening when Windows tries to write out the

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

Hi, V6: The only change from V5 is in patch #6: - changed comment to reflect autoxlate - removed a redundant ASSERT - reworked logic a bit so that get_page_from_gfn() is called with NULL for p2m type as before. arm has ASSERT wanting it to be NULL. Tim: patch 4 needs your approval. Daniel: patch 5 needs your approval. These patches implement PVH dom0. Patches 1 and 2

In p2m.c (line 197 and line 550), the code assumes the number of L3 P2M table entries is 8 (under PAE mode). According to Intel and AMD specs, it is 4. Could someone explain this discrepancy? Is it a bug? -Wei _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi Keir: These two patches remove the need for netloop by performing the copying in netback and only if it is necessary. The rationale is that most packets will be processed without delay allowing them to be freed without copying at all. So instead of copying every packet destined to dom0 we''ll only copy those that linger longer than a specified amount of time (currently 0.5s). As it

Hi, Maybe it''s a dumb question, but I''m actually trying to understand how the memory allocation works within Xen. I try to give 128MB to a domU and see if it increases for example when I "nano" a 500mb file, but the process just get killed when it reachs the 128MB memory limit. How do I configure the guests so they can ask for more memory until a limit is reached

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. What tables are used to manage the

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

On Thu, 17 Jan 2013 22:22:47 -0500 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote: > Jan had some comments about that patch: > > https://patchwork.kernel.org/patch/1745041/ > > Please fix it up so I can put it in the Linux tree. Please see below. Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com> Thanks, Mukesh diff --git a/arch/x86/xen/xen-head.S

Another bundle of issues from Coverity triage. The first one is in x86/mm, and looks scarier than it is. The others are all in xen/drivers and AFAICT are pretty minor. Cheers, Tim.

My system reboots when I trying to start any HVM domU. This problem was described earlier: http://lists.xen.org/archives/html/xen-devel/2013-08/msg01395.html My system is openSUSE 13.1 RC2 with Xen 4.3.0 My hardware is ASRock FM2A75 Pro4 AMD A8-6600K APU Gigabyte Radeon 7850 8 Gb DDR3 1600Mhz I have setup serial console and could provide logs your requested. Attached logs from xl dmesg,

(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 (everything after the mapping

(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 (everything after the mapping

As promised, in preparation for next week's SIG meeting, here's a kick-off discussion about the Virtualization SIG roadmap. I'm mainly tossing out ideas here -- see this is an invitation to discussion. Key things I think should be on the roadmap: * Release process - General cadence - Estimate of the next release (if any) * Specification of targets - Right now, mainly xen4centos

While adding code to create the compatibility p2m table mappings it seemed to me that the creation of the native ones is restricted to memory below the 512G boundary - otherwise, additional L2 tables would need to be allocated (currently other memory following the one L2 page getting allocated would be blindly overwritten). While I realize that machines this big aren''t likely to be

Hi, I''ve added some preliminary support for VT-d for paravirtualized guests. This must be enabled using an ''iommu_pv'' boot parameter (disabled by default). I''ve added some python bindigs to allow xend to assign PCI devices to IOMMU for PV guests. For HVM guests this is handled in ioemu. Not sure if it makes sense to handle both cases in one place. The