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.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561019
Title:
copied cpu flags don't match host cpu
To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1561019/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
