Re: FreeBSD image hangs during boot

Aurelien Jarno
2007-10-02T17:25:57Z

Aurelien Jarno a écrit :
> Aurelien Jarno a écrit :
>> Avi Kivity a écrit :
>>> Aurelien Jarno wrote:
>>>> Avi Kivity a écrit :
>>>>
>>>>> 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?
>> It was working correctly before, up to kvm version 37.
>>
>> 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.

--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org | aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org
`- people.debian.org/~aurel32 | www.aurel32.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.