From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH 0/2] Handle xen_platform_pci=0 case Date: Fri, 22 Nov 2013 17:06:58 +0000 Message-ID: <528F8F32.2080508@eu.citrix.com> References: <1385133191-23033-1-git-send-email-anthony.perard@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1385133191-23033-1-git-send-email-anthony.perard@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Anthony PERARD , Xen Devel Cc: Stefano Stabellini , Ian Jackson , Ian Campbell List-Id: xen-devel@lists.xenproject.org On 22/11/13 15:13, Anthony PERARD wrote: > Hi, > > Here is a little series that attempt to fix the issue regarding > xen_platform_pci=0 not been handled. > > There are two patches, the first one adds an option to specifies the QEMU > machine that a user wants and we handle the xen_platform_pci=0 case using the > new option. > > The new options "qemu_machine_override" will help if one want to try a q35 > based device model. Otherwise, it will be used by libxl to switch to the "pc" > machine instead of the "xenfv" one when necessary, as the only difference > between both (since QEMU 1.6) is the presence of the xen-platform pci device. > > Regards, > > Anthony PERARD (2): > libxl: adding support to use -machine option of QEMU. > libxl: Handle xen_platform_pci=0 case with qemu-xen. As I understand it, this is a fix to functionality which should be supported, so doesn't need a freeze exception at this point. -George