qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] BeOS R5 boot failure


From: Natalia Portillo
Subject: Re: [Qemu-devel] BeOS R5 boot failure
Date: Tue, 23 Mar 2010 12:56:28 +0000

El 23/03/2010, a las 10:07, François Revol escribió:

I've been trying for some time to get an old BeOS R5 image to boot, but
it seems it doesn't like QEMU's IDE controller:

Trying /dev/disk/ide/ata/0/master/0/raw
IDE PCI -- find_devices: intel 82371SB (PIIX3) chipset
IDE PCI -- find_devices: controller supports DMA
IDE ATA -- configure_device: selected dma mode bad,
                            disable dma for this device
IDE ATA -- get_bios_driveinfo: ata/0/0 match bios drive 0x80
found boot device: /dev/disk/ide/ata/0/master/0/raw
IDE PCI -- find_devices: intel 82371SB (PIIX3) chipset
IDE PCI -- find_devices: controller supports DMA
IDE ATA -- configure_device: selected dma mode bad,
                            disable dma for this device
IDE ATA -- get_bios_driveinfo: ata/0/0 match bios drive 0x80
IDE PCI -- find_devices: intel 82371SB (PIIX3) chipset
IDE PCI -- find_devices: controller supports DMA
IDE ATA -- configure_device: selected dma mode bad,
                            disable dma for this device
IDE ATA -- get_bios_driveinfo: ata/0/0 match bios drive 0x80
warning: fs blocks fa000 larger than device blocks 0
bad super block
KERNEL PANIC: was unable to mount /dev/disk/ide/ata/0/master/0/0_0 type
bfs on /boot


Anyone has a clue ?

It's a known bug but nobody knows or has time to apply a solution.

Bochs had the same bug and corrected it about November 2009, maybe checking their commit will make light to correct QEMU.

It seems VirtualBox has the same issue. Older versions (ZETA) seem to
work fine, but they have a totally different IDE subsystem.

VirtualPC had the same fail also.
Zeta however is not an older version but a newer one.
Considering Zeta is a non-authorized hack, who knows what have they changed.
The bug is present on BeOS R3, R4, R4.5 and R5.

The warning suggest the block device is seen as having a size of 0,
though oddly it seems to be able to read from it since it gets the size
of the BFS in the superblock...

I've rebuilt with DEBUG_IDE and put a log here:
http://revolf.free.fr/beos/qemu-beosr5-bad-ide-20100323.log

Note disabling DMA in the boot menu (space bar, Select safe mode
options) doesn't help either...
Use F1 at boot to get serial output.

The image is available here:
http://bebits.com/app/2680
(BeOS R5 Personal Edition for Linux)

François.







reply via email to

[Prev in Thread] Current Thread [Next in Thread]