This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB

To: Ross Philipson <Ross.Philipson@xxxxxxxxxx>
Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 27 Apr 2009 22:01:42 +0300
Cc: Tim Kaufmann <tk@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 27 Apr 2009 12:02:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <831D55AF5A11D64C9B4B43F59EEBF72035FCB54140@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <28109258-1B1E-48F9-936B-9AFC04866C11@xxxxxxxxxx> <831D55AF5A11D64C9B4B43F59EEBF72035FCB540D2@xxxxxxxxxxxxxxxxxxxxxxxxx> <F126C20F-9063-4FCC-BF8F-FE4CCDBCF1E5@xxxxxxxxxx> <831D55AF5A11D64C9B4B43F59EEBF72035FCB540E5@xxxxxxxxxxxxxxxxxxxxxxxxx> <21F81074-ADE6-4913-A77E-4615F84E5CB9@xxxxxxxxxx> <831D55AF5A11D64C9B4B43F59EEBF72035FCB540F1@xxxxxxxxxxxxxxxxxxxxxxxxx> <4343D05F-0C26-4319-BA8A-0EC9C65DA77A@xxxxxxxxxx> <831D55AF5A11D64C9B4B43F59EEBF72035FCB5412D@xxxxxxxxxxxxxxxxxxxxxxxxx> <4844FE6B-C07D-4D02-A342-65A70D4B36EA@xxxxxxxxxx> <831D55AF5A11D64C9B4B43F59EEBF72035FCB54140@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Mon, Apr 27, 2009 at 02:39:40PM -0400, Ross Philipson wrote:
> So using com4, you will need something like this:
>         xen.gz console=com4 com4=115200,8n1,0xe1c0,0
> Note that 0xe1c0 is the IO port for the KT Controller below. Give that a 
> shot. I am interested to see if this works since this would be a useful 
> method of debugging.

This is my DQ35JO configuration for AMT/SOL remote console (that server is NOT 
running Xen though):


# Intel AMT serial-over-lan console
serial --port=0x3440 --speed=115200
terminal --timeout=10 console serial

kernel /vmlinuz-2.6.18-128.1.6.el5 ro root=.. console=ttyS1,115200n8 

0x3440 is the IOport for AMT serial port from lspci.
Linux detects DQ35JO AMT serial port as ttyS1.

Then I connect to the serial console from a Linux desktop using "gamt" tool.
Hopefully that helps.

-- Pasi

> Thanks
> Ross
> -----Original Message-----
> From: Tim Kaufmann [mailto:tk@xxxxxxxxxx]
> Sent: Monday, April 27, 2009 2:31 PM
> To: Ross Philipson
> Cc: xen-devel
> Subject: Re: [Xen-devel] No VT-d with Xen 3.3/3.4rc3 on Intel-Board DQ45CB
> > connect the tools.
> Done.
> > Then you can setup the xen command line to do serial tracing - try
> > it first with COM4.
> A hint on how to *properly* set this up would be very welcome.
> > Also can you send a more verbose lspci trace (lspci -vv e.g.)?
> Attached.
> Tim

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>