From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olivier LAMBERT <lambert.olivier@gmail.com>
Subject: SVM violation gpa, CPU problem ?
Date: Tue, 13 Jul 2010 11:16:58 +0200
Message-ID: <AANLkTimuzq8DH2efSYDNSUk4kRRS1MvBgEGbm5ZTfaTu@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Return-path: <xen-users-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>,
	<mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-users@lists.xensource.com>
List-Help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>,
	<mailto:xen-users-request@lists.xensource.com?subject=subscribe>
Sender: xen-users-bounces@lists.xensource.com
Errors-To: xen-users-bounces@lists.xensource.com
To: Xen User-List <xen-users@lists.xensource.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Hello,

I'm running Xen 3.4.2 on Debien Lenny, with a kernel 2.6.27 for Dom0.
xen_major              : 3
xen_minor              : 4
xen_extra              : .2
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64


Last month, it works like a charm. But when I returned one month
after, all HVM windows hosts (just 2 Windows 2008 64 bits ;) ) went
down.

I don't understand why it works first and then it crashes.

Here is some valuable informations :
hardware : Dell PowerEdge with Six-Core AMD Opteron(tm) Processor 2423 HE.
Hardware virt is enabled.

# xm dmesg | grep SVM
(XEN) AMD SVM: ASIDs enabled.
(XEN) HVM: SVM enabled
(XEN) AMD SVM: ASIDs enabled.

But each time I tried to start a HVM windows domain, a new line
appears in "xm dmesg | grep SVM" :
(XEN) svm.c:924:d1 SVM violation gpa 0x00000000400004, mfn 0x64e200, type 1

And here is xend.log :

[2010-07-13 10:52:28 4198] DEBUG (DevController:139) Waiting for devices vtpm.
[2010-07-13 10:52:28 4198] WARNING (XendDomainInfo:1886) Domain has
crashed: name=winpv id=1.
[2010-07-13 10:52:28 4198] ERROR (XendDomainInfo:2020) VM winpv
restarting too fast (Elapsed time: 0.814288 seconds). Refusing to
restart to avoid loops.
[2010-07-13 10:52:28 4198] DEBUG (XendDomainInfo:2732)
XendDomainInfo.destroy: domid=1
[2010-07-13 10:52:29 4198] DEBUG (XendDomainInfo:2207) Destroying device model
[2010-07-13 10:52:29 4198] INFO (image:556) winpv device model terminated
[2010-07-13 10:52:29 4198] DEBUG (XendDomainInfo:2214) Releasing devices


So, it can't boot, and obviously there is a link between SVM
instructions and this "bug".

No problem with PV Linux Guests.

And more : same problem on the other server, which is the same Dell
Poweredge (same CPU).

The strange thing is that it appears suddenly, before my windows PV
guests works perfectly (good perfs etc.)

I hope to find a solution....


Regards,


Olivier.