Ask Your Question
0

HPHelion: Install failing on Azure virtual machine

asked 2014-11-15 19:52:16 -0600

updated 2014-11-17 03:46:50 -0600

smaffulli gravatar image

Following the install guide for HP Helion Openstack, http://docs.hpcloud.com/helion/commun...

I follow these steps

Log in as root:

sudo su -
Determine if .ssh/id_rsa exists:

ls -l ~root/.ssh/id_rsa
NOTE: The output should look like the example below:

drwxr-x--- . 4096 May 11 09:23
-rwxr-x--- ..4096 May 11 09:23
-rwxr-x--- id_rsa1455 May 11 09:24
-rwxr-x--- id_rsa.pub 1455 May 11 09:24
If the key does not exist, create one, omitting a passphrase and accepting the defaults by pressing Enter:

ssh-keygen -t rsa -N

This is the output i get

root@baHPHelion:/datadrive/tripleo# ls -l ~root/.ssh/id_rsa
-rw------- 1 root root 1766 Nov 16 01:32 /root/.ssh/id_rsa

I go on to start the install

root@baHPHelion:/datadrive/tripleo# sudo HP_VM_MODE=y bash -x tripleo-incubator/scripts/hp_ced_host_manager.sh --create seed
+ set -e
+ set -o pipefail
+ umask 077
++ basename tripleo-incubator/scripts/hp_ced_host_manager.sh
+ SCRIPT_NAME=hp_ced_host_manager.sh
++ dirname tripleo-incubator/scripts/hp_ced_host_manager.sh
+ SCRIPT_HOME=tripleo-incubator/scripts
+ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:tripleo-incubator/scripts
++ id -u
+ '[' 0 '!=' 0 ']'
+ '[' /root '!=' /root ']'
+ export CREATE_SEED=0
+ CREATE_SEED=0
+ export SHUTDOWN_SEED=0
+ SHUTDOWN_SEED=0
+ export BOOT_SEED=0
+ BOOT_SEED=0
+ export EXPORT_SEED=0
+ EXPORT_SEED=0
+ export IMPORT_SEED=0
+ IMPORT_SEED=0
+ export VM_PLAN_FILE=
+ VM_PLAN_FILE=
++ getopt -o ph, -lhelp,create-seed,shutdown-seed,boot-seed,export-seed,import-seed,vm-plan: -n hp_ced_host_manager.sh -- --create seed
+ TEMP=' --create-seed -- '\''seed'\'''
+ '[' 0 '!=' 0 ']'
+ eval set -- ' --create-seed -- '\''seed'\'''
++ set -- --create-seed -- seed
+ print_deps
+ echo 'This script depends on certain baseline capabilities of the HOST operating system'
This script depends on certain baseline capabilities of the HOST operating system
+ echo

+ echo 'The following MUST be installed and running:'
The following MUST be installed and running:
+ echo

+ echo '    openvswitch'
    openvswitch
+ echo '    kvm/qemu'
    kvm/qemu
+ echo '    libvirt'
    libvirt
+ echo '    python-libvirt'
    python-libvirt
+ '[' -n y ']'
+ echo '
    You must also have the following for Virtual Baremetal:
        openssh-server
    '

    You must also have the following for Virtual Baremetal:
        openssh-server

