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/

2015-01-07 22:38 GMT+08:00 Markus Zoeller <mzoel...@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 replacement of the log file has impact on the "os-console-output"
> API [2]. The CLI command `nova console-log <instance-name>` shows:
>     "ERROR (ClientException): The server has either erred or is incapable
>     of performing the requested operation. (HTTP 500)"
> Horizon shows in its "Log" tab of an instance
>     "Unable to get log for instance <uuid>."
>
> Would it be good to have both, the serial console *and* the console log
> file?
>
>
> [1]
> https://review.openstack.org/#/c/113960/14/nova/virt/libvirt/driver.py,cm
> [2]
> http://developer.openstack.org/api-ref-compute-v2-ext.html#ext-os-console-output
>
>
> Regards,
> Markus Zoeller
> IRC: markus_z
> Launchpad: mzoeller
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Regards!
-----------------------------------
Lingxian Kong

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to