7:55 a.m.
Hello,
I'm importing a VM into a new oVirt environment that is in 4.3.10: the new
host is the same as the previous one (only difference it is in 4.3.10 while
the old one in 4.3.9).
This VM acted as a single host HCI environment (with 4.3.9). I imported the
storage domain containing the VM and its disks and the VM boots ok.
Now its Hosted Engine VM (that is so a nested VM) doesn't start.
I think it was good when I stopped/detached it... and so I would like to
cross check and verify if I missed something configuring the new
environment or something changed from 4.3.9 to 4.3.10
In vdsm.log I see this reason:
2020-07-23 14:38:20,489+0200 ERROR (vm/9233dc8b) [virt.vm]
(vmId='9233dc8b-7a4d-4fac-8551-dc7407f36548') The vm start process failed
(vm:
934)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 868, in
_startUnderlyingVm
self._run()
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2892, in
_run
dom = self._connection.defineXML(self._domain.xml)
File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py",
line 131, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94,
in wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3743, in
defineXML
if ret is None:raise libvirtError('virDomainDefineXML() failed',
conn=self)
libvirtError: invalid argument: could not find capabilities for arch=x86_64
domaintype=kvm
The relevant parts of the generated xml in vdsm.log seems:
2020-07-23 14:38:20,487+0200 INFO (vm/9233dc8b) [virt.vm]
(vmId='9233dc8b-7a4d-4fac-8551-dc7407f36548') <?xml version="1.0"
encoding="ut
f-8"?><domain type="kvm"
xmlns:ns0="http://ovirt.org/vm/tune/1.0"
xmlns:ovirt-vm="http://ovirt.org/vm/1.0">
<name>HostedEngine</name>
<uuid>9233dc8b-7a4d-4fac-8551-dc7407f36548</uuid>
<memory>16777216</memory>
<currentMemory>16777216</currentMemory>
<iothreads>1</iothreads>
<maxMemory slots="16">67108864</maxMemory>
<vcpu current="2">32</vcpu>
<sysinfo type="smbios">
<system>
<entry name="manufacturer">oVirt</entry>
<entry name="product">oVirt Node</entry>
<entry name="version">7-7.1908.0.el7.centos</entry>
<entry
name="serial">704e1338-5dec-46f8-a186-8c2080dcefd8</entry>
<entry
name="uuid">9233dc8b-7a4d-4fac-8551-dc7407f36548</entry>
</system>
</sysinfo>
<clock adjustment="0" offset="variable">
<timer name="rtc" tickpolicy="catchup"/>
<timer name="pit" tickpolicy="delay"/>
<timer name="hpet" present="no"/>
</clock>
<features>
<acpi/>
</features>
<cpu match="exact">
<model>Skylake-Server</model>
<feature name="spec-ctrl" policy="require"/>
<feature name="ssbd" policy="require"/>
<feature name="md-clear" policy="require"/>
<topology cores="2" sockets="16"
threads="1"/>
<numa>
<cell cpus="0,1" id="0"
memory="16777216"/>
</numa>
</cpu>
<cputune/>
...
</metadata>
<on_poweroff>destroy</on_poweroff><on_reboot>destroy</on_reboot><on_crash>destroy</on_crash></domain>
(vm:2890)
Any insights?
The configuration of the new 4.3.10 physical oVirt environment that
contains the VM has this cluster cpu type:
Intel Skylake Server IBRS SSBD MDS Family
Do I have to change it to anything else? I don't remember how it was set in
4.3.9
Thanks in advance,
Gianluca