HPE VME Morpheous Installation failed at 75%

[monir-gbpl]

HPE VME Morpheous Installation failed at 75% anybody has any idea? what is the issue there?

Getting bellow message is /var/log/hpe-vm

2025-01-02 17:48:31 INFO: Running hpe-vm in interactive mode
2025-01-02 17:58:16 INFO: Running hpe-vm in interactive mode
2025-01-02 18:01:33 INFO: Preparing KVM
2025-01-02 18:01:33 INFO: Management network does not exist, configuration using: eth0
2025-01-02 18:01:34 INFO: morph local storage pool defined: true
2025-01-02 18:01:34 INFO: morph local storage pool set to autostart: true
2025-01-02 18:01:34 INFO: morph local storage pool startup: true
2025-01-02 18:03:17 WARN: context [anonymous] 23:4 attribute proxyHost isn't defined
2025-01-02 18:03:17 WARN: context [anonymous] 24:11 attribute noProxy isn't defined
2025-01-02 18:03:20 ERROR: Unable to start vm vmemanager:

2025-01-02 18:03:52 INFO: Running hpe-vm in interactive mode
2025-01-02 18:05:53 INFO: Preparing KVM
2025-01-02 18:05:54 WARN: context [anonymous] 23:4 attribute proxyHost isn't defined
2025-01-02 18:05:54 WARN: context [anonymous] 24:11 attribute noProxy isn't defined
2025-01-02 18:05:56 ERROR: Unable to start vm vmemanager:

2025-01-02 18:08:35 INFO: Running hpe-vm in interactive mode
2025-01-02 19:03:28 INFO: Running hpe-vm in interactive mode
2025-01-02 19:13:12 INFO: Running hpe-vm in interactive mode
2025-01-02 19:17:58 INFO: Preparing KVM
2025-01-02 19:17:58 WARN: context [anonymous] 23:4 attribute proxyHost isn't defined
2025-01-02 19:17:58 WARN: context [anonymous] 24:11 attribute noProxy isn't defined
2025-01-02 19:18:01 ERROR: Unable to start vm vmemanager:

2025-01-02 19:18:12 INFO: Running hpe-vm in interactive mode
2025-01-02 19:19:28 INFO: Running hpe-vm in interactive mode
2025-01-02 19:21:52 INFO: Preparing KVM
2025-01-02 19:21:53 WARN: context [anonymous] 23:4 attribute proxyHost isn't defined
2025-01-02 19:21:53 WARN: context [anonymous] 24:11 attribute noProxy isn't defined
2025-01-02 19:21:55 ERROR: Unable to start vm vmemanager:

2025-01-02 19:22:30 INFO: Running hpe-vm in interactive mode
2025-01-02 19:23:01 INFO: Running hpe-vm in interactive mode

[Sunitha_Mod]

Hello @monir-gbpl,

Thank you for posting. 

Could you please let us know which HPE product you are referring to? So we can check and move it to the right board. 

[Moto_PK]

This is a networking related issue.

Do you still need assistance?

[pkbin]

Hi @monir-gbpl ,

May I know what exact error you are getting in the VME console ? You can paste the error snippet.

Also kindly share the below outputs to check
#virsh  list  --all
#virsh net-list  --all
#ip  a

Thanks

-  I'm an HPE employee.

[Saajan_d]

Hi Monir,

Please do it from the Scartch.

Steps to be taken care :

in the hpvme interface execute the below commands :

virsh list --all

virsh net-list --all

check whether it is in clear state. if you getting the output details. remove it and make the Server in a fresh state :

by doing the below :

virsh net-destroy <Name1>

similarly what entries you have in the net-list output you can make all of it inactive by executing the above command.

after doing the above do the below steps :

virsh net-undefine <Name1>

will clear the inactive networks. do the same for all the networks in the net-list output.

Next is to update the /etc/hosts with the below format :

<ip-address>   <hostname+domainname>    <hostname>

:wq! >>> save and exit

next is to login with "sudo hpe-vm"

which will come to a HPE VM Console CLI.

here you have to <configure network>

> you have to provide Static IP for the management Interface to be with Static IP Address and you have the compute interface in DHCP

> go to the <morpheus install option>

then Specify the IP Addres of the VM,

Netmask, Gateway, DNS Server (if available), Appliance URL : specify with "https://<hostname+domainname>"

Hostname of the VM, Admin user and its password to login, 

Specify the "Image URL" with "file://<the-path-of-the-image>/image-file"

Specify the proxy if available and also specify the "no proxy" option too if proxy is specified.

Specify the VM Size as "Medium"

Specify the Management Interface

and then go ahead with the "Install" Tab

if still its stuck in 73%, please update

[AmitBiswas]

Please check the Bond and eth0 ip setting looks issue with IP.

[AmitBiswas]

Please share the output of the command

virsh list --all
virsh net-list --all
virsh start < VM name>
ovs-vsctl show
ip a

[Darinm]

i am having a similar issue with a test setup to test the Morpheus software for use in our environment.

We have a DL 360 Gen11, single gold 5415+ CPU 8 cores, 32GB RAM, Single P210tep dual port Ethernet NIC and a SN1610E FC HBA.

I setup the Ubuntu 24.04.2 and upgrade all packages.  Only have a single port on the NIC active as this is only a test system.  If we go active with the software to replace our esisting VMWare environment, we will have the storage on a fibre backend system so NIC's will be only used for the management and the access to the VM.  We also have several seperate vlan's that we use for access to the VM's.

The install of the HPE-VM software when without a hitch, but when i try to setup the management server if fails to start

root@bssc-hp-vm:/var/morpheus/kvm/local# virsh list --all
Id Name State
-------------------------------------
- bssc-hp-management shut off

root@bssc-hp-vm:/var/morpheus/kvm/local# virsh net-list --all
Name State Autostart Persistent
-----------------------------------------------
default active yes yes
Management active yes yes

Management net i had to start manually

root@bssc-hp-vm:/var/morpheus/kvm/local# virsh start bssc-hp-management
error: Failed to start domain 'bssc-hp-management'
error: Cannot get interface MTU on 'mgmt': No such device

root@bssc-hp-vm:/var/morpheus/kvm/local# ovs-vsctl show
545859a4-b8bc-436f-80b4-ab91d89ec4da
ovs_version: "3.3.0"
root@bssc-hp-vm:/var/morpheus/kvm/local# 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 noprefixroute
valid_lft forever preferred_lft forever
2: ens1f0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000
link/ether 04:32:01:b5:94:a0 brd ff:ff:ff:ff:ff:ff
altname enp18s0f0np0
inet 10.56.241.238/24 metric 100 brd 10.56.241.255 scope global dynamic ens1f0np0
valid_lft 85058sec preferred_lft 85058sec
inet6 fe80::632:1ff:feb5:94a0/64 scope link
valid_lft forever preferred_lft forever
3: ens1f1np1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 04:32:01:b5:94:a1 brd ff:ff:ff:ff:ff:ff
altname enp18s0f1np1
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:c6:0f:4b brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever

[CalvinZito]

@Darinm - I suggest you post this as a new discussion. I'm traveling and don't have access to tools to alert my back end team to take a look at this but I think you're more likely to get a response if you post it as a new thread.

[PeterTzvetanov]

Hi Darim,

if you still struggle with the install, send a mail to the hpe-sw-trial-vmessentials@hpe.com and we will see it live in a teams session.

With regards

Peter Tzvetanov

Support Engineer

Peter.Tzvetanov@hpe.com

Technical Support Phone Numbers

HPE Operations

You can manage your cases on HPE Support Center