similar to: [PROPOSED REMOVAL] PV guest superpage mappings

This patch enables support of hugepages in a pv Xen environment. It is against the latest xen unstable tree on http://xenbits.xensource.com. The patch assumes the guest is passing a physically aligned hugepage. It does reference counting on all the underlying pages. Dave McCracken Oracle Corp. _______________________________________________ Xen-devel mailing list

This is the latest version of a patch that adds hugepage support to the Xen hypervisor in a PV environment. It is against the latest xen-unstable tree on xenbits.xensource.com. I believe this version addresses the comments made about the previous version of the patch. Hugepage support must be enabled via the hypervisor command line option "allowhugepage". It assumes the guest

We have implemented hugepage support for guests in following manner In our implementation we added a parameter hugepage_num which is specified in the config file of the DomU. It is the number of hugepages that the guest is guaranteed to receive whenever the kernel asks for hugepage by using its boot time parameter or reserving after booting (eg. Using echo XX > /proc/sys/vm/nr_hugepages).

Does upstream dom0 support superpage? best regards yang

hi, I tried to make huge page request in Fedora x86_64 PV guest using xen 4.1 unstable and it crashed(crash info given below) I had enabled superpages in config file I had also set hugepages parameter at boot time for the PV Dom U By excuting # cat /proc/mem_info | grep Huge gave me that there are 10 free huge pages available , still the domain crashed. [ 86.403654] BUG: unable to handle

Here is a set of small patches that enables hugetlb on PV machines. They are against xen-unstable and linux-2.6.18-xen. The patches are specifically for x86_64. I originally had these patches working back in May, but recently for some reason my machine now refuses to boot the baseline xen-unstable, so I''ve been unable to verify them. However, they should still work. Comments, bug

Hi all, This is today''s nightly testing report; no new issue found, bug #1259 got fixed. Some vt-d cases failed in first round testing, but can get pass in retesting. Fixed issue: ============================================== 1. booting windows guest causes Xen HV crash http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1259 Old issues:

Hi there, We are using latest version of XCP on 6 hosts. While issuing VM.start or VM.start_on xmlrpc functional call , it says : {''Status'': ''Failure'', ''ErrorDescription'': [''SESSION_INVALID'', ''OpaqueRef:cfb6df14-387d-40a1-cc27-d5962cba7712'']} However if I put VM.start in a loop maybe after

Hi, I''ve played a little bit with the xen scheduler to enhance the performance of paravirtualized SMP domains including Dom0. Under heavy system load a vcpu might be descheduled in a critical section. This in turn leads to even higher system load if other vcpus of the same domain are waiting for the descheduled vcpu to leave the critical section. I''ve created a patch for xen

Folks, Xen 3.4.2 is the latest maintenance release in the 3.4 stable branch. There are a range of bug fixes since 3.4.1, and we recommend users to upgrade. The source repository can be downloaded from: http://xenbits.xensource.com/xen-3.4-testing.hg The release is tagged ''RELEASE-3.4.2''. Alternatively source tarballs can be downloaded from:

Folks, Xen 3.4.2 is the latest maintenance release in the 3.4 stable branch. There are a range of bug fixes since 3.4.1, and we recommend users to upgrade. The source repository can be downloaded from: http://xenbits.xensource.com/xen-3.4-testing.hg The release is tagged ''RELEASE-3.4.2''. Alternatively source tarballs can be downloaded from:

Hi list, I''ve read about recent efforts to push pv-on-hvm drivers to Linux mainline and I''m curious to know the cause for this. What''s the advantage over using pv_ops directly and booting the kernel paravirtualized? Are there plans to move Linux domUs closer to the KVM way (from an architectural point of view)? Hope you can help. Regards, Markus

And also put my name behind the mainternship. Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> --- MAINTAINERS | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 0358a3e..e2252fc 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -193,8 +193,9 @@ F: xen/include/xen/iommu.h LINUX (PV_OPS) M: Jeremy Fitzhardinge

Folks, The first release candidate for Xen 4.0.0 has been tagged and published. You can grab it from here: http://xenbits.xensource.com/xen-unstable.hg (tagged ''4.0.0-rc1'') Please test it! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I wanted to run without 2MB and 1GB EPT pages, so I added "hap_2mb=0 hap_1gb=0" to the Xen grub command line. However I see the following on Xen boot: (XEN) EPT supports 2MB super page. When I bring up a guest I see a non-zero number of 2MB pages in the "xl create" output: xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000017af10 TOTAL:

I can boot a 64-bit HVM image on my SVM-system, and it goes quite a long way before it crashes (due to not finding the hard-disk image and thus no root FS - which I think may well be the configuration file). But if I set debug=y in the Rules.mk, I don''t get very far at all - it crashes well before it gets to any user-mode (Ring3) - in fact, I think it''s crashing pretty much as

Hi, I was wondering if you guys are working on a linux-image-2.6.27-amd64-xen? That would be great! Thomas

There''re basically two methods to enter a given C-state: legacy (hlt + I/O read), and native(using mwait). MWAIT is always preferred when both underlying CPU and OS support, which is a more efficient way to conduct C-state transition. Xen PM relies on Dom0 to parse ACPI Cx/Px information, which involves one step to notify BIOS about a set of capabilities supported by OSPM. One capability

Hi Keir The latest (hybrid) patchset again... Change from v4: 1. Add support for PV clocksource on HVM. (Replace evtchn enabling with pv clock enabling). 2. Update the patch following Tim''s comments. Change from v3: 1. Minor polish the patchset. Replace several specific is_hvm_pv_evtchn_domain() judgement. 2. Name changed... Change from v2: 1. Change the name "hybrid"

Are you expecting improvement after  09/15/2009 new-swiotlb commits ? 4097,6144, "No_dom0_mem_specified" don''t look to me to have any. Boris.   _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel