VME installation stuck at 99% - Webserver does not start

[Kees51]

I am trying to install the VME manager on a DL360 Gen9. The installation stalls at 99% and after an hour I get the error Failed to start VME Manager services: Timed out waiting for morpheus appliance. I tried it on the HPE minimal Ubuntu server install and on a standard server install downloaded from the Ubuntu site.

The virtualization functions of the processor are enabled. On the same server ESXi worked fine. I used sudo hpe-vm.

In the instructions it says the website should be available when it says 'Starting VME Manager services' but it isn't.

The command virsh list works after exiting out of hpe-vm, of course listing no vm's, so it seems at least KVM is (still) working.

The network is not bonded, I have three ports connected: management, production, storage. At the moment I do not have equipment available in my home lab to do bonding.

In the hpe-vm.log it says

2025-11-20 12:38:07 INFO: Running hpe-vm in interactive mode
2025-11-20 12:40:33 INFO: Preparing KVM
2025-11-20 12:40:34 INFO: Management network does not exist, configuration using: eno1
2025-11-20 12:40:36 INFO: morph local storage pool defined: true
2025-11-20 12:40:36 INFO: morph local storage pool set to autostart: true
2025-11-20 12:40:36 INFO: morph local storage pool startup: true
2025-11-20 12:41:15 WARN: context [anonymous] 8:24 attribute nopasswd isn't defined
2025-11-20 12:41:15 WARN: context [anonymous] 21:4 attribute proxyHost isn't defined
2025-11-20 12:41:15 WARN: context [anonymous] 30:11 attribute noProxy isn't defined
2025-11-20 12:41:15 WARN: context [anonymous] 35:4 attribute proxyHost isn't defined
2025-11-20 12:41:15 WARN: context [anonymous] 36:11 attribute noProxy isn't defined
2025-11-20 12:41:15 WARN: context [anonymous] 43:11 attribute installWorker isn't defined
2025-11-20 12:41:41 WARN: Unable to connect to https://192.168.10.18/ping. Trying again in 15 seconds...
java.net.ConnectException: Connection refused

The connection refused message is repeated many many times. No other messages in the log.

Is bonding a hard requirement for the management website? Is there another log I could look at that maybe says what is wrong?

[jagan3]

Even I have faced same issue. it's stuck at 99% . Do we need to specify the different nic for the ip configuration. But it's litsted default nic which is up. 

[pkbin]

@Kees51  May I know the VME version  that you are trying to install ?
Also provide the below outputs from the host where you are running hpe-vm to providion the morpheus VM
#ping 192.168.10.18
#virsh list --all
#virsh net-list --all
#ovs-vsctl show
#ip  a

[Kees51]

@pkbin I am trying to install v8.0.10. I tried it two times. Running on the HPE version of Ubuntu minimal.

kees@ens01:~$ ping 192.168.10.18
PING 192.168.10.18 (192.168.10.18) 56(84) bytes of data.
64 bytes from 192.168.10.18: icmp_seq=1 ttl=64 time=0.048 ms
64 bytes from 192.168.10.18: icmp_seq=2 ttl=64 time=0.036 ms
^C
--- 192.168.10.18 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1026ms
rtt min/avg/max/mdev = 0.036/0.042/0.048/0.006 ms

kees@ens01:~$ sudo virsh list --all
Id Name State
------------------------
- ens01 shut off
- èns01 shut off

kees@ens01:~$ sudo virsh net-list --all
Name State Autostart Persistent
-----------------------------------------------
default active yes yes
Management active yes yes

kees@ens01:~$ sudo ovs-vsctl show
5400f4af-9a85-4a09-93c4-2a3803b45e1f
Bridge mgmt
fail_mode: standalone
Port mgmt
Interface mgmt
type: internal
Port eno1
Interface eno1
ovs_version: "3.3.4"

