[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] We still have to disable vtd for old chipset?


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Neo Jia" <neojia@xxxxxxxxx>
  • Date: Mon, 2 Jun 2008 18:00:33 -0700
  • Delivery-date: Mon, 02 Jun 2008 18:00:55 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=uXtTNu5vYxfor3qz7vSHwHT6d3qjfB94J3FfDbgiAIfQ4zeesrhEU6H00a9f/+C7oYsdAnRXJpen/IAbqD/S8ofhBv9AHgUuZFmKqQrEuAVlYZIaJuIN1DOFVwHDmddDhMusNlaPx9NTVTsuA4SOpFUlfRnoKEPzTvU2WqsHWWM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I am seeing the following error message in xm dmesg.

(XEN) [VT-D]utils.c:59: *** VT-d disabled - pre C0-step Seaburg found
(XEN) [VT-D]utils.c:62: ***  vendor = 8086 device = 4000 revision = 10

This is on Dell T7400. And the change is
http://lists.xensource.com/archives/html/xen-changelog/2007-09/msg00284.html.

So, I am wondering if there is any fix for this?

Thanks,
Neo
-- 
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.