On Wed, Feb 02, 2022 at 05:42:33PM +0200, Juhani Rautiainen wrote:
Hi!
Maybe you have to modify qemu VM CPU settings? I mean that usually if you don't see the svm flag on AMD CPU, virtualization is not available. This page suggests changes to qemu CPU model: https://techviewleo.com/how-to-enable-nested-virtualization-on-kvm-qemu/
I think that the "host-passthrough" setting should let all the CPU flags go through to the VM (https://wiki.openstack.org/wiki/LibvirtXMLCPUModel).
Yes, thank you, you are absolutely right. I had the CPU model set to "host-model" (where libvirt tries to create a model approximating the host). Changing it to "host-passthrough" (ie. same as qemu -cpu host) fixed it and allowed me to install oVirt node in the guest and activate it. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/