From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Where are vmentry failure caugth? Date: Thu, 10 Jan 2008 17:32:35 +0200 Message-ID: <47863A93.2030707@qumranet.com> References: <20080110111958.7a33661d@frecb000711> <20080110152618.2ca2dd18@frecb000711> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Guillaume Thouvenin Return-path: In-Reply-To: <20080110152618.2ca2dd18@frecb000711> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Guillaume Thouvenin wrote: > On Thu, 10 Jan 2008 11:19:58 +0100 > Guillaume Thouvenin wrote: > > >> I tried but it didn't catch any vmentry failures (and I know that >> there is at least one during the test). >> > > I think that there is a vmentry failure because qemu-system-x86_64 > crashes with following error: > "exception 13 (33)" > > I interpreted this as a vmentry failure because 33 is the exit reason > for a vmentry failure. The problem is that I don't find how to catch it > in kvm. I thought that something like: > I think 33 is the error code, which means we got a general protection fault while accessing segment 0x33. What guest code is running when this happens? The dump sometimes includes the current code. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace