Fix the exception caused by IE8

This is a patch for issue 47. The user will get a exception when IE8
is used to access Kimchi.  Here, a patch is provided to avoid the
exception and the user can see the Kimchi web interfaces

Signed-off-by: Shu Ming <shuming@linux.vnet.ibm.com>
bug fix: kimchi supports to show VM with Chinese name

encode the vm's name as UTF-8

libvirt already supports Chinese name.
libvirt says:
virDomainGetXMLDesc:
* Returns a 0 terminated UTF-8 encoded XML instance, or NULL in case of error.
*         the caller must free() the returned value.

virt-manager can also show VM with Chinese name.

bug: https://github.com/kimchi-project/kimchi/issues/54

Signed-off-by: ShaoHe Feng <shaohef@linux.vnet.ibm.com>
bug: fix list vm name in unicode for mockmodel

mockmodel vm names have not converted in unicode, fix it.
Issue:https://github.com/kimchi-project/kimchi/issues/42

Signed-off-by: Royce Lv <lvroyce@linux.vnet.ibm.com>
Reviewed-by: Aline Manera <alinefm@br.ibm.com>
template: add rhel to osinfo

rhel iso was probed to be unknown distro and this is misleading,
add rhel distro information to osinfo

Signed-off-by: Royce Lv <lvroyce@linux.vnet.ibm.com>
Issue #59: Make the popup menu entirely visible in browser

In the guest list page, when some VM line is at the bottom of the
browser, and the user clicks "actions" button, the popup menu may
go out of the viewport or just show a part. We need to make sure
the whole body of the menu is in the viewport.
    In this patch, we did a check to the popup menu and scroll it
into browser viewport.
    Worked in IE9+, Chrome, Firefox 17.0.1, and Safari.

Signed-off-by: Hongliang Wang <hlwang@linux.vnet.ibm.com>
issue60: Avoid using default database file in test

Default database file maybe created by root usr,
making running test suite with unpriviledged usr raise error,
make testcases use their own temp database file instead.
REF:
https://github.com/kimchi-project/kimchi/issues/60

Signed-off-by: Royce Lv <lvroyce@linux.vnet.ibm.com>
issue34: add handling invalid iso file

Invalid iso file includes non-existent path, iso can't be probed by its volume id,
wrong iso format,non-bootable iso.
we will deny wrong format iso, non-bootable iso or file does not exist,
for iso we can't decide it's distro and version,
generate template with default setting.

Signed-off-by: Royce Lv <lvroyce@linux.vnet.ibm.com>