[openstack-dev] [nova] serial-console *replaces* console-log file?
Markus Zoeller
mzoeller at de.ibm.com
Mon Jan 12 09:03:00 UTC 2015
> On Fri, Jan 09, 2015 at 09:15:39AM +0800, Lingxian Kong wrote:
>
>There is an excellent post describing this, for your information:
>
http://blog.oddbit.com/2014/12/22/accessing-the-serial-console-of-your-nova-servers/
In the last section of that article he describes my issue as well:
"It would be nice to have both mechanisms available
-- serial console support for interactive access, **and**
console logs for retroactive debugging."
> Good reference, you can also get some information here:
>
> https://review.openstack.org/#/c/132269/
>
> 2015-01-07 22:38 GMT+08:00 Markus Zoeller <mzoe... at de.ibm.com>:
> > The blueprint "serial-ports" introduced a serial console connection
> > to an instance via websocket.
> > I'm wondering
> > * why enabling the serial console *replaces* writing into log file
[1]?
> > * how one is supposed to retrieve the boot messages *before* one
connects?
>
> The good point of using serial console is that you can create with a
> few lines of python an interactive console to debug your virtual
> machine.
>
> s.
I really like the feature of the serial console and I don't doubt its
usefulness. I'm worried about *not* persisting the OS messages into
a file when I activate the "serial console" feature. Why not having both?
Regards,
Markus Zoeller
IRC: markus_z
Launchpad: mzoeller
More information about the OpenStack-dev
mailing list