From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ml71V-0003ov-3u for qemu-devel@nongnu.org; Tue, 08 Sep 2009 16:10:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ml71Q-0003nV-6e for qemu-devel@nongnu.org; Tue, 08 Sep 2009 16:10:40 -0400 Received: from [199.232.76.173] (port=48878 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ml71Q-0003nP-0d for qemu-devel@nongnu.org; Tue, 08 Sep 2009 16:10:36 -0400 Received: from mail-qy0-f172.google.com ([209.85.221.172]:51630) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ml71P-0007Vj-I0 for qemu-devel@nongnu.org; Tue, 08 Sep 2009 16:10:35 -0400 Received: by qyk2 with SMTP id 2so3139523qyk.21 for ; Tue, 08 Sep 2009 13:10:35 -0700 (PDT) Message-ID: <4AA6BA39.4080600@codemonkey.ws> Date: Tue, 08 Sep 2009 15:10:33 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 0/2] port over extboot from kvm References: <1252401463-3249-1-git-send-email-kraxel@redhat.com> <4AA6607C.4050505@siemens.com> <4AA668A2.1080801@redhat.com> <4AA66B10.2050901@codemonkey.ws> <4AA680BB.5020201@redhat.com> <4AA692A0.1070006@codemonkey.ws> <4AA6AC56.5020700@redhat.com> <4AA6B499.5060103@codemonkey.ws> <4AA6B7E2.40703@redhat.com> In-Reply-To: <4AA6B7E2.40703@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Jan Kiszka , Gerd Hoffmann , qemu-devel@nongnu.org Avi Kivity wrote: >> In fact, when you chain-load with grub, you often have to "swap" >> device mappings which has the effect of hooking int13 and faking the >> primary drive for another OS. See >> http://www.gnu.org/software/grub/manual/html_node/DOS_002fWindows.html > > But grub still has to issue a real int 13 for drive 0x81. If we don't > expose it, it can't. Until a real OS is loaded, the only way to > access a drive is through int 13 and if we don't expose it, it's > invisible. extboot ignores any non-0x80 access today FWIW so this is already broken. Only 0x80 is generally bootable. This means even on modern systems, you still have per-adapter config menus that allow the user to configure which drive ends up getting 0x80. It's awfully messy and not worth exposing to users. >> All else aside, from a BIOS perspective, you can usually only boot >> from 0x80 and that can be mapped to different drives via BCV. > > There things you can do with a drive other than boot it. For example, > access it via int 13. > > How will you access D:\ from DOS? Let the user specify BCV priority, let the BIOS determine how to assign drive numbering. It may turn out that bios drive number isn't stable but this is also true on real machines. Regards, Anthony Liguori