From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [x86] - technical questions about HV implementation on Intel VT Date: Mon, 20 Apr 2009 21:22:21 +0300 Message-ID: <49ECBD5D.4080205@redhat.com> References: <200903241822.11529.goretux@gmail.com> <200904071926.30643.goretux@gmail.com> <200904141424.01608.goretux@gmail.com> <200904201953.53815.goretux@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Eric Lacombe Return-path: Received: from mx2.redhat.com ([66.187.237.31]:57433 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753985AbZDTSWa (ORCPT ); Mon, 20 Apr 2009 14:22:30 -0400 In-Reply-To: <200904201953.53815.goretux@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: Eric Lacombe wrote: > Hi, > > I reviewed my code (modify some things and add missing features) and made more > tests, but I'm stuck with the same problem. > Nonetheless, all the tests I've done seem to freeze my machine when files are > used. > > When I try the commands "echo", "pwd" in the console (X is not started), the > machine behaves nicely. When I try completion (with double-tab) on a command, > it also works. But, when I try for instance "more help.c", the machine > freezes, likewise when I try "more hel"+double-tab. > echo and pwd are part of bash, so they are probably in memory. I guess once you go to disk things fail. Try to boot the entire OS from initramfs (and keep it there). > I really would appreciate some help on this. > This is much to complicated for drive-by debugging. > Please, could you tell me what I could check (because I already checked a lot > of things and can't figure out what happens)? I would also give you all the > information you need. > > (Recall: When loaded, my module use VT-x to go on vmx root operation, then it > creates a vmcs in order to execute the OS inside a VM.) > I imagine you have interrupts working properly? Does 'watch -d cat /proc/interrupts' give the expected results (run it before you enter vmx to load it into cache)? Are you virtualizing memory, or does the guest manipulate page tables directly? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.