HPE VM Essentials installation, Reconfiguring morpheus fails at 75%, unable to boot vm

[se7]

I'm trying to install hpe vm essentials but running into problems in the configuration:

I've already installed the .deb package with the pre-requisite packages without error.

I have following:

• ens18, static ip: 192.168.1.246/24, vlan access 100 (not trunk)
• ens19, dhcp, vlan access 100 (not trunk)
• dns server: 192.168.1.203 (dns record hpe-vme.local pointing to 192.168.1.246)
• virbr0 bridging ens18,ens19 to physical ethernet port (ran on a nested vm, it has internet access)

configuration im trying to apply: Imgur: The magic of the Internet

The morpheus install keeps failing at 75%, through research it seems to be the effect of network configuration.

Is there anything obvious im missing or do i need to use tagged vlans for vme?

Appreciate the help!

[DiegoDelgado]

Hello,

can you check in the CLI of the host if the VM is getting started? You can do it by:

- checking for VM status with "virsh list --all"

- Checking if you can ping the VM either from your host or an external system

If you can ping the VM Essentials manager VM, you should SSH to it and do the following:
The actual issue is caused because the /etc/resolv.conf is just a symlink to
/run/system/resolve/stub-resolv.conf, removing this symlink and pointing it
to /run/system/resolve/resolv.conf solves the name resolution issue.
Steps to solve (run as root):
1. Remove original symlink: rm -f /etc/resolv.conf
2. Create new symmlink: ln -s /run/system/resolve/resolv.conf
/etc/resolv.conf
3. Check if the linking worked: ls -l /etc/resolv.conf
a. You should see something similar to: lrwxrwxrwx 1 root root 31
Feb 13 08:15 /etc/resolv.conf -> /run/system/resolve/resolv.conf
Note: Do you run random commands as root as pointed out by a random

The issue is caused because Ubuntu doesn't really like the .local domains, they are not reserved for internet, but they have special semantics. If this is a lab (and it seems so from your post), try creating a .com domain or something similar and use that one, otherwise, you can just use IPs without any FQDNs everywhere and move forward with them, just be carefull to add your IP to the URL in the bootstrapper (https://<your-ip>)

[AmitBiswas]

Hi,

Can you check the logs of /var/log/hpevm, this will show the reason for failure or if the VM is created.

[se7]

I managed to get another "error" when typing noproxy in both fields where proxy is mentioned as the previous log kept nagging about no proxy serverbeing listed, the hpe vm log file now only says the following:

2025-03-04 09:32:26 INFO: Running hpe-vm in interactive mode
2025-03-04 09:33:17 INFO: Preparing KVM
2025-03-04 09:33:57 ERROR: Unable to start vm hpe-vme:

2025-03-04 09:38:28 INFO: Running hpe-vm in interactive mode
2025-03-04 09:38:50 INFO: Running hpe-vm in interactive mode
2025-03-04 09:39:58 INFO: Preparing KVM
2025-03-04 09:40:38 ERROR: Unable to start vm hpe-vme:

I feel like scrapping the dns record and just running ip for now before getting a domain set up. I reverted the symlink and put in my local dns again and can freely access the internet on the ubuntu vm without errors.

Im currently putting in this: Imgur: The magic of the Internet
Is this correct or do i need to alter the hostname in some form since its ip adress?

virsh list --all
Id Name State
--------------------------
- hpe-vme shut off

2025-03-05 15:07:25 INFO: Running hpe-vm in interactive mode

2025-03-05 15:09:12 INFO: Preparing KVM
2025-03-05 15:11:27 ERROR: Unable to start vm hpe-vme:

Is there any other log file i can check for issues? I cant for the life of me figure out what is thats failing if the log is empty, the log file doesnt give any eror code to why it does start either.

[pkbin]

Hi @se7 

Can you start the VM manually and let us know the error

#virsh start hpe-vme

[se7]

error: Failed to start domain 'hpe-vme'
error: Requested operation is not valid: network 'Management' is not active

virsh # virsh net-list
error: unknown command: 'virsh'
virsh # net-list
Name State Autostart Persistent
----------------------------------------

I guess this shouldnt be empty...

Just to clarify so i understand correctly:

Do i need to preconfigure the network in the configure host part when doing sudo hpe-vm? (i feel like this didnt make any difference...)

Can i not make ens18 the management interface or does it need to be a virtual interface? I'm not very experienced regarding hypervisors, generally i've always had everything automatically done in an installer which hpe vme lacks..

virsh # net-info
error: command 'net-info' requires <network> option
virsh # net-info --network
error: expected syntax: --network <string>
virsh # net-info --network
Compute default Management
virsh # net-info --network
Compute default Management
virsh # net-info --network Management
Name: Management
UUID: 2ef834e5-f321-4665-ad75-6709302d6e29
Active: no
Persistent: yes
Autostart: yes
Bridge: mgmt

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: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether bc:24:11:ce:6d:c8 brd ff:ff:ff:ff:ff:ff
altname enp0s18
inet 192.168.1.246/24 brd 192.168.1.255 scope global ens18
valid_lft forever preferred_lft forever
inet6 fe80::be24:11ff:fece:6dc8/64 scope link
valid_lft forever preferred_lft forever
3: ens19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether bc:24:11:ca:78:f5 brd ff:ff:ff:ff:ff:ff
altname enp0s19
inet 192.168.1.27/24 metric 100 brd 192.168.1.255 scope global dynamic ens19
valid_lft 491512sec preferred_lft 491512sec
inet6 fe80::be24:11ff:feca:78f5/64 scope link
valid_lft forever preferred_lft forever

When i type ens18 in the management interface in the hpe-vm installer it should bridge it to "Management" network within the virsh/kvm hypervisor? 

[pkbin · Accepted solution]

If you are running inside virsh prompt then you must run teh commands as below.

virsh# list --all
Virsh# net-info  --all

Anyway looking at the net-info  output, it is showing as not active.  So for some reason it has not setup correctly.

I would suggest to  clean the setup once and try it again
#virsh destroy <VM name>
#virsh  net-destroy Management
#virsh net-destroy Compute
#Virsh net-destroy  default
#/opt/hpe-vm/scripts/reset_host.sh
#apt install  -f ./hpe-vm_1.0.2-1_amd64.deb
#hpe-vm  <== Setup it again.

Please let me know, how this goes.

[se7]

It looks like everythings solved so far.

There was definitely some old configuration stuck from a previous attempt, guaranteed. The reset_host script solved that issue.

Later on i had another issue with the vm having wrong cpu type, running cpu type: host , seems to have resolved the issue.

Never seen another post recommend the reset_host script but it turned out to be a god send.

Thank you all for the help!