On Tue, Jul 10, 2018 at 11:32 PM, Sakhi Hadebe <sa...@sanren.ac.za> wrote:
> Hi, > > I did not select any CPU architecture. It doenst gove me the option to > select one. It only states the number of virtual CPUs and the memory for > the engine VM. > > Looking at the documentation of installing ovirt-release36.rpm....it does > allow you to select te CPU, but not when installing ovirt-release42.rpm > > On Tuesday, July 10, 2018, Alastair Neil <ajneil.t...@gmail.com> wrote: > >> what did you select as your CPU architecture when you created the >> cluster? It looks like the VM is trying to use a CPU type of "Custom", how >> many nodes in your cluster? I suggest you specify the lowest common >> denominator of CPU architecture (e.g. Sandybridge) of the nodes as the CPU >> architecture of the cluster.. >> >> On Tue, 10 Jul 2018 at 12:01, Sakhi Hadebe <sa...@sanren.ac.za> wrote: >> >>> Hi, >>> >>> I have just re-installed centOS 7 in 3 servers and have configured >>> gluster volumes following this documentation: >>> https://www.ovirt.org/blog/2016/03/up-and-running-with-ovirt-3-6/, But >>> I have installed >>> >>> http://resources.ovirt.org/pub/yum-repo/ovirt-release42.rpm >>> >>> ​package. >>> Hosted-engine --deploy is failing with this error: >>> >>> "rhel7", "--virt-type", "kvm", "--memory", "16384", "--vcpus", "4", >>> "--network", "network=default,mac=00:16:3e:09:5e:5d,model=virtio", >>> "--disk", "/var/tmp/localvm0nnJH9/images/eacac30d-0304-4c77-8753- >>> 6965e4b8c2e7/d494577e-027a-4209-895b-6132e6fc6b9a", "--import", >>> "--disk", "path=/var/tmp/localvm0nnJH9/seed.iso,device=cdrom", >>> "--noautoconsole", "--rng", "/dev/random", "--graphics", "vnc", "--video", >>> "vga", "--sound", "none", "--controller", "usb,model=none", "--memballoon", >>> "none", "--boot", "hd,menu=off", "--clock", "kvmclock_present=yes"], >>> "delta": "0:00:00.979003", "end": "2018-07-10 17:55:11.308555", "msg": >>> "non-zero return code", "rc": 1, "start": "2018-07-10 17:55:10.329552", >>> "stderr": "ERROR unsupported configuration: CPU mode 'custom' for x86_64 >>> kvm domain on x86_64 host is not supported by hypervisor\nDomain >>> installation does not appear to have been successful.\nIf it was, you can >>> restart your domain by running:\n virsh --connect qemu:///system start >>> HostedEngineLocal\notherwise, please restart your installation.", >>> "stderr_lines": ["ERROR unsupported configuration: CPU mode 'custom' for >>> x86_64 kvm domain on x86_64 host is not supported by hypervisor", "Domain >>> installation does not appear to have been successful.", "If it was, you can >>> restart your domain by running:", " virsh --connect qemu:///system start >>> HostedEngineLocal", "otherwise, please restart your installation."], >>> "stdout": "\nStarting install...", "stdout_lines": ["", "Starting >>> install..."]} >>> >> This seems to be in the phase where we create a local vm for the engine. We do this with plain virt-install, nothing fancy. Searching the net for "unsupported configuration: CPU mode 'custom'" finds other relevant reports, you might want to check them. You can see the command in bootstrap_local_vm.yml . Please check/share versions of relevant packages (libvirt*, qemu*, etc) and relevant logs (libvirt). Also updating the subject line and adding Simone. Best regards, -- Didi
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5VIWOQSJOUIVYLLGKKQVMTDBE6MEVGGY/
