From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: qemu-xen-dir + PCI passthrough = BOOM Date: Tue, 31 Dec 2013 10:30:31 -0500 Message-ID: <20131231153031.GA20357@phenom.dumpdata.com> References: <20131206144935.GA3603@pegasus.dumpdata.com> <20131206153503.GS10855@perard.uk.xensource.com> <20131206160018.GC4419@zion.uk.xensource.com> <20131206160310.GD4419@zion.uk.xensource.com> <20131216150816.GA14122@phenom.dumpdata.com> <20131218144823.GB6081@perard.uk.xensource.com> <1387378646.28680.48.camel@kazak.uk.xensource.com> <20131218152235.GG4934@phenom.dumpdata.com> <1387383185.28680.60.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vy1HF-0006Zq-4s for xen-devel@lists.xenproject.org; Tue, 31 Dec 2013 15:30:41 +0000 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Wu, Feng" Cc: Anthony PERARD , "xen-devel@lists.xenproject.org" , "stefano.stabellini@citrix.com" , Ian Campbell List-Id: xen-devel@lists.xenproject.org On Sun, Dec 22, 2013 at 11:25:20AM +0000, Wu, Feng wrote: > > > > -----Original Message----- > > From: xen-devel-bounces@lists.xen.org > > [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of Ian Campbell > > Sent: Thursday, December 19, 2013 12:13 AM > > To: Konrad Rzeszutek Wilk > > Cc: Anthony PERARD; xen-devel@lists.xenproject.org; > > stefano.stabellini@citrix.com > > Subject: Re: [Xen-devel] qemu-xen-dir + PCI passthrough = BOOM > > > > On Wed, 2013-12-18 at 10:22 -0500, Konrad Rzeszutek Wilk wrote: > > > load_roms and bios_load are not set - so it wouldn't even do it. > > > It only does it for Bochs BIOS. > > > > Right, this is deliberate. > > > > For ROMBIOS (AKA BOchs BIOS) hvmloader loads the options roms. and I > > think ROMBIOS subsequently loads them. > > > > For SeaBIOS it is the BIOS itself which both loads and executes the > > ROMS, which is why it is NULL in hvmloader. > > > > The SeaBIOS way is far more like how systems normally work and because > > the BIOS is in charge it can do a better job than splitting it between > > two entities. > > > > I am also interested in this thread. Do you know why ROMBIOS doesn't handle > option ROM the same way as seaBIOS? Is there any special case that ROMBIOS > cannot handle? Thanks! When I find out I will make sure to notify you as well. Thanks!