From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Xen on Seattle Date: Wed, 10 Sep 2014 16:00:35 -0700 Message-ID: <5410D813.6050004@linaro.org> References: <54055D24.60406@amd.com> <5406080B.5030109@amd.com> <54060D1B.1000400@amd.com> <5410D2EB.10601@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5410D2EB.10601@amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Suravee Suthikulanit , Stefano Stabellini Cc: Joel Schopp , "Hurwitz, Sherry" , Stefano Stabellini , Ian Campbell , xen-devel List-Id: xen-devel@lists.xenproject.org Hi Suravee, On 10/09/14 15:38, Suravee Suthikulanit wrote: > ..... > (XEN) DOM0: NET: Registered protocol family 10 > (XEN) DOM0: sit: IPv6 over IPv4 tunneling driver > (XEN) DOM0: NET: Registered protocol family 17 > (XEN) DOM0: Bridge firewalling registered > (XEN) DOM0: 9pnet: Installing 9P2000 support > (XEN) DOM0: NET: Registered protocol family 37 > (XEN) DOM0: bootconsole [uart0] disabled > > Please see attachment for full boot log. I am still working on trying to > get to Dom0 console. Xen is providing a tiny UART emulation which only handle write. It looks like you kernel is using it. Did add "console=hvc0" on your kernel command line? This will allow DOM0 to use the paravirtualised console. Regards, -- Julien Grall