5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
I would like to learn this as well. I think it is not supported on AHV. Here is what i found so far, [url=https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements]https://docs.microsoft.com/en-us/windows/security/identity-protection/credential-guard/credential-guard-requirements[/url] [h2]Hardware and software requirements[/h2]To provide basic protections against OS level attempts to read Credential Manager domain credentials, NTLM and Kerberos derived credentials, Windows Defender Credential Guard uses: [list] [*]Support for Virtualization-based security (required) [*]Secure boot (required) [*]TPM 1.2 or 2.0, either discrete or firmware (preferred - provides binding to hardware) [*]UEFI lock (preferred - prevents attacker from disabling with a simple registry key change) [/list] [url=https://portal.nutanix.com/#/page/docs/details?targetId=AHV-Admin-Guide-v51:vmm-vm-driver-types-r.html]https://portal.nutanix.com/#
FYI - FortiGate published KB explaining the root cause for some of the FortiStuff failing on Nutanix / KVM. Have a look here - [url=https://kb.fortinet.com/kb/documentLink.do?externalID=FD40080]https://kb.fortinet.com/kb/documentLink.do?externalID=FD40080[/url] This is due to FortiStuff (Manager, Reporter) failing to recognize SCSI disks presented by Nutanix. The trick is to use PCI disk type. Make sure you upload qcow2 image manually on the Node (using Element Manager rather then Central) and drop it to right storage container. PRISM Central will drop the qcow2 image to SelfService and once cloned new appliance will stay on SelfService storage bucket as well! quick KB [url=https://kb.fortinet.com/kb/documentLink.do?externalID=FD40080]FD40080[/url] summary below: ### Since there is no storage and the boot is happening from a read-only qcow2 image, then any changes made to the VM would get lost after the reboot. [u]Solution[/u] The problem is due to the fact that the disk
I assume you are running AHV. Nested virtualisation (VM inside of the VM) is supported starting from AOS 5.5 but need to be specifically enabled. Have a look at this great post - [url=https://next.nutanix.com/server-virtualization-27/how-to-enable-nested-virtualization-on-ahv-18408]https://next.nutanix.com/server-virtualization-27/how-to-enable-nested-virtualization-on-ahv-18408[/url] Read the details about this feature - you will loose some of auto-migration features for this VM and for node running this VM. Another question is if you would like to detonate viruses on the shared platform.
[quote=John_B]Slightly stale topic to add to, but I'll have a go... I'm just going through this with a new Nutanix cluster running AHV 5.6, attempting to build nested ESXi hosts for a lab.[code]... [/code] Ideas?[/quote] Here is some brave soul posting instructions on running ESXi on AHV [url=http://www.automashell.com/nest-vmware-esxi-on-nutanix-ahv/]http://www.automashell.com/nest-vmware-esxi-on-nutanix-ahv/[/url]
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.