From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: FreeBSD image hangs during boot Date: Wed, 10 Oct 2007 15:22:52 +0200 Message-ID: <470CD22C.5050003@qumranet.com> References: <47022E7E.3030509@aurel32.net> <470234DF.6030802@qumranet.com> <470237DC.5060008@aurel32.net> <47027161.50004@qumranet.com> <47027586.9020508@aurel32.net> <47027A01.5080903@aurel32.net> <47027F25.80001@aurel32.net> <470CB4DE.20707@qumranet.com> <470CD1F1.20305@aurel32.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Aurelien Jarno Return-path: In-Reply-To: <470CD1F1.20305-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: > Avi Kivity a =E9crit : > = >> Aurelien Jarno wrote: >> = >>>>> I also confirm that using -no-acpi fixes the problem. However, I have >>>>> seen strange data corruption, even on Intel. >>>>> >>>>> Basically, booting a recently installed FreeBSD leads to the following >>>>> message from the bootloader: "No kernel found". And the next time, I = get >>>>> from the *BIOS*: "Boot from Hard Disk failed: not a bootable disk". >>>>> >>>>> Looking at the disk image, the partition table (and maybe more?) has >>>>> disappeared. This is with a raw image disk. >>>>> >>>>> If I pass either -no-kvm or -no-kvm-irqchip, the problem disappear. >>>>> = >>>>> = >>>> I have just got the problem with -no-kvm-irqchip, though it seems to >>>> happen less often. >>>> = >>>> = >>> The data corruption seems to come from the userspace part, as I am not >>> able to reproduce it with the kvm-45 module, and the kvm-44 userspace. >>> >>> = >>> = >> Does it occur with -no-kvm? >> >> = > > After a few more tests, I have been able to reproduce it with the > current CVS version of QEMU. I conclude this is a QEMU or a BIOS > problem, and not a KVM one. > > Sorry for the noise. > = Well, it still needs to be fixed. I think there's a git import of qemu = available somewhere, that can be used for bisecting. -- = error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/