On Wed, 2015-11-11 at 07:26 -0600, ed sandberg wrote:
> > So does it still not work if you add a getty onto "hvc0" instead of
> > "ttySA2"?
>
> Correct, adding getty to hvc0 also does not work.
And you are either using udev or have otherwise arranged for /dev/hvc0 to
exist?
Looking back at your
> So does it still not work if you add a getty onto "hvc0" instead of
> "ttySA2"?
Correct, adding getty to hvc0 also does not work.
Ed
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On Fri, 2015-11-06 at 12:51 -0600, ed sandberg wrote:
> > Does your kernel have the Xen drivers (CONFIG_XEN and all which is
> > gated on that) enabled. In particular CONFIG_HVC_XEN.
> >
> Yes the config file I used to compile has CONFIG_XEN=y and
> CONFIG_HVC_XEN=y. Config file is attached.
Tha
> Does your kernel have the Xen drivers (CONFIG_XEN and all which is
> gated on that) enabled. In particular CONFIG_HVC_XEN.
>
Yes the config file I used to compile has CONFIG_XEN=y and
CONFIG_HVC_XEN=y. Config file is attached.
#
# Automatically generated file; DO NOT EDIT.
# Linux/arm 4.3.0-rc
On Fri, 2015-11-06 at 08:38 -0600, ed sandberg wrote:
Please don't top post.
> Thanks for the help Ian,
> # setenv xen_bootargs 'console=dtuart dtuart=/serial@12C2
> dom0_mem=512M'
> # setenv dom0_bootargs 'console=hvc0 console=ttySAC2,115200n8
> ignore_loglevel psci=enable clk_ignore_unused
Thanks for the help Ian,
I tried using ttySAC2 in /etc/init/ttySAC2.conf but I still am not
prompted to login on the serial output. I also tried creating
/etc/init/ttyhvc0.conf. I think that is the correct place to start
getty from. There are other similar files in that location and this page:
On Thu, 2015-11-05 at 12:59 -0600, ed sandberg wrote:
>
> My initial thought was that I needed to add a getty process on COM3, so
> that when I switched to Dom0 mode I could login. This page seems to
> agree with me:
>
> http://wiki.xenproject.org/wiki/Xen_Serial_Console
>
> I tried to do so b
I am trying to get xen running on an arndale Exynos5250. I think I am
close to success because I can boot the hypervisor and interact with the
debug console and I don't see any errors. I can switch the debug
console from xen mode to Dom0 mode by pressing CTRL-a three times,
however I am not promp
