xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jeroen Groenewegen van der Weyden <groen692@grosc.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: "Christoph.Egger@amd.com" <Christoph.Egger@amd.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Dong, Eddie" <eddie.dong@intel.com>
Subject: Re: [PATCH 20 of 20] n2 MSR handling and capability exposure
Date: Tue, 26 Jul 2011 15:33:57 +0200	[thread overview]
Message-ID: <4E2EC245.2030905@grosc.com> (raw)
In-Reply-To: <20110726114233.GJ8970@whitby.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1592 bytes --]

Tim, This improved a lot. the domu does not become in-responsive 
anymore. However, all four l2 guest are started. but 2 out of 4 are 
hanging/in-responsive after 30 to 60 seconds.

L1 domu (sles11sp1)
  -> seems to be ok

L2-1 propetary OS, seems to be ok
L2-2 propetary OS, seems to be ok
l2-3 sles10sp3, hanging/in-responsive
l2-4 sles10sp3, hanging/in-responsive

no degug/error messages in dmesg.

mfg,
jeroen

Op 26-7-2011 13:42, Tim Deegan schreef:
> At 12:46 +0200 on 26 Jul (1311684389), Jeroen Groenewegen van der Weyden wrote:
>> Here my input
> Thanks.  Looks very similar to the bug I thought I fixed with my patch.
>
> VCPUs 1 and 3 are always at 0xa01a1c9d:<0f>  01 c2 eb 03 0f 01 c3
> which is probably this fragment of code from KVM's vmx_vcpu_run():
>
>          /* Enter guest mode */
>          "jne .Llaunched \n\t"
> 	__ex(ASM_VMX_VMLAUNCH) "\n\t"
>          "jmp .Lkvm_vmx_return \n\t"
>          ".Llaunched: " __ex(ASM_VMX_VMRESUME) "\n\t"
> 	".Lkvm_vmx_return: "
>
> So, just like the case I saw, they're trying to VMLAUNCH a VMCS and
> failing.  That should only fail if the VMCS is already launched.
>
> I think the reason they're _stuck_ is that error paths for VMLAUNCH and
> VMRESUME emulation are wrong; I can fix them up a little but I suspect
> that won't solve the problem; just change it from a hang to some other
> failure mode.
>
> Can you try the attached patch instead of the previous one?
>
> Tim.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


