From: Julien Grall <julien.grall@linaro.org>
To: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Joel Schopp <joel.schopp@amd.com>,
"Hurwitz, Sherry" <sherry.hurwitz@amd.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen on Seattle
Date: Wed, 10 Sep 2014 16:00:35 -0700 [thread overview]
Message-ID: <5410D813.6050004@linaro.org> (raw)
In-Reply-To: <5410D2EB.10601@amd.com>
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
next prev parent reply other threads:[~2014-09-10 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 6:01 Xen on Seattle Suravee Suthikulanit
2014-09-02 18:06 ` Stefano Stabellini
2014-09-02 18:10 ` Suravee Suthikulanit
2014-09-02 18:15 ` Stefano Stabellini
2014-09-02 18:31 ` Suravee Suthikulanit
2014-09-02 18:33 ` Stefano Stabellini
2014-09-10 22:38 ` Suravee Suthikulanit
2014-09-10 23:00 ` Julien Grall [this message]
2014-09-11 0:36 ` Suravee Suthikulanit
2014-09-11 1:24 ` Stefano Stabellini
2014-09-03 9:51 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5410D813.6050004@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=joel.schopp@amd.com \
--cc=sherry.hurwitz@amd.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).