From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Shelton Subject: Re: QEMU 2.2.0 in Xen 4.6 Date: Fri, 23 Jan 2015 11:37:33 -0500 Message-ID: References: <1422024910.19859.82.camel@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3632222026615998996==" Return-path: 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: Stefano Stabellini Cc: xen-devel@lists.xensource.com, Ian Campbell List-Id: xen-devel@lists.xenproject.org --===============3632222026615998996== Content-Type: multipart/alternative; boundary=047d7b33dd74d08edc050d5467bd --047d7b33dd74d08edc050d5467bd Content-Type: text/plain; charset=ISO-8859-1 On Jan 23, 2015 10:10 AM, "Stefano Stabellini" < stefano.stabellini@eu.citrix.com> wrote: > > On Fri, 23 Jan 2015, Ian Campbell wrote: > > On Fri, 2015-01-23 at 14:42 +0000, Stefano Stabellini wrote: > > > > > HVM guest ---------(PV)----------> QEMU in Dom0 for guest > > > | > > > --(emulation)--> QEMU Stubdom-(syscall)->Linux Stubdom---(PV)--> QEMU Dom0 for stubdom > > > > Here, and throughout what you said I think, "QEMU in Dom0 for guest" > > could equally well be e.g. "blkback in driver domain for guest" likewise > > the "... for stubdom" too. > > > > i.e. the PV backend for the stubdom or the guest doesn't necessarily > > need to be QEMU and doesn't necessarily need to be in dom0. > > Indeed > Thank you both. There is one other thing that would be helpful to understand. Anthony had to patch the Linux kernel running in the stubdom to allow memory mapping. What mappings are needed between dom0 and the stub domain, and between the stub domain and the HVM guest domain? I am guessing this comes into play for the display, as it seems that the dom0 qemu instance is running the VNC server. Thanks again, Eric --047d7b33dd74d08edc050d5467bd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Jan 23, 2015 10:10 AM, "Stefano Stabellini" <= ;stefano.stabellini@eu.= citrix.com> wrote:
>
> On Fri, 23 Jan 2015, Ian Campbell wrote:
> > On Fri, 2015-01-23 at 14:42 +0000, Stefano Stabellini wrote:
> >
> > > HVM guest ---------(PV)----------> QEMU in Dom0 for guest=
> > >=A0 =A0 =A0|
> > >=A0 =A0 =A0--(emulation)--> QEMU Stubdom-(syscall)->Lin= ux Stubdom---(PV)--> QEMU Dom0 for stubdom
> >
> > Here, and throughout what you said I think, "QEMU in Dom0 fo= r guest"
> > could equally well be e.g. "blkback in driver domain for gue= st" likewise
> > the "... for stubdom" too.
> >
> > i.e. the PV backend for the stubdom or the guest doesn't nece= ssarily
> > need to be QEMU and doesn't necessarily need to be in dom0. >
> Indeed
>

Thank you both.

There is one other thing that would be helpful to understand= .=A0 Anthony had to patch the Linux kernel running in the stubdom to allow = memory mapping.=A0 What mappings are needed between dom0 and the stub domai= n, and between the stub domain and the HVM guest domain?=A0 I am guessing t= his comes into play for the display, as it seems that the dom0 qemu instanc= e is running the VNC server.

Thanks again,
Eric

--047d7b33dd74d08edc050d5467bd-- --===============3632222026615998996== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============3632222026615998996==--