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

Re: [Xen-devel] Xen dmesg ringbuffer


  • To: Andrew Lyon <andrew.lyon@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 14 Apr 2009 11:07:11 +0100
  • Cc:
  • Delivery-date: Tue, 14 Apr 2009 03:07:35 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acm85/g/yGhh1JYERtmlYQ8PoHPJuQAAM6Fm
  • Thread-topic: [Xen-devel] Xen dmesg ringbuffer

On 14/04/2009 11:00, "Andrew Lyon" <andrew.lyon@xxxxxxxxx> wrote:

> If there is no option to configure the buffer size then at the very
> least should'nt it be set big enough to hold all of the debug info
> that might be output when booting Xen and dom0? once dom0 is running
> the buffer can be written out to a file and cleared.

The iommu code logs large amounts of crap (still, even after I silenced a
lot of it). One way to get the list of advanced features would be do a
single boot of your Supermicro system without iommu=1.

 -- Keir



_______________________________________________
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®.