Difference between revisions of "Vnx-troubleshooting"
(→Troubleshooting (to be translated, revised and completed)) |
(→Errors) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
− | VNX relies mainly on KVM | + | VNX relies mainly on KVM and libvirt, so it is important to check that both are working correctly in your system. To do that: |
<ul> | <ul> | ||
− | <li>Processor with virtualization support. | + | <li>Processor with virtualization support. Check that your processor has support for virtualization extensions with the following command:</li> |
egrep '(vmx|svm)' --color=always /proc/cpuinfo | egrep '(vmx|svm)' --color=always /proc/cpuinfo | ||
If you see the word vmx (for Intel processors) or svm (for AMD processors) in <strong><span style="color:red">red</span></strong>, your processor has virtualization support. Be aware that virtualization extensions are controled from the BIOS and maybe in your computer are disabled. | If you see the word vmx (for Intel processors) or svm (for AMD processors) in <strong><span style="color:red">red</span></strong>, your processor has virtualization support. Be aware that virtualization extensions are controled from the BIOS and maybe in your computer are disabled. | ||
− | <li> | + | <li>Check that '''KVM''' modules can be loaded with:</li> |
modprobe kvm | modprobe kvm | ||
− | modprobe kvm_intel | + | modprobe kvm_intel # for Intel processors |
+ | modprobe kvm_amd # for AMD processors | ||
+ | |||
+ | </ul> | ||
+ | |||
+ | To be completed.... | ||
+ | <!-- | ||
<ul> | <ul> | ||
Line 67: | Line 73: | ||
/etc/init.d/libvirt-bin restart | /etc/init.d/libvirt-bin restart | ||
ver https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/503376 | ver https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/503376 | ||
+ | |||
+ | </ul> | ||
+ | --> | ||
+ | |||
+ | == Errors == | ||
+ | |||
+ | <ul> | ||
+ | <li>If starting a KVM virtual machine you get this error:</li> | ||
+ | <pre> | ||
+ | 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 | ||
+ | </pre> | ||
+ | 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/ | ||
</ul> | </ul> |
Latest revision as of 23:52, 27 May 2015
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.
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/