mirage-console-xen

AuthorsAnil Madhavapeddy and David Scott
LicenseISC
Homepagehttps://github.com/mirage/mirage-console
Issue Trackerhttps://github.com/mirage/mirage-console/issues
Tagsorg:mirage and org:xapi-project
Maintaineranil@recoil.org
Dependencies
&io-page-xen>= 2.0.0
jbuilder>= 1.0+beta9
mirage-console-lwt>= 2.3.5
mirage-console-xen-proto
mirage-xen>= 3.0.2
xen-evtchn
xen-gnt
Availableocaml-version >= "4.03.0"
PublishedJul 15, 2017
Source [http] https://github.com/mirage/mirage-console/releases/download/v2.3.5/mirage-console-2.3.5.tbz
6d0d18cc25fc3e14f070fbb79a24f9ca
StatisticsInstalled 11 times last month.
Edithttps://github.com/ocaml/opam-repository/tree/master/packages/mirage-console-xen/mirage-console-xen.2.3.5/opam

Implementations of Mirage consoles, for Unix and Xen

The Unix version of the console currently uses standard output. The code is in

unix/console.{ml,mli}

The Xen kernel version of the console uses the primary PV console ring. The code is in

xen/console.{ml,mli}

There is also a Unix userspace utility which creates and services Xen consoles ("console backends"):

Connect a console to a VM like this:

[root@st30 ~]# ./mirage-console connect trusty
Operating on VM domain id: 19
Creating device 1 (linux device /dev/tty1)
{ ref = 128; event_channel = 13 }

Then inside the guest:

[root@trusty ~]# cat > /dev/hvc1
hello
there

And observe in dom0:

hello
there

Then hit Control+C and it all cleans up.

No package is dependent