From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Anthony Perard <anthony.perard@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: qemu device model question
Date: Tue, 19 May 2015 00:36:49 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1505190034310.2690@kaball.uk.xensource.com> (raw)
In-Reply-To: <1431943233.4944.24.camel@citrix.com>
On Mon, 18 May 2015, Ian Campbell wrote:
> On Mon, 2015-05-18 at 10:49 +0100, George Dunlap wrote:
> > Is there really no way to start up a qdisk process after the domain is
> > created? The qdisk process doesn't actually need to do any emulation,
> > after all -- it's just acting as a backend, right?
>
> FWIW xencommons starts a qemu for dom0 using:
> $QEMU_XEN -xen-domid 0 -xen-attach -name dom0 -nographic -M xenpv -daemonize \
> -monitor /dev/null -serial /dev/null -parallel /dev/null \
> -pidfile $QEMU_PIDFILE
>
> I'd be surprised if this didn't also work for an arbitrary PV domain and
> I assume it wouldn't be needed for an HVM one.
It doesn't work for HVM guests because the QEMU device model also runs a
qdisk backend instance. However it could work for PV/PVH guests.
FYI I am working on a set of patches to remove the handling of PV
backends from QEMU device model. it requires both QEMU and libxl
changes. Once they are in, you'll be able to do this for HVM guests too.
next prev parent reply other threads:[~2015-05-18 23:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 8:54 qemu device model question Juergen Gross
2015-05-13 9:30 ` Ian Campbell
2015-05-13 13:06 ` Wei Liu
2015-05-13 13:26 ` Ian Campbell
2015-05-13 15:43 ` Wei Liu
2015-05-13 14:44 ` Juergen Gross
2015-05-13 15:47 ` Wei Liu
2015-05-18 9:49 ` George Dunlap
2015-05-18 10:00 ` Ian Campbell
2015-05-18 23:36 ` Stefano Stabellini [this message]
2015-05-19 10:08 ` George Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1505190034310.2690@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.