HPE VME Morpheous Installation failed

[ACITI-steve]

Hi,

I'm trying to setup HPE VME Essential for labs,

I had finished HPE-VME-Console installation.

The next one is to install VME Manager,

but I can't set the manager VM up,

it always stuck at 93%,

sometimes it says the vm cannot start...

Is there something that I was missconfigured?

Here's the log shows in /var/log//hpe-vm

2025-02-13 08:44:23 INFO: Running hpe-vm in interactive mode
2025-02-13 08:46:52 INFO: Preparing KVM
2025-02-13 08:46:53 WARN: context [anonymous] 23:4 attribute proxyHost isn't defined
2025-02-13 08:46:53 WARN: context [anonymous] 24:11 attribute noProxy isn't defined
2025-02-13 08:46:56 ERROR: Unable to start vm hpevmemanager:

2025-02-13 08:47:47 INFO: Running hpe-vm in interactive mode
2025-02-13 08:49:17 INFO: Preparing KVM
2025-02-13 08:49:18 WARN: context [anonymous] 23:4 attribute proxyHost isn't defined
2025-02-13 08:49:18 WARN: context [anonymous] 24:11 attribute noProxy isn't defined
2025-02-13 08:49:21 ERROR: Unable to start vm hpevmemanager:

[Steven McLean · Accepted solution]

Check what you are entering as "Management Interface", i ran in to this too, as I was entering Bond0, however, when i ran an ifconfig, i realized that the management IP address was bound to the "mgmt" interface.  Once i enter mgmt as the Management Interface it completed correctly.

Also, if the deployment failed, you can Kill the VM and remove the files, 

the commant to kill the vm is;  virsh destroy "vm-name", vm name should be vmem-01

then check the /var/morpheus/kvm/local directory and remove the morpheus files.

then rerun the hpe-vm installer.

[mnavada]

Hi,

During the deployment of VME manager stuck at 93% and report as timeout can happen due to following reason.

1. MTU is set to 9000 at interface level. However, MTU is not set at "Switch level". On both side "interface and switch" level you need to set MTU if you are setting. However, VME works with MTU 1500 also.

2. Name resolution. You need to make sure that "vme manager" hostname and IP address are updated in DNS. If you are not using DNS, then "vme manager" hostname and IP needs to be updated on all nodes which part of this setup along with IP and hostnames of nodes. Edit /etc/hosts file and update it. Check name resoultuon by use of "nslookup".

3. Make sure that "Hardware enablement product" installed for ubuntu for better performance and GFS2 support which will upgrade the Linux kernel ( apt install -y linux-generic-hwe-22.04 )

4. If your environment uses "proxy", update "/etc/bash.bashrc" to make sure that both "proxy" and "no_proxy" are updated. Confirm the correct "subnet" address.

You can redeploy this "vme manager" as below.

Login as "root" and excute the below command.

