From: Keir Fraser Subject: Re: [Patch][RFC] BIOS: configure bootable pass-through device Date: Thu, 12 Mar 2009 10:38:13 +0000 Message-ID: References: <49B8DFDA.7040907@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49B8DFDA.7040907@jp.fujitsu.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Akio Takebe , xen-devel Cc: Ian Jackson List-Id: xen-devel@lists.xenproject.org On 12/03/2009 10:11, "Akio Takebe" wrote: > These patches use cmos(0x60) as a place retaining the devfn of bootable > device. > Bochs BIOS doesn't seems to use the offset 0x60. > What do you think of using cmos(0x60)? > Do you have some ideas? This shouldn't need to touch qemu at all. This is a config option that should be parsed by xm/xend and passed directly off to hvmloader. Passing it via hvm_info_table would make most sense in my opinion. In which case you need to probably pass it as an optional param to xc.hvm_build() and poke it into hvm_info_table from that Python C wrapper function. If not specified, should you keep default behaviour and try to load all option ROMs? I'm not fussed - it's just a thought. -- Keir