[-- Attachment #1.2: Type: text/html, Size: 2365 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-07-26 13:33 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  8:25 [PATCH 00 of 20] Rebased Nested VMX v2 Eddie Dong
2011-06-09  8:25 ` [PATCH 01 of 20] pre-cleanup1: Extend nhvm_vmcx_guest_intercepts_trap to include errcode to Eddie Dong
2011-06-09  9:46   ` Christoph Egger
2011-06-09  8:25 ` [PATCH 02 of 20] pre-cleanup2: Move IDT_VECTORING processing code out of intr_assist Eddie Dong
2011-06-09  8:25 ` [PATCH 03 of 20] Add data structure for nestedvmx Eddie Dong
2011-06-09  8:25 ` [PATCH 04 of 20] Add APIs for nestedhvm_ops Eddie Dong
2011-07-08  7:42   ` vickywill
2011-07-08  7:43     ` vickywill
2011-06-09  8:25 ` [PATCH 05 of 20] Emulation of guest VMXON/OFF instruction Eddie Dong
2011-06-09  8:25 ` [PATCH 06 of 20] Define structure and access APIs for virtual VMCS Eddie Dong
2011-06-09  8:25 ` [PATCH 07 of 20] Emulation of guest vmptrld Eddie Dong
2011-06-09  8:25 ` [PATCH 08 of 20] Emulation of guest VMPTRST Eddie Dong
2011-06-09  8:25 ` [PATCH 09 of 20] Emulation of guest VMCLEAR Eddie Dong
2011-06-09  8:25 ` [PATCH 10 of 20] Emulation of guest VMWRITE Eddie Dong
2011-06-09  8:25 ` [PATCH 11 of 20] Emulation of guest VMREAD Eddie Dong
2011-06-09  8:25 ` [PATCH 12 of 20] Add APIs to switch n1/n2 VMCS Eddie Dong
2011-06-09  8:25 ` [PATCH 13 of 20] Emulation of VMRESUME/VMLAUNCH Eddie Dong
2011-06-09  8:25 ` [PATCH 14 of 20] Extend VMCS control fields for n2 guest Eddie Dong
2011-06-09  8:25 ` [PATCH 15 of 20] Switch shadow/virtual VMCS between n1/n2 guests Eddie Dong
2011-06-09  8:25 ` [PATCH 16 of 20] interrupt/exception handling for n2 guest Eddie Dong
2011-06-09  8:25 ` [PATCH 17 of 20] VM exit handler of n2-guest Eddie Dong
2011-06-09  8:25 ` [PATCH 18 of 20] Lazy FPU for n2 guest Eddie Dong
2011-06-09  8:25 ` [PATCH 19 of 20] Add VMXE bits in virtual CR4 Eddie Dong
2011-06-09  8:25 ` [PATCH 20 of 20] n2 MSR handling and capability exposure Eddie Dong
2011-06-13  8:27   ` Tim Deegan
2011-06-14  2:29     ` Dong, Eddie
2011-06-15 12:45       ` Tim Deegan
2011-06-20  6:31         ` Jeroen Groenewegen van der Weyden
2011-06-30 14:14           ` Jeroen Groenewegen van der Weyden
2011-07-01  9:01             ` Tim Deegan
2011-07-01  9:54               ` Christoph Egger
2011-07-01 10:11                 ` Jeroen Groenewegen van der Weyden
2011-07-04  8:58                   ` Tim Deegan
2011-07-04  9:58                     ` Jeroen Groenewegen van der Weyden
2011-07-08  7:12                     ` Jeroen Groenewegen van der Weyden
2011-07-18 15:41                       ` Dong, Eddie
2011-07-19 13:59                         ` Jeroen Groenewegen van der Weyden
2011-07-20 13:44                           ` Dong, Eddie
2011-07-20 14:12                             ` Jeroen Groenewegen van der Weyden
2011-07-25 14:08                               ` Tim Deegan
2011-07-25 16:16                                 ` Tim Deegan
2011-07-26  7:15                                   ` Jeroen Groenewegen van der Weyden
2011-07-26 10:00                                     ` Tim Deegan
2011-07-26 10:11                                       ` Tim Deegan
2011-07-26 10:46                                         ` Jeroen Groenewegen van der Weyden
2011-07-26 11:42                                           ` Tim Deegan
2011-07-26 13:33                                             ` Jeroen Groenewegen van der Weyden [this message]
2011-07-26 14:21                                               ` Tim Deegan
2011-07-26 15:25                                                 ` Jeroen Groenewegen van der Weyden
2011-07-26 15:48                                                   ` Tim Deegan
2011-07-26 16:00                                                     ` Jeroen Groenewegen van der Weyden
2011-07-26 16:08                                                       ` Tim Deegan
2011-07-26 11:05                                       ` Jeroen Groenewegen van der Weyden
2011-06-09 10:13 ` [PATCH 00 of 20] Rebased Nested VMX v2 Christoph Egger
2011-06-13  9:24   ` Tim Deegan
2011-06-14  3:01     ` Dong, Eddie
2011-06-14  9:01       ` Tim Deegan
2011-06-14  7:43     ` Christoph Egger
2011-06-14 14:08       ` Dong, Eddie
  -- strict thread matches above, loose matches on Subject: below --
2011-06-02  8:57 [PATCH 00 of 20] NestedVMX support Eddie Dong
2011-06-02  8:57 ` [PATCH 20 of 20] n2 MSR handling and capability exposure Eddie Dong
2011-06-02 15:07   ` Tim Deegan
2011-06-02 15:11     ` Tim Deegan
2011-06-02 19:20       ` Keir Fraser
2011-06-03  8:39       ` Dong, Eddie
2011-06-03  8:25     ` Dong, Eddie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E2EC245.2030905@grosc.com \
    --to=groen692@grosc.com \
    --cc=Christoph.Egger@amd.com \
    --cc=Tim.Deegan@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).