virsh destroy < domain ID of vme manager>
virsh undefine < vme manager name >
rm -rf /var/morpheus/kvm/vms/*
rm -rf /var/morpheus/kvm/local/*
rm -rf /var/morpheus/kvm/config/*

Run "hpe-vm" to redeploy.

If still issue, let me know. We can arrange remote session to fix this issue.

Regards,

Manjunath G. Navada
Technical Solutions Consultant
ER MCS Software [HPUX, Ubuntu Linux, HPE VM Essentials]

Global Support – Remote

Hewlett Packard Enterprise

[SamFan]

HI 

I have same issue, can we have a remote?

Tks

[Moto_PK]

Hi Samfan,

Please reach out to hpe-sw-trial-vmessentials@hpe.com for a remote session.

[ACITI-steve]

Hi SamFan,

Are you stucked when building manager VM?

You can follow HPE website's step-by-step video to build it.

You must set the interface to Trunk mode like the HPE video did!

After I set the interface to Trunk mode, the Manager VM build successfully~

The 93% will take a long time to reach 100%, you just wait~

You can ssh to Ubuntu by using another Putty session (during it shows 93%), 

then check the Manager VM is running or not by using CLI command!

[SamFan]

Hi

Yes, I stuck at building manager VM.

Is it possible to use stand alone network?

My error shows unable to start vm  xxxx.

My manage vm always show shut off....

[VVin83]

Hi,

I have same problem, oyu have an issue?

[ACITI-steve]

Hi SamFan,

I'm not HPE employee~

I build the Manager VM in standalone network first also;

but the Manager VM didn't power on like you said (alway shut dwon stat)~

The VM power on and running until I reconfigure the interface to trunk mode...

So, I guess it can't set it up at standalone network...

[mnavada]

Hi Samfan,

Thanks for your kind co-operation during the remote session. We could sucessfully able to deploy the VME manager after sucessful reinstallation of OS and applying all pre-requisites .

Have a nice week-end.

Best regards

Manjunath

[MariusR]

Hi everyone. I have been battling with this same issue for a while, reading up on just about every solution available.

I have tried it on bare metal ML350gen8, VMware 8.02 and a bare metal home PC. On the home PC it installed fine, but on the others, I get stuck at 93% until time-out

The HPE-VM.log file fails with this error: WARN: Unable to connect to https://vmem-01.local. Trying again in 15 seconds...

Here's the included commands:

• virsh  list  --all
• virsh net-list  --all
• ip  a

mariusr@vmehost1:/var/log/hpe-vm$ virsh  list  --all

 Id   Name   State

--------------------

mariusr@vmehost1:/var/log/hpe-vm$ virsh net-list  --all

 Name         State    Autostart   Persistent

-----------------------------------------------

 Management   active   yes         yes

mariusr@vmehost1:/var/log/hpe-vm$ ip  a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host

       valid_lft forever preferred_lft forever

2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq master ovs-system state UP group default qlen 1000

    link/ether 00:50:56:82:2f:b1 brd ff:ff:ff:ff:ff:ff

    altname enp2s1

    inet 192.168.11.65/20 brd 192.168.15.255 scope global ens33

       valid_lft forever preferred_lft forever

3: ens34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000

    link/ether 00:50:56:82:b5:cf brd ff:ff:ff:ff:ff:ff

    altname enp2s2

    inet 192.168.17.65/24 brd 192.168.17.255 scope global ens34

       valid_lft forever preferred_lft forever

    inet6 fe80::250:56ff:fe82:b5cf/64 scope link

       valid_lft forever preferred_lft forever

4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

    link/ether a6:18:72:f9:2c:2d brd ff:ff:ff:ff:ff:ff

5: mgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UNKNOWN group default qlen 1000

    link/ether 00:50:56:82:2f:b1 brd ff:ff:ff:ff:ff:ff

    inet 192.168.11.65/20 brd 192.168.15.255 scope global mgmt

       valid_lft forever preferred_lft forever

    inet6 fe80::250:56ff:fe82:2fb1/64 scope link

       valid_lft forever preferred_lft forever

Your help will be greatly appreciated

[pkbin]

Hi  @MariusR   

It seems the CPU virtualization (Intel VT-x or AMD-V)  not enabled at the hardware level. Could you please execute the below command and let us know the output please.

#kvm-ok

#nslookup vmem-01.menm.co.za

#nslookup 192.168.11.65

Anyway , I would appreciate , if you could create a new thread, as this thread is already marked issue resolved.
Thanks

[MariusR]

Thank you,

Indeed the VMware's "Expose hardware assisted virtualization to the guest OS" was not switched on

Regards

Marius


[www.datacentrix.co.za]<>
Marius Redelinghuys
Solution Architect
Enterprise Business Unit
**personal info erased**

www.datacentrix.co.za<>

[pkbin]

@MariusR   Thank you for this update. I am glad that, I was helpful here.  If the issue has been resolved,  kindly give Kudos and mark my post as Accepted Solutions.  
Thanks & Regards,