Error when start VMs


Badge
Hi everyone,

I'm new to Nutanix and just setup a cluster with 3 nodes. But when i started VMs with NIC, i got an error:

Operation failed: InternalException: kUncaughtException: Traceback (most recent call last): File "/home/afg/src/main/builds/build-ce-2017.07.20-stable-release/python-tree/bdist.linux-x86_64/egg/util/task/base_task.py", line 504, in _resume File "/home/afg/src/main/builds/build-ce-2017.07.20-stable-release/python-tree/bdist.linux-x86_64/egg/acropolis/hypervisor/host.py", line 74, in wrapper File "/home/afg/src/main/builds/build-ce-2017.07.20-stable-release/python-tree/bdist.linux-x86_64/egg/acropolis/vm/set_power_state_task.py", line 264, in _run File "/home/afg/src/main/builds/build-ce-2017.07.20-stable-release/python-tree/bdist.linux-x86_64/egg/acropolis/vm/set_power_state_task.py", line 353, in _power_on File "/usr/lib64/python2.6/contextlib.py", line 23, in __exit__ self.gen.next() File "/home/afg/src/main/builds/build-ce-2017.07.20-stable-release/python-tree/bdist.linux-x86_64/egg/acropolis/vm/set_power_state_task.py", line 350, in _power_on File "/home/afg/src/main/builds/build-ce-2017.07.20-stable-release/python-tree/bdist.linux-x86_64/egg/acropolis/hypervisor/kvm/libvirt_connection.py", line 127, in wrapper File "/home/afg/src/main/builds/build-ce-2017.07.20-stable-release/python-tree/bdist.linux-x86_64/egg/acropolis/hypervisor/kvm/power_mixin.py", line 126, in power_on_vm File "build/bdist.linux-x86_64/egg/pylibvirt.py", line 407, in createXML cimpl = self._pool.call("DomainCreateXML", self._cimpl, xml_bytes, flags) File "build/bdist.linux-x86_64/egg/pylibvirt.py", line 111, in call raise libvirtError(*err) libvirtError: Cannot find 'no' in path: No such file or directory

Tried to leave NIC empty, started VMs again and no error coming. So, if you have any suggestions please advise me.

Thank you,
Tuan

5 replies

Badge +1
greggstar wrote:

I found this error AFTER I upgraded to VERSION NUTANIX 20180123.170.
I found the same results with removing the NIC. But, with the NIC added, you see this error:


Note: Everything was fine, prior to the upgrade. NCC reported healthy across the board.


@greggstar

I too was getting this error and found that the reason was that when i went through with the upgrade of Nutanix CE there is a 2 step process. The first one is to up date AHV and then to update AOS...

Once AOS has been updated you will find that your VMs will be able to boot again.

@tuannd
Was this after an upgrade?
After my experiences i would definitely check that the versions of AOS and AHV are the same.
Userlevel 2
Badge +16
Looks like upgrading and/or downgrading Hypervisor/NCC version would fix this error?!
I got the same error. I thought it was because I manually set the NIC to a E1000 with acli, but that is not the case. I can't find where I can change a setting to point it to a new directory so it doesn't go to the build-ce-2017.07.20. If anyone else has figured this out let me know. This is strictly a lab, so if I have to rebuild stuff so be it, but I wouldn't expect an upgrade to break it like that.
Badge
Same error here after upgrading. Any Ideas how to fix this?
I found this error AFTER I upgraded to VERSION NUTANIX 20180123.170.
I found the same results with removing the NIC. But, with the NIC added, you see this error:


Note: Everything was fine, prior to the upgrade. NCC reported healthy across the board.

Reply