From mboxrd@z Thu Jan  1 00:00:00 1970
From: Juergen Gross <jgross@suse.com>
Subject: qemu device model question
Date: Wed, 13 May 2015 10:54:26 +0200
Message-ID: <55531142.6040304@suse.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Hi,

while trying to build a pvusb backend in qemu I think I've found a
general issue in xl: qemu for pv-domains is started only at domain
creation and only if there is at least one backend in qemu required.

If there is no qemu process started for the domain at creation time
it will be impossible to successfully add such a device later while
the domain is running.

Are there any plans to remove that restriction? Or have I missed
some mechanism in xl to start qemu at a later time?

Related to this problem is the question whether it would be desirable
to have e.g. qdisk and pvusb backends in the same process possibly
influencing each others throughput.

Any thoughts?


Juergen