+ true
+ case "$1" in
+ CREATE_SEED=1
+ shift
+ true
+ case "$1" in
+ shift
+ break
+ '[' 1 -gt 1 ']'
+ '[' -z y -a -n '' ']'
+ TMPDIR=/tmp
+ IMAGES_DIR=/var/lib/libvirt/images
+ OPTIONS_PATH=/var/lib/libvirt/images/seed_options
+ TMP_MNT_DIR=/tmp/tmp_options_mount
+ OPTIONS_SIZE=7G
+ ARCH=amd64
+ BRIDGE_NAME=brbm
+ BM_NETWORK_CIDR=192.0.2.0/24
+ BM_NETWORK_SEED_IP=192.0.2.1
+ BM_NETWORK_GATEWAY=192.0.2.1
+ MEMORYM=8192
+ MEMORYK=8388608
+ CPUS=1
+ NODE_DISK=512
+ EXTRAOPTS=
+ IMAGES='overcloud-compute overcloud-control overcloud-control-mgmt overcloud-swift undercloud'
+ DEPLOY_IMAGES='deploy-ramdisk.initramfs deploy-ramdisk.kernel deploy-ramdisk-ironic.initramfs deploy-ramdisk-ironic.kernel'
+ OVERCLOUD_EXT_NET_DEV=ext-gw
+ BM_GATEWAY_DEV=bm-gw
+ ROUTE_DEV=virbr0
+ LIBVIRT_NIC_DRIVER=virtio
+ LIBVIRT_DISK_BUS_TYPE=scsi
+ HOST_IP=192.168.122.1
+ SEED_COMP_PORT=27410
+ SEED_IMAGE_ID=seedImageID
+ apt_updated=
+ check_system_setup
+ check_install_packages
+ '[' -e /etc/debian_version ']'
+ '[' -n y ']'
+ dpkg-query -s openssh-server
+ dpkg-query -s openvswitch-switch
+ dpkg-query -s qemu-system-x86
+ dpkg-query -s libvirt-bin
+ dpkg-query -s python-libvirt
+ check_execute_packages
+ which ovs-vsctl
+ which kvm
+ which virsh
+ '[' -e /etc/debian_version ']'
++ lsb_release -cs
+ RELEASE=trusty
+ '[' trusty = trusty ']'
+ '[' '!' -e /usr/bin/kvm ']'
+ '[' -e /usr/bin/kvm ']'
+ export TRIPLEO_ROOT=tripleo-incubator/scripts/../../
+ TRIPLEO_ROOT=tripleo-incubator/scripts/../../
+ export IMAGE_NAME=seed
+ IMAGE_NAME=seed
+ export VM_IP=
+ VM_IP=
+ export IMAGE_CACHE_FILE=tripleo-incubator/scripts/../..//images/seed.qcow2
+ IMAGE_CACHE_FILE=tripleo-incubator/scripts/../..//images/seed.qcow2
+ '[' '!' -e tripleo-incubator/scripts/../..//images/seed ...
(more)
edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
2

answered 2014-11-15 22:57:04 -0600

9lives gravatar image

from the logs, you might not install kvm in your ubuntu14 or you did not turn on the VT for virutalization in bios , Helion virtual mode install needs the kvm as a prerequisite. check your kvm is running by the following command in terminal

kvm-ok

Hope that helps!

Vic

edit flag offensive delete link more

Comments

Thanks for the feedback,

I run your command and got the following.

root@baHPHelion:/datadrive/tripleo# kvm-ok INFO: Your CPU does not support KVM extensions KVM acceleration can NOT be used

Seems the Microsoft Azure Ubuntu VM images /cpu's don't support KVM extensions.

Lismore gravatar imageLismore ( 2014-11-15 23:17:55 -0600 )edit

I did some research based on your comment,

I followed these steps > https://help.ubuntu.com/community/KVM/Installation (https://help.ubuntu.com/community/KVM...)

The installation continued & now hit another failure unrelated to this topic.

libvirt: QEMU Driver error : internal error: Unable to determine model for scsi controller

thanks

Lismore gravatar imageLismore ( 2014-11-15 23:48:02 -0600 )edit

are you using the VM from Azure to install Helion? If so, i don't think you can make it work, because Helion requires hardware level visualization meaning it should be installed in physical box with kvm installed.

9lives gravatar image9lives ( 2014-11-16 00:41:07 -0600 )edit
0

answered 2015-01-01 18:25:54 -0600

If you are installing HP Helion OpenStack Community Edition using the Virtual Installation method, you must use a physical machine running Ubuntu as the host for the installation. You cannot attempt to follow these instructions using a virtual machine. The reason for this is because the Virtual Installation option creates the cloud using nested virtualization already, and adding another layer of virtualization is not supported (and would greatly impede the performance of the environment as well if it were possible). Also note that using the Virtual Installation method creates an environment that will not persist if the physical host machine is restarted (also due to the nested virtualization)

edit flag offensive delete link more
0

answered 2014-12-05 01:31:39 -0600

kashifkarar gravatar image

you cannot do any modification on the BIOS plus the virtualization is not allowed on Windows Azure Virtual Machine, you cannot work with Virtualization over Virtual Machine. However, I had the similar issue on VMware workstation 10 and got it resolved by checking the option as mentioned below:

image description

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-11-15 19:50:06 -0600

Seen: 402 times

Last updated: Dec 05 '14