Hi Daniel, might I ask what you expect now? The changes to seabios are not even upstream yet in git://git.seabios.org/seabios.git The changes to qemu are neither upstream in git://git.qemu.org/qemu.git
The changes linked also are for a qemu way++ back in time (like pre trusty), so they just don't apply. Some of these changes are handled already, but different like the second qemu change of above mail is in qemu since "6c7c3c21 x86: implement la57 paging mode" which is qemu >=2.9. That said - this one I could track, maybe the other changes are also upstream but in a way different form. At least for myself I currently have no >1TB system to even try this - well I have done this on s390x and there it works fine already but you need x86 here. Even when all of the above would be resolved, the mail above states that even if those are applied they still have issues when going >1TB. I think you'd need a clear this is what I tried and this is what fails with a setup as simple as possible. If it fails in Ubuntu we can build a latest upstream build for you and if failing there we can work with upstream to resolve properly. From there we can think about the backportability of those changes. But the suggested "hey there are these patches, won't work. Please don't get me wrong (I want to help), but so far this appears to me so far as a suggestion of a set of non-upstreamed, non-applicable, non-testable, non-working changes. We need to better sort out how to handle this which is why I ask what you expect to happen now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769053 Title: Cannot start a guest with more than 1TB of RAM To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1769053/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
