This bug has been copied from bug #1060557 and has been proposed to be backported to 6.5 z-stream (EUS).
I can reproduce this issue with: RHEVM 3.3.1-0.48.el6ev libvirt-0.10.2-29.el6_5.4.x86_64 Create a vm with name "mhuizer_9123456789212345678931234567894123456789512111" which name length is longer than 48. start the vm, from the event console, error message will pop up: "VM mhuizer_9123456789212345678931234567894123456789512111 is down. Exit message: internal error internal error Domain name 'mhuizer_9123456789212345678931234567894123456789512111' exceeded 48 characters."
Verified the issue with: libvirt-0.10.2-29.el6_5.5.x86_64 libvirt-debuginfo-0.10.2-29.el6_5.5.x86_64 libvirt-lock-sanlock-0.10.2-29.el6_5.5.x86_64 libvirt-python-0.10.2-29.el6_5.5.x86_64 libvirt-client-0.10.2-29.el6_5.5.x86_64 libvirt-devel-0.10.2-29.el6_5.5.x86_64 RHEVM 3.3.1-0.48.el6ev Use the same env as comment4, Scenario A: vm with 54 char name. 1. In rhevm3.3, Start the vm with name "mhuizer_9123456789212345678931234567894123456789512111" (totally 55 char with '\0'), the vm could start successfully. Console popup "VM mhuizer_9123456789212345678931234567894123456789512111 started on Host lcui-rhel65" 2. In host, # sanlock status daemon 450a307d-77a2-49c1-befb-88f422c91e49.lcui-rhel6 ... p 30559 mhuizer_912345678921234567893123456789412345678 ... The owner_name part have been truncated as 48 chars by design. Scenario B: vm with a normal name shorter than 48 1. In rhevm3.3, Start the vm with name "lcui_rhel_test" VM start successfully and console popup: VM lcui_rhel_test was started by admin@internal (Host: lcui-rhel65). 2. In host, # sanlock status ... p 30559 mhuizer_912345678921234567893123456789412345678 p 29995 p 32720 lcui_rhel_test ... New VM name displayed with the full name as it is shorter than 48 Scenario C: create a vm with name longer than 48 in KVM. The vm could start successfully. As above all, change the status from 'ON_QA' to 'VERIFIED'
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0256.html