Nutanix VirtIO 1.1 Drivers Released

If you are a Nutanix customer and using AHV (Acropolis Hypervisor), I have some great news for you. We have released VirtIO 1.1 drivers, and the big deal is that they are now Microsoft WHQL signed. I know the lack of signing was holding back some customers for production workloads. No longer!

VirtIO 1.1And there’s a nice Nutanix install wizard:

Nutanix VirtIOPlease do note, this signed driver package is for 64-bit operating systems only. The supported operating systems are:

  • Windows 7
  • Windows 8.x
  • Windows 10
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016

You can directly download the drivers from here. We have them in both .MSI format and ISO, depending on your needs. All of the related documentation can be found here, including the special case of 32-bit operating systems. And don’t forget, if you want to inject the VirtIO drivers into your Windows ISO, check out my blog post here.

Nutanix Acropolis 101: Creating VMs

Now that Nutanix Acropolis is shipping with NOS 4.1.3, I wanted to cover a few basics in a series of blog posts. Most of you won’t be familiar with Acropolis, which is based on KVM. If you’ve used KVM in the past, you will know how difficult it can be. Acropolis removes much of the complexity and headache. So for my first installment, I wanted to do something very basic: Upload an ISO to the Nutanix cluster which I could use to image a VM, then create a VM and install the OS from the ISO.

Please take note that the Acropolis road map is quite detailed with many major enhancements in both terms of features and ease of use. So in a few months this procedure will probably change, particularly around ISO management. But 4.1.3 is shipping today, so here’s what you need to do. This assumes you have a running  Nutanix cluster imaged with Acropolis/KVM.

1. From your Windows machine launch WinSCP. Enter the hostname/IP of your Acropolis cluster, change the port to 2222, then use a username of ‘admin’ and your cluster password. WinSCP should then connect to NDFS.

2. Once WinSCP connects, in the right pane you will see a list of containers. If no containers exist, then you have a brand new cluster and need to go into PRISM and create a storage pool and container. Refreshing WinSCP may not reveal the new container(s), so you may need to reconnect to see them. I went into my first container and created a directory called “ISO”.

3. Next, in the left pane of WinSCP navigate to your ISO(s) and drag them into the right pane. Wait for the upload process to complete.

Note: In NOS 4.5 we will be adding a PRISM ISO upload option, so you won’t need to resort to WinSCP for uploading your ISOs. There’s also some cool feature in the future around ISO libraries that is in the works.

4. Login into PRISM (the Nutanix GUI not the NSA spy tool). From the left pull-down menu select “VM”.

2015-07-14_9-04-48

5.  From the left-side menu, select Create VM:

2015-07-14_9-09-38

6. Next up we need to define some VM parameters, such as memory and CPU. Fill in the form as appropriate for your VM.

2015-07-14_9-14-04

7. Next, click on New Disk. The dialog box below opens up. Assuming you’ve already created a container, just enter the size of the disk in GB. All disks are thin provisioned, so no need to select various format types.

2015-07-14_9-16-09 8. After the disk is created, we now need to add a NIC. If this is the first VM you have created, and haven’t yet defined any networks, we need to define a network to attach the VM to. You can of course have different networks, each associated with a different VLAN.  Click on “New NIC”, then you will see the box below.

2015-07-14_12-37-28

Because we have no networks, click on “Add Network”. Add the relevant VLAN ID and close the dialog box. Note, in NOS 4.5 you will be able to define network names, so you won’t have to rely on remembering long UUIDs.

9. Now, if you followed my article to inject the VirtIO drivers into your Windows ISO, then configure the CD-ROM to mount your ISO image from the NDFS datastore. If you have a virgin Windows ISO image and didn’t inject the drivers, then you can mount a second CD-ROM to the VM. In this second CD-ROM mount your VirtIO ISO image.

10. Power on the VM, and wait for Windows to boot. When you get to the “Where do you want to install Windows?” screen you have two option. First, if you created your custom Windows ISO then your boot disk should be listed and you can proceed as normal. If you are relying on the second CD-ROM, then click on Load Driver and browse to the vioscsi driver for the appropriate operating system. Your boot disk should now appear.

2015-07-31_12-33-55

11. Proceed with the Windows installation as normal. Once Windows is fully installed, login as administrator.

12. Open the Device Manager, and you will see a NIC under Other Devices with a yellow exclamation point. Right click and update driver software. On the VirtIO CD navigate to the NetKVM folder and appropriate OS. You NIC will now be detected.

2015-07-31_12-49-17

13. Congratulations! You now have a fully functional Acropolis Windows VM. Unlike other hypervisors, you don’t need to install any additional drivers..just SCSI and NIC. Keyboard, video and mouse are all native and should work as expected.

Injecting KVM VirtIO Drivers into Windows

When dealing with hypervisors it is not uncommon to be required to supply specific drivers in order to recognize the virtual hardware, such as NICs and SCSI controllers. A while back I wrote blog articles on how to inject VMware drivers (PVSCSI and VMXNET3) into a Windows Server 2008 R2, Windows 7 image and Windows Server 2012. You can check out those articles here and here. But if you use the Nutanix Acropolis hypervisor (based on KVM), you will need a different set of drivers.

This article will show you how to inject the VirtIO drivers into your Windows Server 2012 R2 ISO, so that it will recognize the virtual KVM hardware. Do keep in mind that in the future Nutanix will be redistributing the Fedora VirtIO drivers, after we get them WHQL signed by Microsoft. So while this article uses unsigned Fedora drivers, in the future you can use fully signed and supported drivers. Stay tuned for that release!

The process below injects the required drivers into the Windows Server 2012 R2 installation boot files, and the actual Window Server operating system, for a fully KVM aware image. The drivers include Balloon, NetKVM, serial, rng, SCSI, and stor.

1. Download the Windows 8 ADK (Assessment and Deployment Kit) from here. Never mind that it says Windows 8, as it will work with Windows Server 2012 R2.

2. Start the installation process and after a long download select the two options below (Deployment Tools and Windows Preinstallation Environment (Windows PE)). WinPE is optional, but in case you need it in the future, I’d install it anyway. If you are in a hurry and won’t ever use WinPE, just select Deployment tools.

3. Mount the Windows Server 2012 R2 ISO. Navigate to the Sources directory and copy boot.wim and install.wim to your computer, say on the C: drive under C:\WIM.

4. Download the Fedora VirtIO Drivers from here, or when they are released, the Microsoft-signed Nutanix Acropolis driver bundle. Fedora packages the drivers as an ISO, so mount that ISO to your VM. I’m using the Z drive for my CD-ROM.

5. Create a folder on the C: drive called Mount. This will be the WIM mounting target.

6. Depending on your Windows Server 2012 R2 ISO image, it may have varying amounts of images included in the WIM. The VL ISO I have contains four indexes, or images. You can list the indexes with the following command:

dism /get-wiminfo /wimfile:C:\WIM\install.wim

2015-07-17_13-22-44Decide which index you want to inject the drivers in. Open the provided batch file found here and modify the IDX variable as needed. You could run the script multiple times and do all indexed images, if you wish.

7. Run the batch file and wait for it to complete. It should take a few minutes, depending on the speed of your disks. Make sure you monitor the output for any errors, in case you messed up the paths to the files.

2015-07-17_14-25-15

8. Now you can re-build the Windows ISO with the updated WIM files, and you are set. Just create a VM shell on Nutanix Acropolis, then mount the updated ISO, and it will be all set for a smooth installation. If you don’t have an ISO building tool, I recommend UltraISO. It’s not free, but I’ve exceptionally good luck with it for many years.

Download the batch file here.

© 2017 - Sitemap