From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?windows-1252?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com>
Subject: Re: xen4.5 dom0pvh test failed
Date: Thu, 29 Jan 2015 16:36:02 +0100
Message-ID: <54CA5362.5070902@citrix.com>
References: <47498F109986134D9A5B42B82F405EBB7EDE5833@SZXEMA502-MBX.china.huawei.com>
	<54C7488A.3040608@citrix.com>
	<47498F109986134D9A5B42B82F405EBB7EDE6991@SZXEMA502-MBX.china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <47498F109986134D9A5B42B82F405EBB7EDE6991@SZXEMA502-MBX.china.huawei.com>
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: "Yuzhou (C)" <vitas.yuzhou@huawei.com>
Cc: "Zhangleiqiang (Trump)" <zhangleiqiang@huawei.com>, "Xiaoding (B)" <xiaoding1@huawei.com>, "Luohao (brian)" <brian.luohao@huawei.com>, Zhuangyuxin <zhuangyuxin@huawei.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

Hello,

El 29/01/15 a les 13.44, Yuzhou (C) ha escrit:
> Hi Roger,
> 
>> Yes, I've successfully tested Xen 4.5.0 and Linux 3.18.0.
> 
> 
>      Did you do any patch? 

Well, as said before PVH Dom0 is still very experimental. I usually find
issues as I test it on different hardware. Right now I've successfully
tested it on a Dell Precision T3500 with a Xeon W3550 and a Dell
PowerEdge R310 with a Xeon X3450, without any additional patches.

It would be quite good if you can follow the steps requested by Jan in a
previous email and try to find the root cause of your issue. Without
this I'm afraid that you will have to wait for someone to stumble upon
the same issue and fix it.

Roger.