Lines Matching refs:to
7 Xen traditionally provided a single pv console to pv guests, storing the
15 This document tries to describe how the whole system works and how the
26 The vuart console provides access to a virtual SBSA UART on ARM systems.
27 To enable vuart the following line has to be added to the guest configuration
42 * 'connection' information describing to what they should be
46 We call a PV console with a name a "channel", in reference to the libvirt
48 how to use channels and includes a registry of well-known channel names.
51 is written to the frontend directory:
61 * path: only present if connection = 'socket', the path of the socket to
62 glue the channel to
68 If the toolstack wants the console to be connected to a pty, it will write
69 to the backend:
74 The backend will write the pty device name to the "tty" node in the
85 If the toolstack wants a listening Unix domain socket to be created at path
86 <path>, a connection accepted and data proxied to the console, it will write:
104 console and it can only connect to a pty.
106 Emulated serials are provided by qemu-dm only to hvm guests; the number
108 are given to qemu. The output of a serial is specified as argument to
109 the -serial command line option to qemu. Qemu writes the tty name to
114 xenconsole is the tool to connect to a PV or virtual UART console or an
120 specify the console type xenconsole will try to guess: if the guest is a pv
121 guest it defaults to PV console, if the guest is an hvm guest it defaults to
126 Considering that xenconsole defaults to emulated serials for hvm guests,
127 executing xl create -c "domain" causes xenconsole to attach to the
129 currently no bootloaders support xen pv consoles so the only way to
130 interact with a bootloader like grub over a console is to use the
132 However the pv console is still easy to use with Linux PV on HVM guests:
133 the user just need to pass "console=hvc0" to the kernel command line and
134 then execute "xl console -t pv <domain>" to connect to it.
140 console connection between the stubdom and dom0 to export the serial
141 output from the stubdom to dom0. The pv console backend for stubdom's pv
144 too. In order to simplify the setup when using stubdoms the hvm guest
146 could provide pv console backends to the hvm guest but then it would
147 need another pv console connection for each console backend to export
148 the pty to dom0).
150 The xenconsole program supports a very simple protocol to notify parent about
153 write 0x00 to that fd after connecting to the guest but before entering the
154 event loop. Parent can read from the read end of the fd to know the status.