Hi everybody,
with this being an issue for so long but nobody than "us" (=canonical STS + canonical Dev) caring I wonder if we should even switch that on again - since it is also disabled upstream intentionally as Serge reported.
The question is if users that want/need it can enable it.
So I wonder if the following would enable it again as it should:
via libvirt
<cpu mode'custom' match='exact'> <model>qemu64</model>
<feature name='svm' policy='require'/>
</cpu>
via cmdline
qemu -cpu qemu64,+svm
@smb - could you test this on the AMD system when you find some time?
If it works I'd think we could close this bug without changing something.
Hi everybody,
with this being an issue for so long but nobody than "us" (=canonical STS + canonical Dev) caring I wonder if we should even switch that on again - since it is also disabled upstream intentionally as Serge reported.
The question is if users that want/need it can enable it.
<model> qemu64< /model>
So I wonder if the following would enable it again as it should:
via libvirt
<cpu mode'custom' match='exact'>
<feature name='svm' policy='require'/>
</cpu>
via cmdline
qemu -cpu qemu64,+svm
@smb - could you test this on the AMD system when you find some time?
If it works I'd think we could close this bug without changing something.