Re: [Xen-devel] PATCH: Add persistent guest & hv logging in xenconsoled

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 31/5/07 22:32, "Daniel P. Berrange" <berrange@xxxxxxxxxx> wrote:

> The first is how to configure & pass the --log arg to xenconsoled. In the
> upstream xen codebase the various daemons (xenstore, xenconsoled, etc)
> are all forked by the tools/misc/xend script (typically in /usr/sbin/xend).
> In Fedora we're intending to ditch this script & just start each daemon
> directly from the init script & thus we can use /etc/sysconfig/xend to
> configure the logging args. Solaris also doesn't use that tools/misc/xend
> script IIRC, having their own scripts for stopping/starting distros. So
> in this patch I've not made any attempt to provide a way to actually pass
> the --log arg to xenconsoled, leaving such decisions upto the distro
> packagers. Any alternate ideas are welcome...

For guest logging it'd be nice to have the option to specify via xenstore
where the log file should be written. Then it could be decided per guest by
xend, perhaps via a config file option. Having a blanket option on the
cmdline *as well* as a fallback is okay though. Other useful options would
be max log size (both in terms of max logging to a file, and max buffering
for the pty), again these could be read from xenstore per guest, with a
cmdline-specifiable fallback.

> When logging hypervisor data we call xc_readconsolering to fetch the data.
> Since we don't want to log the same data over & over again we have to tell
> it to clear the console. So if you enable hypervisor logging in xenconsoled,
> then 'xm dmesg' will no longer show you any data. Personally I don't have
> any problem with this, but if there's a way to reliably consume hypervisor
> logs in an incremental manner without having to clear the data I'm open
> to suggestions...

I thought I'd applied a patch to improve this interface, clearly I haven't
though. I'll look into it.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel