Maybe someone from virt team could refer to this. On Wed, May 27, 2020 at 2:06 PM Gianluca Cecchi <gianluca.cec...@gmail.com> wrote:
> On Wed, May 27, 2020 at 11:26 AM Gianluca Cecchi < > gianluca.cec...@gmail.com> wrote: > >> On Wed, May 27, 2020 at 10:21 AM Amit Bawer <aba...@redhat.com> wrote: >> >>> From your vdsm log, it seems as occurrence of an issue discussed at >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/JE76KK2WFDCDJL3DF52OGOLGXWHWPEDA/ >>> >>> 2020-05-26 19:51:53,837-0400 ERROR (vm/90f09a7c) [virt.vm] >>> (vmId='90f09a7c-3af1-45a9-a210-78a9b0cd4c3d') The vm start process failed >>> (vm:871) >>> Traceback (most recent call last): >>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 801, in >>> _startUnderlyingVm >>> self._run() >>> File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 2608, in >>> _run >>> dom.createWithFlags(flags) >>> File >>> "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line >>> 131, in wrapper >>> ret = f(*args, **kwargs) >>> File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line >>> 94, in wrapper >>> return func(inst, *args, **kwargs) >>> File "/usr/lib64/python3.6/site-packages/libvirt.py", line 1166, in >>> createWithFlags >>> if ret == -1: raise libvirtError ('virDomainCreateWithFlags() >>> failed', dom=self) >>> libvirt.libvirtError: unsupported configuration: unknown CPU feature: >>> tsx-ctrl >>> >>> >>> On Wed, May 27, 2020 at 9:15 AM Patrick Lomakin < >>> patrick.loma...@gmail.com> wrote: >>> >>>> I think the problem with a storage connection. Verify your IP addresses >>>> on the storage adapter port. Are they connected? After install my ports for >>>> storage was deactivated by defaut. Try to connect your iSCSI manually with >>>> iscsiadm command and then check your storage connection in storage tab >>>> using a host admin portal. >>>> >>> >> Yes, in that thread I asked if possible to specify in some way an >> alternate cpu type and/or flags to be setup for self hosted engine vm, >> without setup to automatically detect/configure it, but I didn't receive an >> answer. >> Because the cpu flag is there also in 4.3.9 but doesn't create problems >> with self hosted engine or host. >> >> Gianluca >> > > BTW: is there anything special we can do to help to have this cpu as > supported? > > model name : Intel(R) Xeon(R) Platinum 8260L CPU @ 2.40GHz > > So that others could have better and wider options and also RHV benefit > from it? > Also, I now find here below that Cascadelake is supposed to be supported: > > https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_cockpit_web_interface/#CPU_Requirements_SHE_cockpit_deploy > > > Thanks, > Gianluca > >
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/TVOTLOCNG44ZEZ7NHKBB7BOPXPCMMN3O/
