Nested installation of VME 8.0.7

[wprather125]

What if I told you... ?

I was posting onto older posts and was advised in the Slack channel to start a new thread to get eyes on this.  I know it's not "supported", but I've working with what I've got and made work for similar testing - so I'm optimistic. 

Working on getting a single-VM instance of VME running in the lab.  ESXi 7 on the host, plenty of CPU/mem/nvme storage.  Single vSwitch/vPortgroup, allowed promiscuous mode, forged transmits, etc on the port group and switch.  Nested Nutanix CE 2.0 runs well and I can power on VMs inside the "host" VM, so I know this *should* work.  I'm stuck attempting to get the installer for the VME Manager installed and then be able to successfully connect a VM (guest) to the network.  I figured out how to do storage - but the network is still snagging me.  Even if I get the VME Manager/Console installed and an OVS port group created on a pre-configured bond0, the guest VMs can't talk.  Note: Everything runs local on the VME "host", technically a "worker node" which also runs the VME Manager.  Since there are no "VLANs" in my lab, every uplink is access mode, so I've tried "0" and "1" in the field for the Compute VLAN on the bond0 interface with no luck.  Can I do this without a OVS port group and just use ens224,ens256,or ens161 from the screenshots below and get a guest VM running?  Thanks in advance for any assist.  Screenshots of my inputs and experience below...   

Netplan YAMLIP ADDRSYSINFOMEDIAOptions-nettagging VLAN 0tagging VLAN 1result (I can get it to install with only 1 nic connected, but no Compute network)Ping no workieResult-fail

I hope this helps someone - mainly me!    Putting it in 4-wheel-drive to get this science project running!  Cheers!

Thanks to @Arnout_Verbeken for his initial helpful advice, and shout out to @CalvinZito for the pointers to here.

[PeterTzvetanov]

I would recommend to send a mail to the hpe-sw-trial-vmessentials@hpe.com and we will have a look together. You can add me(Peter.Tzvetanov@hpe.com) into the mail in cc.

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

[JyrkiKilpinen]

About similar setup, only differences that we use wlans.
On 8.0.7 setup, if you chose Use compute VLAN, we got similar behaviour. Just ignore it during installation, and create later when things are up.
So management interface in our case is bond0 + vlan, you should use bond0, if thats where your management network is.

[wprather125]

Thanks, @PeterTzvetanov for the advice.  I've done just that.  In the meantime, I've commandeered a physical server to also play with, but due to the lack of tagged interfaces in my lab I am still confused about how to set up the Compute network.  I've been told to install without a compute network (management only), then set up the compute network after the fact.  How does one reconfigure it?

[PeterTzvetanov]

Hi Wes,

as talked the last time, ping me via Teams or mail and we will come together once you have time to check the compute network and also to apply the settings and the install on the baremetal system.

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

[wprather125]

Thank you to Peter for his help.  We were able to make the nested configuration work with a single access-mode uplink.  (no tags)

Super-Time-Saver (before you start typing sudo blah blah blah over and over...)

sudo -i

Some helpful commands I learned for cleaning up...

virsh list --all

virsh undefine vme

virsh net-list --all

virsh net-undefine Management

virsh net-undefine Compute

virsh net-destroy default

virsh net-undefine default

ovs-vsctl show

Handy Cleanup Commands: (for starting over)

cd /var/morpheus/kvm/

cd config/

rm *

ls

cd ../local/

rm *