From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Tramnitz Subject: Re: debugging Xen in a serial-less environment Date: Sat, 07 Mar 2009 09:50:25 +0100 Message-ID: References: <49AF9E92.5060207@redhat.com> <49B17A8C.90706@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49B17A8C.90706@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Gerd Hoffmann wrote: > Does the box have AMT? The you can use serial-over-lan. Unfortunately it doesn't. As far as I know only vPro systems have AMT and there is no vPro chipset for Nehalem yet... Jeremy Fitzhardinge wrote: > There's the USB debug port stuff which got added to the kernel a while > ago. Looks like it shouldn't be too hard to graft into Xen. But it seems to be a bit harder to find those dongles. It look like the only model (NET20DC) isn't RoHS compliant which explains why I don't find a place to order them in Eruope. But other than that this seems to be a good long-term alternative to a serial console. I haven't looked at the code for it in the linux kernel but does anyone know if it's required to get all the hcd and usbcore stuff loaded before being able to use the debug port? If not, whats the behaviour of the usb bus (and the debug port) when those drivers are loaded by dom0 subsequently? Best regards, Christian