Step 5 : Now we will Shutdown the Nutanix AHV host. If you want to do this manually, VMware has a knowledge base article that describes the process here: In addition to the CVM the AHV host itself has its own maintenance mode. End AHV Host Maintenance Mode. If you are running VMware ESXi or Microsoft Hyper-V you are done here. *-flat.vmdk” -exec basename {} \;) vmdkname=$(find -name “*ce-*.*. This will allow the installation to complete even though you only have 12 GB of physical memory available. If you go to the ACLI and run a host.list you see that the host is not schedulable … Add the existing ce-2019.02.11.vmdk file as SCSI0:0, Change the SCSI controller to type VMware Paravirtual SCSI Adapter (PVSCSI). Edit the /home/install/phx_iso/phoenix/svm_template/kvm/default.xml file using for example command “vi”. Minimum 16 GB memory (you must really have a minimum 16 GB physical memory available if not this can be solved: After deployment, do not start the installation. 2.) Steps prior to bring down host :1) Ensure that the “Data Resiliency – Status” is Normal in PRISM Portal for the target Cluster.2) Migrated all the user VMs (except CVM) residing in the target ESXi host to other healthy nodes part of the cluster.3) Connect the CVM via SSH and find its UUID using below mentioned command. In case of AHV go on with step 2. Sure unless somehow you manage to fat finger the root ESXi password twice on one of the three hosts. We also get your email address to automatically create an account for you in our website. Deploying the Nutanix Community Edition (CE) on nested ESXi can be slightly tricky, but in this blog post, I will guide you through the process in just a few easy steps with the help of a script I have produced. Log in, Click to share on Twitter (Opens in new window), Click to share on Facebook (Opens in new window), Nutanix: Error – Foundation service running on one of the nodes, HP Data Protector: How to stop a hanging session (Windows). Instead, log in using root / nutanix/4u, Edit the /home/install/phx_iso/phoenix/ file. Upload the ce-2019.02.11-flat.vmdk file to the newly created folder. Modify network adapter to VMXNET3 and connect it to the appropriate port group. Once your account is created, you'll be logged-in to this account. Run this command to reboot the ESXi host: [root@esxi]# esxcli system shutdown reboot -r 'replace driver' Ensure that the correct driver downgrade is successful and the correct version is running using this command on the ESXi host command line: [root@esxi]# esxcli software vib get -n For example: [root@esxi]# esxcli software vib get -n ixgben. VMCE practice exam – Veeam Certified Engineer, Unpack the ce-2019.02.11-stable.img.gz file (the expected result is the file ce-2019.02.11-stable.img), Rename the ce-2019.02.11-stable.img file to ce-2019.02.11-flat.vmdk, Create a virtual machine configuration (VMX) file with correct settings. Search for rhel7.3.0 by using /rhel7.3.0 then replace it with rhel7.2.0 and save the file. Create a thin-provisioned 500 GB VMDK to be used for the Nutanix cold tier; Create a virtual machine configuration (VMX) file with the correct settings; Register the new virtual machine with your ESXi host; Once the VM boots up, you will need to: Select the second option in the boot menu (rescue) Login using. After successfully shutdown the Nutanix CVM, now we can continue to shutdown/power off the Nutanix AHV host. When you login first time using a Social Login button, we collect your account public profile information shared by Social Login provider, based on your privacy settings. *-flat.vmdk”), if [ -z “$vmdkpath” ] then echo “Unable to locate Nutanix CE image… aborting” else echo % Located Nutanix CE image and setting up variables vmdkflatname=$(find -name “*ce-*.*. Rename it from ce-2019.02.11-flat.vmdk to -flat.vmdk, Creating the missing disk descriptor file and a temporary -flat.vmdk file, Move the new disk descriptor file to the virtual machine folder, Create a thin-provisioned 200 GB VMDK to be used for the Nutanix hot tier (this virtual disk will be marked as a virtual SSD), Create a thin-provisioned 500 GB VMDK to be used for the Nutanix cold tier, Create a virtual machine configuration (VMX) file with the correct settings, Register the new virtual machine with your ESXi host, Select the second option in the boot menu (rescue), Change directory to /var/cache/libvirt/qemu/capabilities/, Edit the only XML file inside the /var/cache/libvirt/qemu/capabilities/ folder using for example command “vi”. 2019-03-18 by Rasmus Haslund Leave a Comment. Create a folder on your target datastore with the same name as you would like the virtual machine to be named. root@ahv# shutdown -h now. Connect to your ESXi host using SSH and execute the script. However, some features such as compression/deduplication will have insufficient memory so beware! *-flat.vmdk” -exec basename {} \; | sed ‘s/.\{10\}$//’) vmdksize=$(ls -nl $vmdkpath | awk ‘{print $5}’) vmdktempfolder=$(find -name “*ce-*.*. If you have difficulties following the KB article or just prefer to have this automated, then you can use this script: # Set variables to locate the Nutanix CE image you have uploaded and renamed to -flat.vmdk cd /, vmdkpath=$(find -name “*ce-*.*. Look for the domain type = kvm section and find the sub-section that looks like: Once you get to the login prompt, simply enter as username: From here the process is straight forward. *-flat.vmdk” -exec dirname {} \; | sed “s|^\.||”)/temp vmdkfolder=$(echo $vmdktempfolder | sed ‘s/.\{4\}$//’) vmname=$(basename $vmdkfolder) vmdkdisk1=$(echo $vmname\_1.vmdk) vmdkdisk2=$(echo $vmname\_2.vmdk), echo % Renaming Nutanix CE image mv $vmdkpath ${vmdkfolder}${vmname}-flat.vmdk, echo % Creating temporary working folder mkdir $vmdktempfolder, echo % Creating new disk descriptor file and temporary -flat.vmdk file vmkfstools -c $vmdksize -d thin $vmdktempfolder/$vmname.vmdk, echo % Deleting temporary -flat.vmdk file rm $vmdktempfolder/${vmname}-flat.vmdk, echo % Moving new disk descriptor file to same folder as the uploaded nutanix ce image mv $vmdktempfolder/$vmname.vmdk $vmdkfolder, echo % Removing temporary working folder rmdir $vmdktempfolder, echo % Creating 200 GB virtual SSD hot tier VMDK – thin provisioned vmkfstools -c 214748364800 -d thin $vmdkfolder$vmname\_1.vmdk, echo % Creating 500 GB HDD cold tier VMDK – thin provisioned vmkfstools -c 536870912000 -d thin $vmdkfolder$vmname\_2.vmdk, echo % Creating VMX file with customized settings vmxnvram=$(echo $vmname.nvram) cat <> $vmdkfolder/$vmname.vmx .encoding = “UTF-8” config.version = “8” virtualHW.version = “13” nvram = “$vmxnvram” pciBridge0.present = “TRUE” svga.present = “TRUE” pciBridge4.present = “TRUE” pciBridge4.virtualDev = “pcieRootPort” pciBridge4.functions = “8” pciBridge5.present = “TRUE” pciBridge5.virtualDev = “pcieRootPort” pciBridge5.functions = “8” pciBridge6.present = “TRUE” pciBridge6.virtualDev = “pcieRootPort” pciBridge6.functions = “8” pciBridge7.present = “TRUE” pciBridge7.virtualDev = “pcieRootPort” pciBridge7.functions = “8” vmci0.present = “TRUE” hpet0.present = “TRUE” floppy0.present = “FALSE” numvcpus = “4” memSize = “16384” bios.bootRetry.delay = “10” powerType.powerOff = “default” powerType.suspend = “soft” powerType.reset = “default” tools.upgrade.policy = “manual” sched.cpu.units = “mhz” sched.cpu.affinity = “all” sched.cpu.latencySensitivity = “normal” vm.createDate = “1552034628071900” scsi0.virtualDev = “pvscsi” scsi0.present = “TRUE” sata0.present = “TRUE” svga.autodetect = “TRUE” scsi0:0.deviceType = “scsi-hardDisk” scsi0:0.fileName = “$vmname.vmdk” sched.scsi0:0.shares = “normal” sched.scsi0:0.throughputCap = “off” scsi0:0.present = “TRUE” scsi0:1.deviceType = “scsi-hardDisk” scsi0:1.fileName = “$vmdkdisk1” scsi0:1.virtualSSD = 1 sched.scsi0:1.shares = “normal” sched.scsi0:1.throughputCap = “off” scsi0:1.present = “TRUE” scsi0:2.deviceType = “scsi-hardDisk” scsi0:2.fileName = “$vmdkdisk2” sched.scsi0:2.shares = “normal” sched.scsi0:2.throughputCap = “off” scsi0:2.present = “TRUE” ethernet0.virtualDev = “vmxnet3” ethernet0.networkName = “VM Network” ethernet0.addressType = “generated” ethernet0.wakeOnPcktRcv = “FALSE” ethernet0.present = “TRUE” sata0:0.deviceType = “atapi-cdrom” sata0:0.fileName = “/vmfs/devices/cdrom/mpx.vmhba64:C0:T0:L0” sata0:0.present = “TRUE” displayName = “$vmname” guestOS = “other-64” vhv.enable = “TRUE” bios.bootDelay = “5000” toolScripts.afterPowerOn = “TRUE” toolScripts.afterResume = “TRUE” toolScripts.beforeSuspend = “TRUE” toolScripts.beforePowerOff = “TRUE” tools.syncTime = “FALSE” uuid.bios = “56 4d fe 2a 63 f7 10 22-a1 84 e7 d8 2f 20 6e 23” uuid.location = “56 4d fe 2a 63 f7 10 22-a1 84 e7 d8 2f 20 6e 23” uuid.action = “create” vc.uuid = “52 c0 0c 4c 3b a9 bb 9d-05 aa 9b ba 72 31 f0 80” sched.cpu.min = “0” sched.cpu.shares = “normal” sched.mem.min = “0” sched.mem.minSize = “0” sched.mem.shares = “normal” EOT, vim-cmd solo/registervm $vmdkfolder/$vmname.vmx, Thanks to Jorge de la Cruz for the awesome guide in Spanish, make sure you check out his blog post for additional screenshots, Filed Under: Nutanix Tagged With: ce, community, edition, nutanix.