From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: FreeBSD image hangs during boot Date: Tue, 02 Oct 2007 18:27:13 +0200 Message-ID: <47027161.50004@qumranet.com> References: <47022E7E.3030509@aurel32.net> <470234DF.6030802@qumranet.com> <470237DC.5060008@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: <470237DC.5060008-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: >> = >>> Hi all, >>> >>> That's not something new, but I never seen the problem mentioned here. >>> FreeBSD does not work on KVM, approximately since the lapic merge. >>> >>> However, that does not seem related to lapic, as using -no-kvm-irqchip >>> does not help. With -no-kvm I get a page fault in kernel mode, while the >>> normal QEMU (0.9.0 or CVS) does not have this problem. >>> >>> This can be easily reproduced with the latest installation CD: >>> ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.2/6.2-RELEASE-i386-= bootonly.iso >>> >>> = >>> = >> It complains about the RSDT checksum. Running with -no-acpi works = >> around the problem (it gets to some country selection screen). So it = >> looks like the ACPI tables are messed up. >> = > > The RSDT checksum problem is not new, but it was harmless on previous > versions (like kvm-37). > > Using -no-acpi, I am able to boot the machine with -no-kvm, but the > guest still hang with -no-acpi and with -no-kvm-irqchip or lapic > enabled. At least on AMD64, I haven't tested yet on an Intel machine. > > = Looks like there is a compiler problem that's interfering here. A bios = compiled on one machine will boot fine on Intel, but on other machines = (unfortunately my work machines) will not. There is a separate issue with -no-acpi on AMD. Is there some version = where -no-acpi worked on AMD? -- = error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/