From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1HyUGW-0006hK-01 for mharc-grub-devel@gnu.org; Wed, 13 Jun 2007 10:56:08 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HyUGU-0006hF-TL for grub-devel@gnu.org; Wed, 13 Jun 2007 10:56:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HyUGS-0006h3-Hy for grub-devel@gnu.org; Wed, 13 Jun 2007 10:56:05 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HyUGS-0006h0-C3 for grub-devel@gnu.org; Wed, 13 Jun 2007 10:56:04 -0400 Received: from pne-smtpout4-sn2.hy.skanova.net ([81.228.8.154]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HyUGR-0000lk-Rc for grub-devel@gnu.org; Wed, 13 Jun 2007 10:56:04 -0400 Received: from [127.0.0.1] (88.193.32.97) by pne-smtpout4-sn2.hy.skanova.net (7.2.075) id 45B621690071C162 for grub-devel@gnu.org; Wed, 13 Jun 2007 16:56:00 +0200 Message-ID: <46700584.1090405@nic.fi> Date: Wed, 13 Jun 2007 17:56:04 +0300 From: =?ISO-8859-1?Q?Vesa_J=E4=E4skel=E4inen?= User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: The development of GRUB 2 References: <8c0c43de0706130533y1dbec4b6ka302af5f8960b2ea@mail.gmail.com> <8c0c43de0706130639n3192ec1ev9a6d2201836f9067@mail.gmail.com> In-Reply-To: <8c0c43de0706130639n3192ec1ev9a6d2201836f9067@mail.gmail.com> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-detected-kernel: Solaris 8 (1) Subject: Re: QEMU and ElTorito and EDD 3 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2007 14:56:07 -0000 Alex Roman wrote: > On 13/06/07, Alex Roman wrote: >> However, it does not support ElTorito extensions... I called the 4D >> function (Return Boot Catalog) and the QEMU BIOS (I think) printed a >> "nice" informative message: >> "FATAL: Int13 eltorito call with AX=4D00. Please report" (see screenshot) > > Furthermore, I wonder... If QEMU doesn't support this, and installing > Windows and other operating systems off CDs works, will many BIOSes > support this interface at all? PHOENIX BIOSes should, IMO, since the > ElTorito standard is made by PHOENIX, but what about the others? > > We might have to read the boot catalog manually, not with the 4Dh > function to achieve more compatibility. Tonight I'll try to do an > "Extended Read", function 42h, to get the boot catalog and parse it in > a structure and see if it "makes sense". > El Torito part of the EDD3 spec might not be accessible if you have not booted with such media that needs that support. At least this seems to be case with VMWare which uses Phoenix BIOS. I once tested out those CD-ROM access API's, but problem is that those devices are not exposed by BIOS when booted from floppy or from HDD. Eg. when you enumerate all devices, CD-ROM drives are not listed at all thus cannot be accessed. But then again... I noticed that your device id was 0xe0 which I think I may have not tried out. I had much better success with directly using ATA :) If you have floppy image, I can try it out in VMWare and tell results what happens.