https://bugzilla.kernel.org/show_bug.cgi?id=102731 --- Comment #35 from cwseys@xxxxxxxxxxxxxxxx --- Thanks! I think you mistyped 4.2.3 -> 4.3.2 . Here's the table (helps me see any pattern b/c it is closer together. Less memory required. :) ) Hversion Gversion Gmem time before read-only 3.16 3.16 1 GB ~4 days 3.16 3.18.19 1 GB ~20 days 3.16 4.2.3 1 GB 4 days 4.2.3 4.2.3 2 GB not after ~90 days 4.2.3 3.16 1 GB inprogress > Then I upgraded the host to 4.3.2, noticed the guest had only 1G of > memory (and the guest kernel was bitching about not having enough memory > during some TCP operations) so I increased the guest memory to 2G, Bad > debugging style, but I was desperate. Debugging and production don't get along well together. :) > So now I've set the guest to 3.16 with 1G of memory. We'll see what > happens next. I haven't tried changing the host's kernel version yet. Will be interested to know how it turns out! Thanks for debugging and hopefully you'll help us (Debian/Ubuntu users) find a workaround at least. Thanks again, Chad. -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
