lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4905EE6B.9070000@redhat.com>
Date:	Mon, 27 Oct 2008 18:38:03 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Eric Lacombe <goretux@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [x86] - technical questions about HV implementation on Intel
 VT

Eric Lacombe wrote:
> Hi,
>
> Thanks for your answer.
> I will eventually add a netconsole, but for now, I find how to bypass my 
> problem (getting debug information).
>
> However I come with a new question, related to an unexpected VM-exit.
> The scenario is as follows:
> 1. some setup occur
> 2. vmlaunch is executed by a function F, so the guest is launched. This guest 
> (as I explained in my previous mail) executes the end of the function F.
> 3. The end of F, do some "printk" then return to the module init function.
>
> The problem is that I get a VM-exit during the step 3. In fact after the 
> first "printk", a vm-exit occurs with exit_reason=2 (triple-fault).
>
> Do you have an idea of what could be the cause of this vm-exit?
>   

Almost any emulation error can cause this.  Something goes wrong, an 
exception is raised, can't be handled due to the same problem (or maybe 
another one), triple fault.

You need to print out the entire contents of the vmcs before the last 
entry and check it out carefully.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