This can be tested from PPA [1]
and was Regression tested against the functionally equal (other type names) [2]
Initially implemented for the bug, then adapted for our discussion around naming.
Finally regression tests found an issue in the type aliasing that was fixed as well.
Example without the new type using more than 1TB of memory:
The guest starts up a while, but when initializing memory it crashes and the guest log will show:
KVM internal error. Suberror: 1
emulation failure
RAX=0000000000000000 RBX=0000000000000046 RCX=0000000000000000 RDX=00000000000003f4
...
With the new type set (e.g. via virsh edit) the guest works.
This can be tested from PPA [1]
and was Regression tested against the functionally equal (other type names) [2]
Initially implemented for the bug, then adapted for our discussion around naming.
Finally regression tests found an issue in the type aliasing that was fixed as well.
Example without the new type using more than 1TB of memory: 00000 RBX=00000000000 00046 RCX=00000000000 00000 RDX=00000000000 003f4
The guest starts up a while, but when initializing memory it crashes and the guest log will show:
KVM internal error. Suberror: 1
emulation failure
RAX=00000000000
...
With the new type set (e.g. via virsh edit) the guest works.
[1]: https:/ /launchpad. net/~canonical- server/ +archive/ ubuntu/ large-virt /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ 3284
[2]: https:/