similar to: RE: [PATCH] [HVM] Rename file hvm_info_table.htoplatform.h

branch xen-unstable xen branch xen-unstable job build-i386 test xen-build Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git Tree: xen git://xenbits.xen.org/xen.git *** Found and reproduced problem changeset *** Bug is in tree: xen git://xenbits.xen.org/xen.git Bug introduced: ae763e4224304983a1cde2fbb3d6e0c4d60b2688 Bug not present:

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

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

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

Hey, Linus released this Saturday v3.5 and there were quite a few of interesting components/fixes/features that went in! Going to go down the list of what shortlog provided: - Less MSR traps when using AMD machines - so better performance. [andre] - The APIC IPI interface works - which means that ''perf'' in the initial domain works. So no more lockups. Also with some

[PATCH 6/8] HVM save restore: guest memory handling Signed-off-by: Zhai Edwin <edwin.zhai@intel.com> add support for save/restore HVM guest memory diff -r bb1c450b2739 tools/libxc/xc_hvm_restore.c --- a/tools/libxc/xc_hvm_restore.c Thu Jan 11 21:03:11 2007 +0800 +++ b/tools/libxc/xc_hvm_restore.c Thu Jan 11 21:05:45 2007 +0800 @@ -31,6 +31,40 @@ #include <xen/hvm/ioreq.h>

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, the page size of Big Page is 2MB --

(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

Hello, since weeks I was ignoring this warning at my CentOS 5.6/64 bit machine - /etc/cron.weekly/99-raid-check: WARNING: mismatch_cnt is not 0 on /dev/md0 in the hope that the software RAID will slowly repair itself. I also had executed "echo 100000 > /proc/sys/dev/raid/speed_limit_max" on the advice from the mailing list. But now my web server is offline - I had to boot

The following patches are a cleaned up version of the HVM SMBIOS patches I submitted last Friday. Differences include (1) SMBIOS is no longer optional for HVM domU''s. (2) The refactoring I did of hvmloader wasn''t really necessary, so I got rid of it. (3) The patches have been tested on changeset 10671:b20580cf7fc1bfe5119597bb5b576cdd020551d5 (4) The versions of strcpy() and

attached is the vmx domain save/restore patch. works well for different guest/host combination W/O breaking domu save/restore according to my test. pls. first apply xiaowei''s qemu dm fix. ===know issue=== * shpage pfn * HV look for shpage pfn in an e820 entry when init. but some guest(win/em64t linux) will reuse this e820 ram, which cause losing shpage pfn when restore. so this

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

xen_changeset : Sun Apr 16 15:45:57 2006 +0100 9629:07408313ce33 /var/log/xend.log: [2006-04-19 20:42:09 xend] DEBUG (balloon:126) Balloon: free 1348; need 521; done. [2006-04-19 20:42:09 xend] DEBUG (XendCheckpoint:148) [xc_restore]: /usr/lib/xen/bin/xc_restore 11 20 42 133120 1 2 [2006-04-19 20:42:10 xend] ERROR (XendCheckpoint:227) xc_linux_restore start: max_pfn = 20800

https://bugs.freedesktop.org/show_bug.cgi?id=83271 Priority: medium Bug ID: 83271 Assignee: nouveau at lists.freedesktop.org Summary: Windowed mode causes framebuffer not to refresh with PRIME on optimus/kepler discrete GPU QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

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

Hm, well you can see the messages about failure to set plls, which is why you don't see anything. The only odd thing I see is that you're using vesa, which can definitely mess things up. Try not using that. Also try booting with nouveau.debug=debug drm.debug=0xe which might provide more relevant info. On Jun 12, 2015 8:34 AM, "Andre Campos Rodovalho" <andre.rodovalho at

https://bugs.freedesktop.org/show_bug.cgi?id=54830 Bug #: 54830 Summary: Display is shifted to right (ASUS VS197) Classification: Unclassified Product: xorg Version: 7.7 (2011) Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component:

Not yet, but I don''t see any reason for it to work any differently. I simply used vmware because it was convenient. -Adam | -----Original Message----- | From: Simon Gao [mailto:gao@schrodinger.com] | Sent: Thursday, October 05, 2006 11:22 AM | To: Adam Crews -X (acrews - Xerox at Cisco) | Cc: xen-users@lists.xensource.com; Mike Freemon | Subject: Re: [Xen-users]