From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: 32-bit FreeBSD under 64-bit KVM Date: Tue, 27 Feb 2007 09:08:50 +0200 Message-ID: <45E3D902.7000102@qumranet.com> References: <45E38511.9000006@aurel32.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Aurelien Jarno Return-path: In-Reply-To: <45E38511.9000006-rXXEIb44qovR7s880joybQ@public.gmane.org> 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 Aurelien Jarno wrote: > Hi all, > > While I am able to run a 64-bit FreeBSD under a 64-bit KVM perfectly, I > am having problems with running a 32-bit FreeBSD under the same KVM: > > INIT: version 2.86 booting > INIT: PANIC: segmentation violation! sleeping for 30 seconds. > pid 34 (init), uid 0: exited on signal 11 > INIT: PANIC: segmentation violation! sleeping for 30 seconds. > INIT: PANIC: segmentation violation! sleeping for 30 seconds. > INIT: PANIC: segmentation violation! sleeping for 30 seconds. > INIT: PANIC: segmentation violation! sleeping for 30 seconds. > INIT: PANIC: segmentation violation! sleeping for 30 seconds. > INIT: PANIC: segmentation violation! sleeping for 30 seconds. > INIT: PANIC: segmentation violation! sleeping for 30 seconds. > > Basically the kernel boots correctly, but then the userland fails to > work. I am using KVM-15 on an AMD64 CPU. > > I am able to run the same OS with -no-kvm, also I am able to run a > 32-bit Linux under a 64-bit KVM. It seems the 32-bit support is at least > not totally broken, though I haven't made extensive tests. > > Does somebody is experiencing the same problems? Do you have a solution? > > Can you try turning the '#undef AUDIT' to '#define AUDIT' in mmu.c? Also, change 'int dbg = 1' to 'int dbg = 0' in the same file. Note kvm will be very slower after this. dmesg will show any issues (issue a 'echo 9 > /proc/sysrq-trigger' to make sure all messages are shown) -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV