While bisecting on upstream git with just "-cpu Penryn" we have seen that it always works there.
So it might be an interaction with some Ubuntu build/packaging/configure detail together with these old chips.
While we still can't be sure if the VMX warnings are a red-herring chances are that only "-cpu Penryn,vmx=on" will trigger the issue - Andreas will test and bisect with that once he is back online - we will see if that is any different.
I'll also build a Ubuntu'esque 4.2 with the Penryn changes of [1] reverted just to complete the interim picture of our testing. That is available for testing at [2]. Further I added a Ubuntu build with rather crude reverts of almost all VMX related 4.2 changes.
Thanks David!
While bisecting on upstream git with just "-cpu Penryn" we have seen that it always works there. /configure detail together with these old chips.
So it might be an interaction with some Ubuntu build/packaging
While we still can't be sure if the VMX warnings are a red-herring chances are that only "-cpu Penryn,vmx=on" will trigger the issue - Andreas will test and bisect with that once he is back online - we will see if that is any different.
I'll also build a Ubuntu'esque 4.2 with the Penryn changes of [1] reverted just to complete the interim picture of our testing. That is available for testing at [2]. Further I added a Ubuntu build with rather crude reverts of almost all VMX related 4.2 changes.
[1]: https:/ /git.qemu. org/?p= qemu.git; a=commit; h=0723cc8a5558c 94388db75ae1f49 91314914edd3 /launchpad. net/~paelzer/ +archive/ ubuntu/ bug-1866870- qemu-penryn- crash /launchpad. net/~paelzer/ +archive/ ubuntu/ bug-1866870- qemu-penryn- crash-fullrever ts
[2]: https:/
[3]: https:/