On Mon, Dec 08, 2014 at 01:20:19PM +, Dave Walker wrote:
> On 8 December 2014 at 10:33, Daniel P. Berrange wrote:
> > On Sat, Dec 06, 2014 at 04:38:52PM +1100, Tony Breeds wrote:
> >> Hi All,
> >> In the most recent team meeting we briefly discussed: [1] where the
> >> console.log grows in
On 8 December 2014 at 10:33, Daniel P. Berrange wrote:
> On Sat, Dec 06, 2014 at 04:38:52PM +1100, Tony Breeds wrote:
>> Hi All,
>> In the most recent team meeting we briefly discussed: [1] where the
>> console.log grows indefinitely, eventually causing guest stalls. I mentioned
>> that I was
On Sat, Dec 06, 2014 at 04:38:52PM +1100, Tony Breeds wrote:
> Hi All,
> In the most recent team meeting we briefly discussed: [1] where the
> console.log grows indefinitely, eventually causing guest stalls. I mentioned
> that I was working on a spec to fix this issue.
>
> My original plan wa
Tony Breeds wrote:
> [...]
> So if that timeline is approximately correct:
>
> - Can we wait this long to fix the bug? As opposed to having it squashed in
> Kilo.
> - What do we do in nova for the next ~12 months while know there isn't a qemu
> to fix this?
> - Then once there is a qemu that fi
On Sun, Dec 07, 2014 at 08:47:28AM +, Tim Bell wrote:
> Would the nova view console be able to see the older versions also ? Ideally,
> we'd also improve on the current situation where the console contents are
> limited to the current file which causes problems around hard reboot
> operations
> -Original Message-
> From: Tony Breeds [mailto:t...@bakeyournoodle.com]
> Sent: 06 December 2014 06:39
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [nova] Fixing the console.log grows forever bug.
>
...
>
> However I was encouraged to in
Hi All,
In the most recent team meeting we briefly discussed: [1] where the
console.log grows indefinitely, eventually causing guest stalls. I mentioned
that I was working on a spec to fix this issue.
My original plan was fairly similar to [2] In that we'd switch libvirt/qemu to
using a unix
