similar to: [PATCH] xen: Add GS base to HVM VCPU context

The aim of this patch is to define a stable way in which PVH is going to do AP bringup. Since we are running inside of a HVM container, PVH should only need to set flags, cr3 and user_regs in order to bring up a vCPU, the rest can be set once the vCPU is started using the bare metal methods. Additionally, the guest can also set cr0 and cr4, and those values will be appended to the default values

This is a patch repairing a regression in code previously functional in 4.1.x. It appears that, during some refactoring work, calls to hvm_memory_event_cr3 and hvm_memory_event_cr4 were lost. These functions were originally called in mov_to_cr() of vmx.c, but the commit http://xenbits.xen.org/hg/xen-unstable.hg/rev/1276926e3795 abstracted the original code into generic functions up a level in

Fix the mistake for debug exception(#DB), overflow exception(#OF; generated by INTO) and int 3(#BP) instruction emulation. For INTn (CD ib), it should use type 4 (software interrupt). For INT3 (CC; NOT CD ib with ib=3) and INTO (CE; NOT CD ib with ib=4), it should use type 6 (software exception). For other exceptions (#DE, #DB, #BR, #UD, #NM, #TS, #NP, #SS, #GP, #PF, #MF, #AC, #MC, and #XM), it

1: correct LDT checks 2: add address validity check to guest_map_l1e() 3: use {rd,wr}{fs,gs}base when available 4: check for canonical address before doing page walks Signed-off-by: Jan Beulich <jbeulich@suse.com>

Check the return values of the libxc mem_access calls. Free allocated structures (platform_info, domain_info) on errors during initialization and exit. Unbind VIRQ, close event channel and connection to Xen on errors during initialization Signed-off-by: Aravindh Puthiyaparambil <aravindh@virtuata.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> diff -r ea47068fa7a2 -r

This series of patches fix the mistake for debug exception(#DB), overflow exception(#OF) and INT3(#BP), INTn instruction emulation. Introduce new function vmx_inject_sw_exception() which deliver the software excetion, software interrupt and privileged software exception. Split hardware exception as a seperate function(old function vmx_inject_hw_exception()). Also Passed down intruction length

Changes from v1: - Define new struct hvm_trap to represent information of trap, include instruction length. - Renames hvm_inject_exception to hvm_inject_trap. Then define a couple of wrappers around that function for existing callers, so that their parameter lists actually *shrink*. This series of patches fix the mistake for debug exception(#DB), overflow exception(#OF) and INT3(#BP),

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.

Hi, I have buit Xen (32 bit) with PAE and can start multiple Paraguests with 4 gig memory, but cannot launch a single VM with more than 4 gb memory. I would like to launch 1 VM with 30GB or so memory. Are there any config paramters like kernel,/inittrd that need to be changed. I have the ramdisk set to the initrd I used to boot xen with PAE. Thanks - padma

This patch adds a check to see if v_end in setup_guest() wraps around to 0 and lets the builder exit gracefully when it does. Signed-off-by: Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> > -----Original Message----- > From: Keir Fraser [mailto:Keir.Fraser@cl.cam.ac.uk] > Sent: Thursday, June 01, 2006 6:14 AM > To: Puthiyaparambil, Aravindh > Cc:

This patch causes "xm mem-set" to be lower bound on domX-min-mem option in xend-config. Another configuration option called domU-min-mem has been introduced, which works similarly to dom0-min-mem. This is prevents users from freezing the system when doing "xm mem-set" on very low values like 32M. Signed-off-by: Aravindh Puthiyaparambil

Xiaowei, I''m puzzled by the following bit of code in p4_check_ctrs():        if (guest_kernel_mode(current, regs))                 mode = 1;         else if (ring_0(regs))                 mode = 2; If I look at the definition for guest_kernel_mode() it is: include/asm-x86/x86_64/regs.h: #define guest_kernel_mode(v, r)   \     (ring_3(r) && ((v)->arch.flags &

destroy() is being called on exception in both start() and create(). It needs to be called only in create(). Signed-off-by: Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Sir/Madam, This is Aravindh,final year student of Anna University India.We are carrying on research in Cloud Computing and using Open Nebula toolkit for that;for which we need strong network connectivity. The problem i am facing is that i am not able to ping continuously to other nodes in the network. The connectivity is getting lost after 2-3 minutes. we have inspected the connectivity links ,

I''ve checked in a patch that will hopefully fix ''acpi=off'' and ''acpi=ht'' modes for domain0. It''s been tested on just one machine so far, so it''d be good to get some wider feedback. :-) -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Make sure the upper 32 bits of RAX are disregarded during MSR write emulation. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: 2007-08-08/xen/arch/x86/traps.c =================================================================== --- 2007-08-08.orig/xen/arch/x86/traps.c 2007-08-08 11:37:08.000000000 +0200 +++ 2007-08-08/xen/arch/x86/traps.c 2007-08-08 11:40:02.000000000 +0200 @@

Here is a patch for clustered xAPIC and Unisys ES7000 support in Xen. To turn the features on add CONFIG_X86_CLUSTERED_APIC and CONFIG_ES7000 defines to xen/include/asm-x86/config.h Signed off by Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I am getting the following build break on changeset 13662. I am compiling on x86_64 SLES10 with gcc 4.1.0. Is there a fix for this? Thanks, Aravindh Puthiyaparambil Xen Development Team Unisys, Tredyffrin PA make[1]: Entering directory `/root/xen/xen-unstable.hg/tools/firmware'' make[2]: Entering directory `/root/xen/xen-unstable.hg/tools/firmware/rombios'' gcc -o biossums

I am getting the following error when I try to bring up Mini-OS on x86_64 Xen (unstable: 9994). It is dying in xc_linux_build() causing xend to fault and restart. Any clue why this happening? Has something changed in the builder that Mini-OS needs to be aware of? PS: I tried reverting changeset 9993 (Allow linking of mini-os with application-specific object code), but still got the same error

Yes, I saw that problem and removing the vif line or changing it to vif0 fixed it for me. Aravindh > -----Original Message----- > From: wei huang [mailto:huanwei@cse.ohio-state.edu] > Sent: Friday, November 04, 2005 12:14 PM > To: Puthiyaparambil, Aravindh > Cc: Mark Williamson; xen-users@lists.xensource.com; ewan@xensource.com > Subject: RE: [Xen-users] Error "Device 0