From xen-devel-bounces@lists.xen.org Wed Sep 18 16:47:14 2013 Received: (at maildrop) by bugs.xenproject.org; 18 Sep 2013 15:47:14 +0000 Received: from lists.xen.org ([50.57.142.19]) by bugs.xenproject.org with esmtp (Exim 4.80) (envelope-from ) id 1VMJyE-0001nh-OK for xen-devel-maildrop-Eithu9ie@bugs.xenproject.org; Wed, 18 Sep 2013 16:47:14 +0100 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VMJvm-0007I6-FR; Wed, 18 Sep 2013 15:44:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VMJvl-0007Hs-EU for xen-devel@lists.xenproject.org; Wed, 18 Sep 2013 15:44:41 +0000 Received: from [85.158.143.35:9803] by server-2.bemta-4.messagelabs.com id 4E/69-26052-86AC9325; Wed, 18 Sep 2013 15:44:40 +0000 X-Env-Sender: JBeulich@suse.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1379518539!32324!1 X-Originating-IP: [130.57.49.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMwLjU3LjQ5LjI4ID0+IDQ4MDU=\n X-StarScan-Received: X-StarScan-Version: 6.9.12; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14502 invoked from network); 18 Sep 2013 15:35:40 -0000 Received: from nat28.tlf.novell.com (HELO nat28.tlf.novell.com) (130.57.49.28) by server-9.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2013 15:35:40 -0000 Received: from EMEA1-MTA by nat28.tlf.novell.com with Novell_GroupWise; Wed, 18 Sep 2013 16:35:38 +0100 Message-Id: <5239E46802000078000F4764@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.2 Date: Wed, 18 Sep 2013 16:35:36 +0100 From: "Jan Beulich" To: "Fabio Fantoni" References: <52397B4C02000078000F43F7@nat28.tlf.novell.com> <52399CA2.6030701@m2r.biz> <5239BBBB02000078000F4565@nat28.tlf.novell.com> <5239B4B9.8000604@m2r.biz> <5239D52602000078000F46B7@nat28.tlf.novell.com> <5239C616.8000507@m2r.biz> In-Reply-To: <5239C616.8000507@m2r.biz> Mime-Version: 1.0 Content-Disposition: inline Cc: George Dunlap , Andrew Cooper , "qemu-devel@nongnu.org" , Keir Fraser , Anthony PERARD , xen-devel Subject: Re: [Xen-devel] [PATCH] libxl: Remove qxl support for the 4.3 release X-BeenThere: xen-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org >>> On 18.09.13 at 17:26, Fabio Fantoni wrote: > Il 18/09/2013 16:30, Jan Beulich ha scritto: >>>>> On 18.09.13 at 16:12, Fabio Fantoni wrote: >>> Il 18/09/2013 14:42, Jan Beulich ha scritto: >>>>>>> On 18.09.13 at 14:29, Fabio Fantoni wrote: >>>>> I not see the MMIO error on logs, what must I do to see it or any >>>>> similar debug information? >>>>> Tell me if I must do other specific test or you need other details. >>>> Without the patch you ought to have seen "bad mmio size ..." >>> I was unable to see the MMIO error on each log files also before the patch. >>> I don't know if I have enable sufficent debug to log them. >>> And I have no ideaon how to do it. >> This is a guest warning (from log level perspective), so by default >> would be visible in a rate limited fashion. If you want to be certain, >> just add "loglvl=all guest_loglvl=all". But I'm more and more >> convinced that the information we got from you originally was >> misleading. > > On grub.cfg now I have: > ... > multiboot /boot/xen.gz placeholder dom0_mem=4G,max:4G loglvl=all > guest_loglvl=all > ... > But I'm unable to see debug related information in log files. Log files? There can be a pertinent log file only if you have some daemon running transferring the hypervisor log into a log file. Otherwise you need to look at "xl dmesg" output. > This was the test of Anthony Perard with all details about the problem: > http://lists.xen.org/archives/html/xen-devel/2013-05/msg02050.html See the "bad mmio size 16" and "MMIO emulation failed @ ..." messages there? > So my questions are: > - Is your patch aimed to completely solve cpus instrictions with MMIO > operands > 8 byte or > - does it need also some qemu changes? The patch is aiming at completely solving the in-hypervisor emulation issues with operands of more than 8 bytes in size. Whether on top of that a qemu change is also necessary I don't know, but I wouldn't have expected so. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel