The first 4GB disk is the installation partition.
The seccond 6GB disk you need to resize before power-on the VM and do the installation.
Don't change the second disk size after installation.
For the recommend deployment size / disk size see the installation guide. 10GB is fine for a MM-VA-500 deployment.
------------------------------
Marcel Koedijk | MVP Expert 2022 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
------------------------------
Original Message:
Sent: Jan 09, 2023 02:06 PM
From: Pasquale Monardo
Subject: Virtual mobility conductors - 8.10.0.5
On the topic of a virtual MCndr...the installation guide says you need a minimum of 8Gb disk space for an MM-500 but when loading up the OVA, there are two disks, one is 4Gb and the is 6Gb....page 11 - table 4.
Besides upping the vCPU and RAM to meet the minimum criteria for an MM-500, what am I supposed to do with the disks?
The guide mentions only 1 disk but the OVA provisions 2 of them....
Original Message:
Sent: Jan 02, 2023 05:16 AM
From: marcel koedijk
Subject: Virtual mobility conductors - 8.10.0.5
Hi Richard,
The simple answer is that only VMware/Hyper-V/KVM are supported.
https://www.arubanetworks.com/techdocs/ArubaOS-8.x-Books/810/ArubaOS-8.10.0.0-Virtual-Appliance-Installation-Guide.pdf
------------------------------
Marcel Koedijk | MVP Expert 2022 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
Original Message:
Sent: Dec 22, 2022 01:33 PM
From: Richard du Feu
Subject: Virtual mobility conductors - 8.10.0.5
Hi,
I know the supported virtualisation system of choice for Aruba Mobility Conductors is clearly stated as VMWare/ESXi.
Our test environment has been migrated to XenServer so I've been trying to make a Virtual MM work on Xen. Fairly soon after starting the install process when it gets to "Loading Modules" the VM aborts the install and powers off. Before I put a lot of time into this problem does anyone run a virtual MM on Xen rather than VMware or is this more a case of doesn't work rather than not supported?
Obviously for production we're sticking with VMWare as the supported platform!
Many thanks,
Richard