kees@ens01:~$ 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000
link/ether 94:57:a5:5c:ac:a4 brd ff:ff:ff:ff:ff:ff
altname enp2s0f0
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 94:57:a5:5c:ac:a5 brd ff:ff:ff:ff:ff:ff
altname enp2s0f1
inet 192.168.179.7/24 brd 192.168.179.255 scope global eno2
valid_lft forever preferred_lft forever
inet6 2a02:a44f:a1ef:2:9657:a5ff:fe5c:aca5/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 6740sec preferred_lft 3140sec
inet6 fe80::9657:a5ff:fe5c:aca5/64 scope link
valid_lft forever preferred_lft forever
4: eno3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 94:57:a5:5c:ac:a6 brd ff:ff:ff:ff:ff:ff
altname enp2s0f2
5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 94:57:a5:5c:ac:a7 brd ff:ff:ff:ff:ff:ff
altname enp2s0f3
6: ens1f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000
link/ether 1c:98:ec:5c:ba:c0 brd ff:ff:ff:ff:ff:ff
altname enp8s0f0
inet 172.16.10.19/24 brd 172.16.10.255 scope global ens1f0
valid_lft forever preferred_lft forever
inet6 fe80::1e98:ecff:fe5c:bac0/64 scope link
valid_lft forever preferred_lft forever
7: ens1f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 1c:98:ec:5c:ba:c8 brd ff:ff:ff:ff:ff:ff
altname enp8s0f1
8: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether da:06:78:9a:4a:60 brd ff:ff:ff:ff:ff:ff
9: mgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 94:57:a5:5c:ac:a4 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.18/24 brd 192.168.10.255 scope global mgmt
valid_lft forever preferred_lft forever
inet6 2a02:a44f:a1ef:1:9657:a5ff:fe5c:aca4/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 7081sec preferred_lft 3481sec
inet6 fe80::9657:a5ff:fe5c:aca4/64 scope link
valid_lft forever preferred_lft forever
10: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:5f:ff:b6 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
kees@ens01:~$

eno1 is the interface that I gave 192.168.10.18 to. I see the network configuration has been changed by the installer. It has created a mgmt interface and moved the IP number there. The eno2 is meant for the traffic of the VM's and ens1f0 is meant for the storage. Those were not changed.

It is very strange that there are two VM's in the virsh list. The second one has an accent aigu on the e.

Thank you for your time!

[pkbin · Accepted solution]

Thanks for providing the information.

I see the IP "192.168.10.18" is already assigned to the host. Then why you are specifying teh same IP address to the VME manager applaince  VM ( via hpe-vm ) ?? You must specify a unique IP to the VME manager appliance VM ( same subnet)  while provisoing the applince VM.

Please follow the below details.
#virsh undefine  ens01  <== make sure 'virsh list --all' doesn't list any VMs
#rm /var/morpheus/kvm/local/hpe-vm*

// now provision the morpheus appliance VM
#hpe-vm  => Install VME manager ->  Specify the unique IP addresse for the VME manager VM => Also unique name => .. .. ...  ( specify eno1 as management interface)

// Let me know if this helps!

Still issue ? we can have a remote session to check on this. Kindly send an email to "hpe-sw-trial-vmessentials@hpe.com" . We can then send meeting ivite to have a remote session to fix this issue

[pkbin]

@jagan3 I would appreciate, if you could provide the same details in a separate thread, so that we can look in to it.  Issue can be different from site to site. Alternatively you can send email to hpe-sw-trial-vmessentials@hpe.com for assistance

[Kees51]

@pkbin Thank you very much for your quick reply! For some reason I had not understood that the manager would be a VM. I thought the manager would be installed into the Ubuntu install itself. Thats why I entered the same number. Now that I gave a new unused IP number to the manager install it finished successfully and the manager web page is there.

Thanks again!

[pkbin]

Hi @Kees51 ,

Thank you for the update. I’m glad to hear that the issue has been resolved.

Since the issue has been resolved, kindly mark this thread as closed and don't forget to give 'kudos'  if you are happy with the reolution provided.