Re: [ovirt-users] Engine start up error (NIC name too long)

Hi Didi, Thanks for the reply. oVirt Engine Version: 4.1.6.2-1.el7.centos

I was able to locate the vm.conf file (/var/run/ovirt-hosted-engine-ha) for the engine and I tried changing the NIC name to something smaller: “prvmgmt". Libvirt then threw an error that the MTU for the NIC was incorrect. So I’m not sure if the NIC name length was the exact cause. Anyway I ended up editing the conf file to wipe that NIC and then was able to successfully log into the engine.

Thanks for your response, appreciate it. Alex Witte On Oct 15, 2017, at 9:31 AM, Yedidyah Bar David <didi(a)redhat.com&gt; wrote: On Sun, Oct 15, 2017 at 4:25 AM, Alexander Witte <alexander.witte(a)baicanada.com&gt; wrote: Help! I seem to be getting this error when trying to start the hosted engine. I had created another network interface for the engine and it appears the name is too long? Can someone please point me to how I can resolve this? 2017-10-14 21:03:00,292-0400 ERROR (vm/c1dae7a4) [virt.vm] (vmId='c1dae7a4-5b86-4fcb-b66d-4a6a91bbe2ad') The vm start process failed (vm:631) Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 562, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 2060, in _run self._connection.createXML(domxml, flags), File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 123, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 1006, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3567, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: Network interface name 'PrivateManagement' is too long: Numerical result out of range 2017-10-14 21:03:00,300-0400 INFO (vm/c1dae7a4) [virt.vm] (vmId='c1dae7a4-5b86-4fcb-b66d-4a6a91bbe2ad') Changed state to Down: Network interface name 'PrivateManagement' is too long: Numerical result out of range (code=1) (vm:1259) Searching google, I only find two results - your post, and: https://bugzilla.redhat.com/show_bug.cgi?id=1478806 So should be fixed in 4.1.6. Which version do you use? Regards, -- Didi