Vnx-troubleshooting

Troubleshooting

VNX relies mainly on KVM and libvirt, so it is important to check that both are working correctly in your system. To do that:

• Processor with virtualization support. Check that your processor has support for virtualization extensions with the following command:

egrep '(vmx|svm)' --color=always /proc/cpuinfo

If you see the word vmx (for Intel processors) or svm (for AMD processors) in red, your processor has virtualization support. Be aware that virtualization extensions are controled from the BIOS and maybe in your computer are disabled.

• Check that KVM modules can be loaded with:

 modprobe kvm
 modprobe kvm_intel    # for Intel processors
 modprobe kvm_amd      # for AMD processors

To be completed....

Errors

• If starting a KVM virtual machine you get this error:

ERROR: VNX::vmAPI_libvirt->start_vm returns 'Error calling qemu:///system hypervisor libvirt error code: 1, 
message: internal error: process exited while connecting to monitor: qemu-system-i386: -drive file=/root/.vnx/scenarios/simple_ubuntu/vms/ubuntu/fs/root_cow_fs,if=none,id=drive-ide0-0-0,format=qcow2: 
could not open disk image /root/.vnx/scenarios/simple_ubuntu/vms/ubuntu/fs/root_cow_fs: 
Could not open backing file: Could not open '/usr/share/vnx/examples/fw/rootfs_ubuntu': Permission denied

Check the permissions of the directory where the rootfs is and give it execution permission if not set:

chmod +x /usr/share/vnx/examples/fw/