This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] disable qemu PCI devices in HVM domains

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, Steven Smith <steven.smith@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] disable qemu PCI devices in HVM domains
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 17 Dec 2008 08:27:27 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Wed, 17 Dec 2008 00:27:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0154FFFF@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acle2DIWYJ2mwybHShGrV6zzIswFwABILgmgAAoYQ2M=
Thread-topic: [Xen-devel] disable qemu PCI devices in HVM domains
User-agent: Microsoft-Entourage/
On 17/12/2008 03:47, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

>>> I'm not sure if the approach taken by the Citrix drivers could be at
> all
>>> useful. Cc'ing Steven Smith in case he has any comments to make.
>> I can't see any reason why the approach we take in our closed-source
>> drivers wouldn't work here as well.  I've attached the appropriate
>> patches from our product qemu patchqueue, tidied up and stripped of
>> the most obviously XenServer-specific bits, and made to apply to
>> current ioemu-remote.
> 3.3.1 is feature frozen at this point isn't it, which means 3.3.2 for
> these patches right?

I'm reluctant to introduce anything into a stable branch which would prevent
us migrating domains up or down the branch. If we are going to shove it in,
it should happen now, for 3.3.1. My .1 releases tend to be generously
proportioned, but beyond a .1 release I definitely don't take anything other
than pure bug fixes.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>