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

[Pasi Kärkkäinen <pasik@xxxxxx>]

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):

grub.conf:

# 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 
console=tty0

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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel