From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48402) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wrkdw-0000Hj-8r for qemu-devel@nongnu.org; Tue, 03 Jun 2014 05:04:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wrkdp-0000FP-6N for qemu-devel@nongnu.org; Tue, 03 Jun 2014 05:04:28 -0400 Received: from smtp02.citrix.com ([66.165.176.63]:42623) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wrkdp-0000ED-3C for qemu-devel@nongnu.org; Tue, 03 Jun 2014 05:04:21 -0400 Message-ID: <1401786258.8841.42.camel@kazak.uk.xensource.com> From: Ian Campbell Date: Tue, 3 Jun 2014 10:04:18 +0100 In-Reply-To: <538DB300020000660003261A@soto.provo.novell.com> References: <1401333804-15456-1-git-send-email-cyliu@suse.com> <20140530160452.GB3621@localhost.localdomain> <1401722371.30097.5.camel@kazak.uk.xensource.com> <20140602165836.GD5127@phenom.dumpdata.com> <538DB300020000660003261A@soto.provo.novell.com> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Xen-devel] [RFC PATCH 0/2] support xen HVM direct kernel boot List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Chun Yan Liu Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org, Konrad Rzeszutek Wilk On Mon, 2014-06-02 at 21:35 -0600, Chun Yan Liu wrote: > Now I wonder how does it handle device? (A backend file or partition is also a place > on host.) Stubdom uses qemu-xen-traditional, maybe there is some special handling? > Will have a look. The stubdom VM has access to PV Xen devices via its own {blk,net}front etc. When emulating a device it issues the resulting operations via those devices. Ian. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [Xen-devel] [RFC PATCH 0/2] support xen HVM direct kernel boot Date: Tue, 3 Jun 2014 10:04:18 +0100 Message-ID: <1401786258.8841.42.camel@kazak.uk.xensource.com> References: <1401333804-15456-1-git-send-email-cyliu@suse.com> <20140530160452.GB3621@localhost.localdomain> <1401722371.30097.5.camel@kazak.uk.xensource.com> <20140602165836.GD5127@phenom.dumpdata.com> <538DB300020000660003261A@soto.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <538DB300020000660003261A@soto.provo.novell.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Chun Yan Liu Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org, Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Mon, 2014-06-02 at 21:35 -0600, Chun Yan Liu wrote: > Now I wonder how does it handle device? (A backend file or partition is also a place > on host.) Stubdom uses qemu-xen-traditional, maybe there is some special handling? > Will have a look. The stubdom VM has access to PV Xen devices via its own {blk,net}front etc. When emulating a device it issues the resulting operations via those devices. Ian.