From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:36413)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1Sx2IV-0000s1-Dq
	for qemu-devel@nongnu.org; Thu, 02 Aug 2012 16:47:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1Sx2IU-0007Dy-Hp
	for qemu-devel@nongnu.org; Thu, 02 Aug 2012 16:47:07 -0400
Received: from gate.crashing.org ([63.228.1.57]:40656)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1Sx2IU-0007D7-9W
	for qemu-devel@nongnu.org; Thu, 02 Aug 2012 16:47:06 -0400
Message-ID: <1343940385.6911.27.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Fri, 03 Aug 2012 06:46:25 +1000
In-Reply-To: <501A9A07.4040308@redhat.com>
References: <1343873409-8571-1-git-send-email-david@gibson.dropbear.id.au>
	<1343873409-8571-2-git-send-email-david@gibson.dropbear.id.au>
	<87vch2nhn0.fsf@codemonkey.ws> <1343879428.6911.6.camel@pasglop>
	<501A9A07.4040308@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 1/2] Allow QEMUMachine to override reset
	sequencing
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>, agraf@suse.de, Anthony Liguori <anthony@codemonkey.ws>, qemu-devel@nongnu.org

On Thu, 2012-08-02 at 17:17 +0200, Paolo Bonzini wrote:
> 
> On x86 we do not pre-load the kernel.  Neither the kernel/initramfs
> and
> the option ROM that loads the kernel are written in memory, they are
> passed to the guest via fw_cfg.  Then the option ROM is loaded by the
> BIOS, and loads the kernel/initramfs.

How does it do ? IE. how does it access a random pair of files on the
host side ? Via some magic ports ?

Cheers,
Ben.