5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Well, in fact you could even move the file with the help of WinSCP to your preferred directory instead of calling support ;)
Just to inform everybody here, single deleted vdisks are sent to recycle bin.
Allright!
Hello JeroenTielen, the VM has not been deleted, only one disk of this specific VM. So, how about this? Regards.
Hello bcaballero, that’s how it looks like in Volume Group … I suppose that in this case the disk of a specific VM cannot be recovered, right? Regards!
Hello Moustafa,yes, that’s what I read about deleting VMs, but I did not delete VMs, I just moved them from one to another container, more than 24 hours have past, but not a single byte has been reclaimed so far.I will let pass the upcoming weekend and check on monday again.Remember I have not deleted VMs, I just have fully moved them to another container and the old container did not drop in space usage so far.Regards,Didi7
Of course those pre_freeze/post_thaw scripts are fake, but as long as the Windows 10 VM just acts as let’s say a file-server, it is still application or OS consistent.In VMware vSphere you just need VMware Tools and no scripts to create application consistent snapshots (of course as long as there is no specific application) for Windows client VMs, like Windows 10, depending on the backup software.Veeam B&R has its own proprietary AAIP integration to create app consistent snapshots being independent from VMware Tools, when using vSphere as Hypervisor.
Ok, it works now for Windows 10 using pre_freeze.bat and post_thaw.bat in e.g. C:\Program Files\Nutanix\scripts with contents … @echo offver Funny!
Hello Sergei, app consistent snapshot backups with Windows Servers work perfectly, as long as NGT is installed and activated on the VM and the relevant Protection Domain exist. In other words, to have the same effect on e.g. Windows 10 you need to create a pre_freeze.bat and post_thaw.bat script like the following … @echo offver Is it that simple? We don’t need to shutdown any services on those specific VMs. Strange that this does work on Windows Server without those scripts but not on Windows 10. Regards,Didi7
Is there any official statement what version of NFS is supported with VMware on Nutanix now that AOS 5.20.x was released already? Any Nutanix employee that can make an official statement?
Hello Alona, thanks for letting me know. Well, I will open a case for both locations where we have this stale entry problems. Please get in contact with your software engineers, so that end users can delete such entries from the Prism Element GUI themselves or via CVM commands at least through a knowledge base article. It’s annoying to open support cases for such trivial things. Thank you,Didi7
As far as I heard it is now part of AOS 5.19 but not part of the UI directly. Maybe in an LTS build later.
Well, you can change the resolution in the UEFI-BIOS but as soon as you power off the VM the old resolution of 1280x1024 is back.Good luck!
Not that I know of :(
Hi Alona,we use RF2 in all our Nutanix clusters. I can see those figures by clicking Home => Hardware => Table => Disk (Prism Element) …There I can see, that 531.82 GiB are useable from a 960GB SSD, same in another cluster, where we have 1.92 TB SSDs (instead of 960GB) and there the usable size is 1.22TB.Now I would like to know how much space is available from a 3.84TB SSD, the percentage of ususable space from different SSDs differ a lot.
Near future sounds always good!
Hello. I have long been looking for a solution to this problem. Thank you for guide! Me too! Is there any nutanix work in progress to do it as a container live migration? Hello Nutanix, is there any plan to allow live vm migrations between storage containers? This is a much appreciated feature! Thanks for any clarification!
Hi Sudhir, interesting! Well, other Hypervisors like Hyper-V and VMware have no display resolution change problems with UEFI-VMs under Windows Server 2016. Lets see how Nutanix can fix that! Regards, Didi7
Ok, I continued my tests on UEFI-firmware based Windows 2016 VMs and finally found out, that display resolution in Windows 2016 VMs only changes, when changing the default resolution in UEFI-firmware and only if you enter UEFI-firmware configuration after a reboot and exit. The display resolution changes to the one you choose in UEFI-firmware. As soon as you power off the Windows Server 2016 VM again, the display resolution returns to 1280x1024 again and cannot be changed within Windows. If you reboot (not power off) the Windows 2016 VM, enter UEFI-firmware with F2 and exit again, the display resolution changes again to the one you chose in Nutanix UEFI-firmware settings. That’s what I call annoying and should be changed from Nutanix asap, but maybe I am the only one claiming it’s annoying, at least in our company several users find it annoying. Any comments from Nutanix are welcome! Regards, Didi7
Quote: Would it be correct to say that the issue you are experiencing is when connecting to the VM by using “Launch console” feature in Prism? Yes absolutely, but as long as there is no network connection, one is forced to use the VNC Console until everything is setup and I am talking about VM-template generation, where there are no network connections availaible, as here they stay disconnected. Updates, like Cumulative Updates in Windows Server 2016 are done via ISO medias. After syspreping and cloning those VM-templates, they get connected to networks and then RDP is used of course. I really know a lot of Hypervisor platforms and have 15 years of experience with VMware and the likes, but never had any problems to change the display resolution via the console, even if it’s only 640x480 and a change to 800x600 is only possible, but that I am forced to change the display resolution in the UEFI-firmware and that display resolution change within Windows is no longer possible, is uniqu
Changing resolution within UEFI-configuration is possible but has no effect during installation. The whole installation process of a Windows VM can only be done with 1280x1024, so you are forced to use big monitors to succeed with the installation of Windows Server 2016 and as you cannot change the resolution during installation, you are also stuck at 1280x1024, when Windows is fully installed and Nutanix Guest Tools, as well as VirtIO drivers are installed. Really, that’s so annoying and really not resonable to customers. Might be fixable with an Nutanix display driver, don’t know? Using non-UEFI VMs during installatation of Windows Server 2016 results in the same Monitor and display driver, but you can change resolutions. Is there a solution from Nutanix available or is this a known bug? Does there exist a work-around?
Hello Alona, no it is not within the UEFI configuration, you are stuck at display resolution 1280x1024 within Windows OS.
[quote=Jon]That and never making more vCPUs (regardless of how you do it) in a single VM, than there is physical cores in any given system.[/quote] Didn't you want to say … That and never making more vCPUs (regardless of how you do it) in a single VM, than there is physical CPU sockets in any given system. ??? Nutanix should make this more clear in their documentation, cause I just found the upper … [url=https://next.nutanix.com/server-virtualization-27/ahv-vcpu-vs-vcores-18216][u]https://next.nutanix.com/server-virtualization-27/ahv-vcpu-vs-vcores-18216[/u][/url] ... thread regarding the use of vCPUs and Cores in a Nutanix VM. IMO, you should point out more, that it's not recommended to put more vCPUs instead of Cores into a Nutanix VM, when there is only one or two physical CPU sockets. Regards, Didi7
Hello ddubuque, just saw this ... [url=https://next.nutanix.com/server-virtualization-27/ahv-vcpu-vs-vcores-18216]https://next.nutanix.com/server-virtualization-27/ahv-vcpu-vs-vcores-18216[/url] ... and thought, how about Nutanix nodes that only have 1 CPU socket. Before we migrated to Nutanix, we used to have a lot of VMware ESXi hosts with not more than 2 CPU sockets and there to me it only made sense to use not more that 2 vCPUs per VM, which resulted in a 4 CPU-machine be configured with not more than 2 vCPUs and 2 Cores or 1 vCPU with 4 Cores but in no case more than 2 vCPUs, as the ESXi host only had 2 CPU sockets. Then I saw the upper mentioned Nutanix forum thread and thought, maybe Nutanix sees it different but the question, whether it makes sense to also use more than 1 CPU socket, if you only have 1 CPU socket available in one node, wasn't answered completely. Nevertheless, I agree with you. Best regards, Didi7
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.
