https://bugzilla.kernel.org/show_bug.cgi?id=102731 --- Comment #32 from John Hughes <john@xxxxxxxxx> --- Well I've (finally) rebooted with guest kernel 3.16 and 1Go memory. It took a long time to convince the users to risk a (potentially) unstable system after a long time of all working OK. For memory -- the problem went away when I moved the host kernel to 4.2.3 and increased the memory of the guest system to 2Go. Changing the guest kernel from 4.2.3 to 3.16 *did not* make the problem go away. Possible results -- 1. problem does not show up, implies the fix is moving the host kernel to 4.2.3 2. problem does show up, implies the fix is either: a. increasing the guest memory to 2Go, or b. moving the host to 4.2.3 *and* increasing the guest memory to 2Go c. moving the guest to 4.2.3 *and* increasing the guest memory to 2Go d. moving the host to 4.2.3 *and* moving the guest to 4.2.3 e. moving the host to 4.2.3 *and* moving the guest to 4.2.3 *and* increasing the guest memory to 2Go. More news as it happens. -- 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
